12:07:42 RRSAgent has joined #wot 12:07:42 logging to http://www.w3.org/2016/03/16-wot-irc 12:08:31 present+ Daniel_Peintner 12:09:10 present+ DarkoAnicic 12:09:19 Soumya has joined #wot 12:09:38 present+ SOumya 12:10:13 VictorCharpenay has joined #wot 12:10:37 zakim, pick a scribe 12:11:04 Louay has joined #wot 12:11:18 (I will Scribe) 12:11:45 Johannes: F2F@Montreal Updates. Draft agenda available 12:11:57 https://www.w3.org/WoT/IG/wiki/F2F_meeting_2016,_April,_11th_-_13th,_Montreal,_Canada 12:12:22 There's still room for contributions 12:12:52 (see Input/Comments section) 12:13:46 Sebastian: contribution to add from Bosch about the BEZIRK IoT platform 12:14:07 toru has joined #wot 12:14:41 Johannes: there should be a dedicated section for expert talks -> Sebastion will do it. 12:15:38 Johannes: next topic: Plugfest. 12:16:18 q+ 12:16:20 room will be available on Sunday for demos, presentation on the same day as open contributions. Same setup as in Nice 12:17:00 See table on the F2F wiki page for contributions to the plugfest. 12:17:33 Put your name if you are willing to participate. 12:18:13 Reminder: deadline for registraton is April, 5th 12:20:42 Daniel: comment about the plugfest: would it make sense to move it later? 12:21:02 in the afternoon. 12:22:28 Johannes: new column in the participatin table for availability on Sunday -> Daniel will do it. 12:23:24 q+ 12:23:47 Sebastian: just updated it myself: added an Encoding column to know which encodings are used by the devices. 12:24:07 Yingying has joined #wot 12:24:49 Louay: column for discovery. Still a bit early to tell what kind of discovery we want to setup during the plugfest. 12:25:51 Johannes: last time, was a central discovery with self-registration to a server (see webthing-repository on Github) 12:26:09 thingweb-repository* 12:27:10 Louay: my own demo will offer 3 discovery mechanisms. How a client will know which one(s) is (are) available 12:27:25 Johannes: How-to needed? 12:28:08 Sebastian: Feedback from last time: common vocabulary needed. Discovery should rely on that. 12:29:58 Yingying has joined #wot 12:31:04 Louay: also important. Example of SSDP: SSDP requests (similar to UDP request) and response with some links? What should be the content of the requests? Should the response contain link to the Thing Description, something else? 12:31:16 rrsagent, make minutes 12:31:16 I have made the request to generate http://www.w3.org/2016/03/16-wot-minutes.html Yingying 12:31:18 Indeed, how-to/discussion needed. 12:33:06 Soumya: als wants to have a mDNS client, we should synchronize. 12:33:42 kaz has joined #wot 12:34:16 Johannes: this how-to should be included in the Current Practice document (http://w3c.github.io/wot/current-practices/wot-practices.html) 12:34:47 Sebastian: discussion about a common vocab should also start now. 12:35:15 Darko: we could use the Scenario table to foresee which concepts are needed. 12:37:31 Johannes: further topics about the F2F? 12:38:03 Soumya: in the agenda, joint breakout sessions. Should it be prepared by each TF? 12:39:04 Johannes: would make sense. Topics should be collected directly on the wiki page. 12:39:42 rrsagent, draft minutes 12:39:42 I have made the request to generate http://www.w3.org/2016/03/16-wot-minutes.html Soumya 12:40:11 Next topic: Charter 12:40:28 set up by Dave and Yingying. 12:41:17 s/and Yingying./, kaz and Yingying./ 12:41:31 contributions welcome through Github (issues or pull requests) 12:43:00 https://github.com/w3c/charter-drafts/blob/gh-pages/wot-wg-2016.html 12:44:02 in our own Github repo, all raised issues in the WG/ folder should be added to the charter 12:44:55 Feedback is welcome about this charter, e.g. relevant agenda? IPR? 12:45:22 present+ Kaz 12:47:21 already submitted a PR: https://github.com/w3c/charter-drafts/pull/47 12:47:32 rrsagent, draft minutes 12:47:32 I have made the request to generate http://www.w3.org/2016/03/16-wot-minutes.html kaz 12:47:56 rrsagent, make log public 12:47:59 rrsagent, draft minutes 12:47:59 I have made the request to generate http://www.w3.org/2016/03/16-wot-minutes.html kaz 12:48:30 Meeting: WoT IG/TF-TD 12:48:35 end of the IG topics. Moving to TD topics 12:48:38 Chair: Johannes 12:48:40 rrsagent, draft minutes 12:48:40 I have made the request to generate http://www.w3.org/2016/03/16-wot-minutes.html kaz 12:49:16 topic: New TD structure 12:49:53 [ present: Kaz, Johannes, Achille, Claes, Daniel, Darko, Johannes, Katsuyoshi, Louay, Michael, N_Wang, Ryuichi, Soumya, Takuki, Toru, Victor, Yingying ] 12:50:38 -> http://w3c.github.io/wot/current-practices/wot-practices.html WoT Current Practices Document 12:50:54 see Current Practice document. 12:51:33 s/see Current Practice document/Sebastian: see Current Practice document/ 12:52:39 new structure based on feedback from last time. 12:52:47 1. "href", new term to indicate how to access the Thing's properties, events, events. 12:53:08 2. removed "metadata". Instead metadata fields directly in the root object 12:53:17 -> http://w3c.github.io/wot/current-practices/wot-practices.html#quick-start-td-samples Example 1 at 3.1.1 Quick Start: TD Samples 12:53:33 q+ 12:53:47 q? 12:54:06 Michael: clarification: intended to use standard URI rules (like concatenation of base URI and localname)? 12:54:06 Zakim has joined #wot 12:54:17 q+ jhund 12:54:28 (example was "href": "temp") 12:55:22 q+ 12:55:47 those rules are defined in RFC 3986 12:56:28 present+ Toru_Kawaguchi 12:56:44 something that would be needed is to have composite Things 12:57:19 q? 12:57:32 q+ 12:58:28 ryuichi has joined #wot 12:59:11 k_nimura has joined #wot 12:59:22 q? 12:59:45 Victor: it has been added to the TD vocabulary: "associatedThing", to link different Things with each other 13:00:07 ack jhund 13:00:13 Johannes: other comment about mandatory and optional fields 13:00:30 I have to leave now, but I have experience the same Michael mentioned. I considered them as M2M device having several endpoints and described the device and endpoints seperately. 13:00:44 I can talk on this later if required 13:00:51 Bye for now 13:00:53 Sebastian: all this should be added in the Current Practice document 13:01:20 Soumya and Johannes agree with Michael 13:03:47 Johannes: TD is the blueprint of how to communicate with the Thing. Not known beforehand. Need for TD "templateĀ§? 13:04:03 s/"templateĀ§/"template" 13:04:17 s/"templateĀ§/"template"/ 13:05:52 Darko: similar to the difference between class and instance. Using classes/templates could increase interoperability 13:05:53 q? 13:06:20 ack dape 13:07:18 Daniel: about Michael's question about "href". In case of URI arrays, cartesian product or one-to-one mapping? 13:08:17 Michael: definitely not in the RFC. Should have a kind of "map" of base URIs 13:09:23 where each base URI fits 13:09:51 Daniel: what if the resource structure is different depending on the scheme (HTTP, CoAP)? 13:10:45 ack Soumya 13:11:33 Michael: chance of having such a situation? 13:12:10 Sebastian: this was about TD core. There's also the possibility to extend a TD with other vocabularies. 13:12:23 Darko will present this part 13:13:32 Darko: 1. machine-readable -> defined term in vocabs already available. 13:14:33 2. aditional properties to describe a Thing? Provided in an extended context, as shown in Example 2 of the Current Practice doc. 13:15:02 Ex: "@type": "sensor:Temperature" 13:15:16 or "sensor:unit": "sensor:Celsius" 13:16:40 q+ 13:17:13 Michael: it really makes sense to do such things. 13:18:14 have you tried to convert JSON-LD into RDF triples? 13:21:24 Darko: by the way, we have much better TDs if we start from RDF and turn them afterwards into JSON-LD than writing it directly in JSON-LD 13:22:10 Michael: things would be easier if we put as many things in the context, maybe? 13:23:13 Darko: want to standardize TD, we shouldn't re-standardize existing vocabs (such as units, quantity kinds) 13:25:43 way to go -> one TD context + one horizontal context for common concepts like units? 13:26:32 Sebastian: moving on to the next example of a TD (see Current Practices) 13:27:21 "uri", "decodings". And "security": requirements to access Thing's resources 13:27:30 ack MIchael 13:27:58 self-contained. Example 3 shows auth with JSON Web Token (JWT). 13:30:42 A lot of new things, details to be found on the document. Comments welcome. 13:31:49 other questions about the TD? 13:32:30 End of the meeting. 13:32:40 rrsagent, make minutes 13:32:40 I have made the request to generate http://www.w3.org/2016/03/16-wot-minutes.html Yingying 13:35:23 present: Kaz, Johannes, Achille, Claes, Daniel, Darko, Johannes, Katsuyoshi, Louay, Michael, N_Wang, Ryuichi, Soumya, Takuki, Toru, Victor, Yingying 13:35:30 rrsagent, make minutes 13:35:30 I have made the request to generate http://www.w3.org/2016/03/16-wot-minutes.html Yingying 13:36:15 taki has left #wot 14:47:01 kaz has joined #wot 16:03:42 Zakim has left #wot 18:06:40 bengo has joined #wot 19:29:27 bengo has joined #wot 20:38:03 bengo has joined #wot