06:32:28 RRSAgent has joined #wot-td 06:32:28 logging to http://www.w3.org/2017/10/13-wot-td-irc 06:32:40 Meeting: WoT WG - TD-TF 06:33:14 present+ Kaz_Ashimura, Darko_Anicic, Michael_Koster, Michael_McCool, Sebastian_Kaebisch, Takeshi_Yamada, Victor_Charpenay 06:34:11 ryuichi has joined #wot-td 06:34:28 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#Agenda 06:34:34 present+ Taki_Kamiya 06:34:44 sebastian has joined #wot-td 06:35:46 present+ Masato_Ohura, Ryuichi_Matsukura, Tomoaki_Mizushima 06:35:55 dape has joined #wot-td 06:36:09 present+ Daniel_Peintner 06:38:17 scribenick: victor 06:38:54 DarkoAnicic has joined #wot-td 06:38:59 present+ DarkoAnicic 06:39:05 topic: TD breakouts 06:39:30 https://www.w3.org/WoT/IG/wiki/F2F_meeting,_4-10_November_2017,_Burlingame,_CA,_USA#Plenary_and_Breakouts 06:40:05 Sebastian: topics were 1. interaction with Alexa, 2. capabilities for semantic modeling 06:40:23 s/TD breakouts/Agenda for today/ 06:40:43 s/Plenary_and_Breakouts/Agenda/ 06:40:53 topic: TD breakout topics 06:40:55 https://www.w3.org/WoT/IG/wiki/F2F_meeting,_4-10_November_2017,_Burlingame,_CA,_USA#Plenary_and_Breakouts 06:41:06 3. observable properties 06:41:43 [[ 06:41:43 WoT Thing Description 06:41:43 Type System: 06:41:43 JSON Schema ontology (JSON Schema vocabulary + Linked Data integration) 06:41:43 How to handle more specific types such as from the CBOR and XML Schema type space (e.g., unsignedShort, date,...)? -- Binding Templates 06:41:46 Evaluation of the new features used in TD for PlugFest: 06:41:48 JSON Schema as Linked Data model 06:41:50 iot.schema.org or Amazon Alexa vocabulary set usage (no decision yet) 06:41:52 introducing subscription flag in Property for doing Property subscription (for CoAP and MQTT) 06:41:54 ]] 06:43:50 q+ 06:44:44 does the group agree on these topics? Questions? 06:44:58 ack k 06:45:13 Mizushima has joined #wot-td 06:45:56 Kaz: people should think of how to expose the capabilities of their devices before 06:46:20 s/before/based on their PlugFest implementations/ 06:46:22 s/people/PlugFest participants/ 06:48:30 in particular, Japanese use EchoNet, McCool OCF. What are the common capabilities? 06:49:05 s/EchoNet/Echonet/ 06:49:23 q+ to wonder about JSON schema ontology and its impact on PlugFest 06:50:05 q? 06:51:07 Sebastian: I also first put in the list an item about a terms for protocol bindings. I removed it because the Protocol binding TF wanted to discuss this. 06:51:52 Michael Koster: right. Nothing we would implement now, though. 06:52:47 s/Michael Koster:/Michael_Koster:/ 06:52:53 Michael McCool: you also mentioned capabilities. Any draft? 06:53:30 s/Michael McCool:/Michael_McCool:/ 06:53:31 MK: nothing yet, see later. 06:54:16 topic: TD for PlugFest 06:54:46 -> https://lists.w3.org/Archives/Member/member-wot-wg/2017Oct/att-0022/TD4PlugFest.pdf Sebastian's slides 06:54:54 1. Alexa. Developers should know what to do before the event. 06:54:57 (updated one to be shared later) 06:55:17 MMC: I have slides on this 06:55:29 ohura has joined #wot-td 06:55:39 -> https://github.com/w3c/wot/blob/master/plugfest/2017-burlingame/WoT%20-%20McCool%20POC%20(003).pdf McCool's slides 06:56:10 q- 06:57:12 an idea is to scan a Thing Directory for markup, and map TDs to Alexa "skill adapters" (e.g. a power controller) 06:57:19 q? 06:57:32 is a JSON object 06:58:13 skill also include light control and streams (e.g. camera image stream) 06:58:18 q+ 06:58:44 q+ 06:59:00 door lock and thermostat 06:59:04 https://developer.amazon.com/docs/smarthome/understand-the-smart-home-skill-api.html 06:59:55 the reason why I asked whether there is a draft for capabilities is that we should define these skills in RDF 07:00:56 MK: capabilities are just pieces of TDs. 07:01:35 I haven't looked at streams yet. But streams are just objects, it should be possible to define actions/events on these objects 07:01:42 https://developer.amazon.com/docs/device-apis/alexa-powercontroller.html 07:02:19 MCC: how to generate the payload to send to Alexa from a TD? 07:02:38 https://developer.amazon.com/docs/device-apis/alexa-powerlevelcontroller.html 07:03:13 ack m 07:03:33 MK: does Alexa map a message to a (vocal) command? 07:04:02 that is, does Alexa send messages to IoT devices in response to commands? 07:04:52 MCC: so it is basically a bridge between a user and the device. Similar to what a TD does 07:05:11 q+ 07:06:52 we should use built-in skills (home skills) and not custom skills (e.g. door lock vs. front door lock/back door lock). It's easier. 07:07:29 ack d 07:07:38 https://developer.amazon.com/docs/device-apis/alexa-powerlevelcontroller.html 07:07:45 Darko: I've been working on capabilities (based on the previous PlugFest). 07:07:59 some are ready (e.g. thermostat) 07:08:37 the most common. You will be able to review them right after I commit. 07:09:59 we are reviewing OCF, Haystack, openT2T, SAREF, etc. We can review Alexa as well 07:10:38 MCC: ok, let's coordinate 07:12:22 MK: the goal of iot.schema.org is to make two servients using each one of the frameworks above be interchangeable 07:13:28 q? 07:13:29 MCC: one scenario I'm working on is "smart security", with a face recognition service 07:13:44 (to lock/unlock one's door) 07:13:52 s/face/person/ 07:13:57 https://www.w3.org/TR/semantic-interpretation/ 07:15:24 Kaz: regarding this, it might relate to the W3C recommandation about speech recognition semantics 07:16:46 ... binding template might want to have that kind of capability to interact with Amazon Alexa at some point 07:16:56 ack k 07:17:33 present+ Amelie_Gyrard 07:18:19 MCC: note on Amazon: security aspects in Alexa are well done, and also in AWS IoT. This was also a reason to look at it. 07:18:54 S: sync between Darko, McCool. We need a decision soon 07:20:29 s/S:/Sebastian:/ 07:22:25 topic: Pull requests 07:22:39 https://github.com/w3c/wot-thing-description/pull/54 07:23:22 topic: Observable properties 07:23:43 https://github.com/w3c/wot-thing-description/pull/54/commits/9b0e1978c939ea5c98ee5339467a4901cca7c72a 07:24:26 Victor: made a PR to wot-thing-description 07:24:54 [[ 07:24:55 observableBoolean value that indicates whether a remote servient can subscribe to ("observe") the Property, to receive change notifications or periodic updates.boolean 07:24:56 ]] 07:25:17 Sebastian: should be moved to the Current Practices doc 07:25:41 Victor: ok, I'll do this. 07:25:57 Sebastian: we also had 'stability' as a field. 07:26:16 zkis has joined #wot-td 07:26:55 -> http://w3c.github.io/wot/current-practices/wot-practices-duesseldorf-2017.html Current Practices (Dusseldorf version) 07:27:18 -> http://w3c.github.io/wot/current-practices/wot-practices-duesseldorf-2017.html#property 3.2.3.1 Property 07:27:37 but it was rarely used (if ever) 07:27:37 q? 07:27:41 q+ 07:28:20 ack k 07:28:45 Sebastian: shall we discuss this field as well in a breakout? 07:29:17 kaz: note during TPAC we don't have a breakout room, so we should assume all the sessions are plenary (at least at this moment) 07:29:18 Kaz: note that we don't have any breakout room at the TPAC 07:30:09 topic: New vocabulary for Protocol Bindings 07:30:15 q+ 07:30:20 MK: we also had a discussion about 'observable' in the Protocol Binding call. 07:30:44 s/topic: New vocabulary for Protocol Bindings// 07:30:47 topic: New vocabulary for Protocol Bindings 07:31:16 Sebastian: as I said before, isn't this too soon? 07:31:31 MK: we'll try to experiment with it at the PlugFest 07:31:51 next Wednesday, we'll have some draft. 07:32:01 (PB call deadline) 07:32:54 Darko: w.r.t. observable properties, what would be the difference with events? 07:32:58 q+ 07:34:46 MK: the discussion last Wednesday was about events with/without state 07:35:25 an event is something that is not a Property state change 07:35:55 ack v 07:36:11 ack d 07:36:13 q+ 07:36:25 is an hypothesis at this point. 07:37:03 Kaz: where shall this discussion take place (TD, Protocol bindings)? 07:37:26 MK: maybe during the main meeting 07:37:36 Kaz: that would make sense, I think 07:37:39 Sebastian: Protocol bindings. The TD should only reflect the decisions taken there 07:38:47 anyway, clear guidelines are needed. 07:39:09 MK: at least, best practices. 07:39:23 q? 07:39:32 ack m 07:40:09 MCC: some protocols are more event-oriented and speaking about states might seem confusing 07:40:34 ack m 07:40:49 MK: You said Zigbee? It also is oriented towards state change. 07:42:09 topic: Open issues 07:42:10 topic: open issues and current discussions 07:42:17 s/topic: Open issues// 07:42:34 Sebastian: new issue from Taki 07:42:50 -> https://github.com/w3c/wot-thing-description/issues/56 issue 56 07:42:59 are (should) the RDF files (be) normative? 07:44:37 MK: is the TD RDF vocab constraining anything? If not, we maybe shouldn't standardize it? 07:45:02 Sebastian: no need to decied now. To discuss at the TPAC 07:45:16 -> https://github.com/w3c/wot-thing-description/issues/53 issue 53 07:45:32 second issue: docs for semantics in TD 07:45:50 idea of "integration level" of semantic annotations 07:46:27 third: stability. We discussed that today 07:46:44 -> https://github.com/w3c/wot-thing-description/issues/29 issue 29 07:47:09 -> https://github.com/w3c/wot-thing-description/issues/16 issue 16 07:47:34 TD serialization, nothing new? 07:47:59 Kaz: fiy, Dave recontacted Ben about this 07:48:25 s/about this/and I'll also follow that up 07:48:32 S: can you ask him if he's going to the PlugFest 07:48:36 ? 07:48:45 s/S:/Sebastian/ 07:48:51 Kaz: will do 07:48:55 q+ 07:49:08 ack d 07:49:20 Daniel: is it 07:49:40 -> https://github.com/w3c/wot-thing-description/issues/14 issue 14 07:49:55 s/is it/is the new proposal for data types going to be implemented for the PlugFest?/ 07:50:05 S: yes 07:50:25 identical for most types 07:50:38 -> https://lists.w3.org/Archives/Member/member-wot-wg/2017Oct/att-0022/TD4PlugFest.pdf Sebasitian's slides (see slide 3: Data Type (Prio 1)) 07:50:45 ack dape 07:51:01 q+ 07:52:12 -> https://github.com/mjkoster/wot-protocol-binding/blob/master/bindingtemplates-19092017.pdf Koster's slides for the Binding call 07:52:28 MK: I've started to use it. The change regarding name/value results in a more compact representation, a sort of emplatet 07:53:08 Victor: by the way, there is a PR pending 07:53:12 ack v 07:53:27 -> https://github.com/w3c/wot-thing-description/issues/13 issue 13 07:54:39 Sebastian: will close that later 07:54:44 -> https://github.com/w3c/wot-thing-description/issues/12 issue 12 07:55:20 issue #13 can be closed, its outcome was the proposal for data types using Linked data 07:55:44 MK: Issue 12 is related to the issue on serialization 07:55:54 Sebastian: maybe we should change the title of this issue 07:56:02 -> https://github.com/w3c/wot-thing-description/issues/9 issue 9 07:56:29 [@@@ victor's clarification should go before the link of issue 12] 07:57:16 Sebastian: issue 9 is from Maria. Not put in practice by PlugFest participants, though 07:57:28 -> https://github.com/w3c/wot-thing-description/issues/3 issue 3 07:58:05 issue 3 is old. The discussion moved on to TF LD, right? 07:58:41 https://w3c.github.io/wot-thing-description/#namespaces 07:58:46 -> https://github.com/w3c/wot-thing-description/issues/2 issue 2 07:58:47 Darko: I can put this on the agendo of TF LD 07:58:59 s|-> https://github.com/w3c/wot-thing-description/issues/2 issue 2|| 07:59:01 -> https://github.com/w3c/wot-thing-description/issues/2 issue 2 07:59:18 Sebastian: last issue about binary encodings. No news on it. 07:59:57 new issue from Maxime 07:59:59 -> https://lists.w3.org/Archives/Public/public-wot-wg/2017Sep/0013.html Maxime's issue on the ML 08:00:50 context: one Property(, one data type), two serialization/media types 08:01:47 s/one/1./ 08:01:50 s/two/2. / 08:02:27 the question is whether we should have one data type def per media type or not 08:03:25 -> https://lists.w3.org/Archives/Public/public-wot-wg/2017Oct/0005.html Maxime's proposal to have discussion on Oct 20 08:03:32 Maxime is not here today, we'll postpone the discussion for next week 08:03:53 -> https://github.com/w3c/wot-thing-description/pull/55 PR 55 08:04:14 There is also a PR from Maria, which actually depends on the discussion initiated by Maxime 08:04:26 Also ajourned. 08:04:43 [adjourned] 08:04:49 rrsagent, make log member 08:04:53 rrsagent, draft minutes 08:04:53 I have made the request to generate http://www.w3.org/2017/10/13-wot-td-minutes.html kaz 11:18:01 Zakim has left #wot-td 14:05:17 RRSAgent has joined #wot-td 14:05:17 logging to http://www.w3.org/2017/10/13-wot-td-irc 14:05:25 Meeting: WoT IG - TF-LD 14:05:30 present+ Kaz_Ashimura, Danh_Le_Phuoc, Taki_Kamiya 14:05:35 present+ Michael_Koster 14:05:40 present+ Aparna_Thuluva, Darco_Anicic, Victor_Charpenay 14:05:44 present+ Uday_Davuluru 14:05:54 rrsagent, make log public 14:05:58 zkis has joined #wot-td 14:05:58 rrsagent, draft minutes 14:05:58 I have made the request to generate http://www.w3.org/2017/10/13-wot-td-minutes.html kaz 14:06:30 present+ Maxime_Lefrançois 14:10:28 zakim, pick a scribe 14:10:28 Not knowing who is chairing or who scribed recently, I propose Maxime_Lefrançois 16:36:07 Zakim has left #wot-td 18:21:46 zkis has joined #wot-td 21:51:03 zkis has joined #wot-td