00:02:41 naomi has joined #wot 00:11:33 naomi has joined #wot 00:24:21 naomi has joined #wot 04:59:20 naomi has joined #wot 06:17:12 zkis has joined #wot 07:14:47 naomi has joined #wot 07:54:48 dsr has joined #wot 08:27:15 zkis has joined #wot 09:56:03 naomi has joined #wot 10:26:13 naomi has joined #wot 10:53:51 naomi has joined #wot 11:55:14 Karen has joined #wot 12:00:22 uday has joined #wot 12:01:10 Zakim has joined #wot 12:01:17 McCool has joined #wot 12:01:26 rrsagent, bye 12:01:26 I see no action items 12:01:30 RRSAgent has joined #wot 12:01:30 logging to http://www.w3.org/2017/09/13-wot-irc 12:01:32 present+ Michael_McCool 12:01:38 Meeting: WoT IG/WG 12:01:45 mkovatsc has joined #wot 12:01:51 present+ Kaz_Ashimura, Michael_Koster, Uday_Davuluru 12:02:22 present+ Matthias_Kovatsch 12:02:53 dape has joined #wot 12:03:42 present+ Dave_Raggett 12:03:54 present+ Zoltan_Kis 12:03:59 rrsagent, make log public 12:04:05 rrsagent, draft mintues 12:04:05 I'm logging. I don't understand 'draft mintues', kaz. Try /msg RRSAgent help 12:04:09 rrsagent, draft minutes 12:04:09 I have made the request to generate http://www.w3.org/2017/09/13-wot-minutes.html kaz 12:04:12 s/rrsagent, draft mintues// 12:04:44 kajimoto has joined #wot 12:05:44 DarkoAnicic has joined #wot 12:05:55 present+ DarkoAnicic 12:06:23 present+ Daniel_Peintner, Kazuo_Kajimoto, Niklas_Widell 12:06:48 ohura has joined #wot 12:10:31 https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Agenda 12:11:03 scribenick: McCool 12:11:22 ryuichi has joined #wot 12:11:57 present+ Masato_Ohura 12:11:59 nwidell has joined #wot 12:12:25 ohura_ has joined #wot 12:13:30 barryleiba has joined #wot 12:13:33 present+ Barry_Leiba 12:13:50 Matsukura-san, are you working on audio? 12:15:31 present+ Ryuichi_Matsukura 12:15:36 topic: quick updates 12:15:44 kaz: status of fpwd 12:16:09 monday, found some minors issues, talked with editors got some clarification 12:16:24 but will be working with editors, and will get them published tomorrow 12:16:35 mk: dave offered to write a blog 12:16:41 we are still deciding where it will go 12:16:43 s/editors/the webmaster/ 12:17:08 mk: mm, workshop status? 12:17:12 mm: 2 proposals 12:17:23 ... talked with the other proposer 12:17:33 ... updated our proposal a bit 12:17:47 ... to merge the 2 workshops together 12:17:57 ... will circulate the updated proposal to the group 12:18:21 ... we have to submit a paper to the NDSS workshop ourselves 12:18:34 ... the other is IoT security 12:18:47 ... security across various standards 12:18:56 ... focus on Web of Things 12:19:18 ... going to have to work on another proposal for IEEE workshop 12:19:28 mk: what is the motivation for the 2nd one? 12:19:36 mm: focus on standards 12:19:51 ... NDSS one is broader 12:20:02 ... would have more focused workshop for IEEE 12:20:33 ... for NDSS workshop, paper deadline is in 2 months 12:20:45 ... IEEE S&P is May 12:20:49 ... much more time for review 12:21:11 ... would generated an updated proposal for IEEE 12:21:38 ... presenting at NDSS and get people involved 12:21:43 ... and invite them to IEEE one 12:21:54 i/workshop status?/scribenick: kaz/ 12:21:55 mm: I will distribute the revised proposal; could use some more topics related to WoT if you have any suggestions 12:22:22 i/I will distribute/scribenick: McCool/ 12:23:04 topic: plugfest and tpac and next steps for wg 12:23:29 yongjing has joined #wot 12:23:41 mjkoster has joined #wot 12:23:50 present+ Yongjing_Zhang 12:23:59 mk: now we have released fpwd 12:24:03 Chair: Matthias, McCool, Kajimoto, Yongjing 12:24:12 ... some changes; want to get plugfest aligned with the fpwd 12:24:18 present+ Kazuaki_Nimura 12:24:28 ... so one goal is that we want to update node-wot to match the fpwd 12:24:51 ... would also like to target the scenarios as well 12:25:03 tokuyama has joined #wot 12:25:08 ... does anyone see any blockers for updating their implementations 12:25:11 rrsagent, draft minutes 12:25:11 I have made the request to generate http://www.w3.org/2017/09/13-wot-minutes.html kaz 12:25:14 ... to match the fpwd 12:25:23 ... asking implementors and leads 12:25:28 q+ 12:25:59 kajimoto: what is viable target for plugfest implementors? 12:26:21 q+ 12:26:57 ... consensus on what is viable 12:27:20 ... thing description, changes at the plugfest every time 12:27:30 ... so what is standard to define interoperability 12:27:47 ... defined current practices as viable... but now we have fpwd 12:28:10 q? 12:28:12 ack mc 12:28:28 q+ 12:28:37 mm: do you want to define a subset of the fpwd for the plugfest? 12:28:43 kajimoto: yes 12:29:02 present+ Keiichi_Tokuyama 12:29:05 ... first step, update current practices to fpwd 12:29:14 ... for thing description 12:29:24 ... adding security support 12:29:42 ... define purposes for next plugfest to prove concepts 12:30:14 kaz: proposing organizing and orchestrating plugfest as a starting point 12:30:27 ... but not sure we need a profile or a minimum subset 12:30:35 ... would like some clairification 12:30:56 mk: about current practices document, have some responses 12:31:14 q? 12:31:16 ack k 12:31:36 naomi has joined #wot 12:31:48 kajimoto: use cases are good... but we should have some guidelines or standards for how to describe our semantics 12:32:05 ... the current practices document was good to have something to target 12:32:18 ... but now we have the td only, less specific 12:32:38 q+ 12:32:59 q+ 12:33:02 ... would like to update the current practices document to match the fpwd 12:33:25 mk: overall, have plan that current practices needs to be adapted 12:33:28 ack dape 12:33:38 ... but main content is now in fpwd; normative content is there 12:33:54 ... but there are some primary and secondary features; we should define which is which 12:34:05 ... and it would also be useful to set some goals, for instance 12:34:21 ... to describe their security features, test thing, use cases 12:34:40 ack mkovatsc 12:34:45 ... would this solve some of your issues? 12:34:49 kajimoto: yes 12:34:58 kaz: mk has mostly covered my point 12:35:21 ... we probably should update the current practices with whatever is not covered in other fpwd documents 12:35:24 ack k 12:35:43 topic: plugfest update 12:35:58 matsukura: plugfest update, sharing screen 12:36:40 -> https://lists.w3.org/Archives/Public/public-wot-ig/2017Sep/att-0005/Issues_for_TPAC_plugfest_170913.pptx Matsukura-san's slides 12:37:04 See issue #346 12:37:58 -> https://github.com/w3c/wot/issues/346 Issue 346 12:38:10 McCool_ has joined #wot 12:38:14 topic: plugfest update 12:38:25 scribenick: McCool_ 12:38:35 rrsagent, draft minutes 12:38:35 I have made the request to generate http://www.w3.org/2017/09/13-wot-minutes.html kaz 12:38:48 matsukura: three kinds of servient 12:39:15 ... exposed thing, consumed thing, servient (gateway) 12:39:32 ... also integration model, 3-layer, 4-layer 12:40:26 ... issues: interfaces between servients, authentication, discovery, TD exchange, 12:40:34 ... NAT and firewall traversal 12:40:42 ... event operation 12:40:56 ... finally, TD management issues 12:40:59 q+ to CP and authentication 12:41:59 ... for TD management, how to create URI, who manages TD and how 12:43:33 ... call for participation, want to accelerate preparation, share information 12:44:00 ... so please share information about what you plan to do 12:44:52 q+ 12:44:54 q+ 12:45:09 q+ 12:45:33 dape: mentioned authentication... some content used quite a while ago 12:45:47 ... but not sure if it is still the state of the art 12:46:08 -> http://w3c.github.io/wot/current-practices/wot-practices-duesseldorf-2017.html current practice doc 12:46:17 mk: mechanism in current practices is just one way of how it could be done 12:46:29 ... but really we want to describe what is existing 12:46:39 ... rather than defining our own mechanisms 12:46:49 ... main comment is also about management of TDs 12:47:04 ... we have a Thing Directory... at the moment is standalone 12:47:16 ... but could also be merged with a (cloud) servient 12:47:33 ack dape 12:47:33 dape, you wanted to CP and authentication 12:47:34 ... but might also have a sparql endpoing 12:47:35 ack mk 12:47:41 to support semantic search 12:48:01 matsukuru: some variations are possible 12:48:04 mk: could be included 12:48:16 ... logically it could be a separate component 12:48:16 naomi has joined #wot 12:48:20 q? 12:48:38 mm: exposed OCF device as a Thing 12:48:44 ... including CoAP as protocol 12:48:55 ... question about security metada 12:49:18 ... various decision to make about devices 12:49:28 ... mechanisms for authentication 12:49:44 ... we could for further 12:49:55 ... we should pick examples 12:50:07 ack mc 12:50:21 i/exposed/scribenick: kaz/ 12:50:25 mm: I think we should pick some other platforms and figure out how to support them 12:50:35 q+ to comment on work for TPAC on plain JSON and WebSocket based messaging protocol and ask about specific goals for interoperability testing 12:51:11 mm: interested in Amazon Alexa interface 12:51:28 ... that's doable but don't want to identify any devices 12:51:35 ... need to find out how to handle discovery 12:51:43 ... more than one Thing Directory 12:52:00 i/Amazon/scribenick: kaz 12:52:24 mk: Thing Directory could be a good entry point 12:52:38 mm: multiple directories 12:52:46 ... starting with one entry point 12:52:57 ... can be a working assumption 12:53:00 q+ regarding OCF devices provisioning and CMS 12:53:00 mm: I want to build an Alexa service that can discover things and talk to them in a generic way 12:53:13 q+ 12:53:14 mk: good working assumption is one Thing Directory 12:53:17 i/want to/scribenick: McCool_ 12:53:41 mk: if there is more than one, they could still have a single front end and delegate, but we don't plan to do that for plugfest 12:53:53 kaz: do we need an additional document 12:54:01 s/document/document?/ 12:54:08 matsukura: yes, we need an additional document 12:54:22 ... need a specification 12:54:29 s/document/document in addition to the PlugFest wiki/ 12:55:33 ... we do want another document... but were? wiki? markdown? expand current practices document? 12:55:45 mk: propose re-expanding the current practices document 12:56:18 mk: but ultimately should go into arch... but current practices can be used to draft things 12:56:18 ack k 12:56:21 ack d 12:56:21 dsr, you wanted to comment on work for TPAC on plain JSON and WebSocket based messaging protocol and ask about specific goals for interoperability testing 12:56:44 dsr: hope to collaborate with mozilla... websockets, etc 12:56:51 q+ 12:56:54 ... mozilla hopes to bring some actual devices 12:57:04 ... dsr to bring some simulated devices 12:57:11 see: https://lists.w3.org/Archives/Public/public-wot-ig/2017Sep/0006.html 12:57:22 ... wants to see us as a group to clarify our goals for interop testing 12:57:38 ... dsr also looking at "plain JSON" description in collab with mozilla 12:58:09 ... unfortunately ben is unavailable for now... dsr not ready to share 12:58:16 mk: would be better to share early 12:58:18 q+ 12:58:35 dsr: is plain JSON aspect, is also web socket aspect 12:58:53 mk: can the ws aspect be aligned with panasonic? 12:59:21 kajimoto: can you explain the current situation with ws communication? 12:59:50 ... (asking panasonic members) 13:00:33 ... have a document that panasonic sent to mozilla 13:00:45 ... need to understand the differences in the approaches, is useful 13:01:55 tokuyama: have to confirm these topics with rest of panasonic team and communications with mozilla 13:02:17 q? 13:02:18 ... but waiting for response from mozilla 13:02:31 ... have already sent some material to them 13:02:56 mk: best if moz and panasonic can collaborate directly 13:03:12 kaz: probably should send official invitation 13:03:23 dsr: we already talked to them about this 13:03:36 ... they are just waiting for internal authorization 13:03:58 ... so we already talked about this; can send another email, but already aware 13:04:09 kaz: point is they should enter their information on the wiki etc. 13:04:22 dsr: yes, but they are still waiting for internal approval 13:04:29 kaz: ok, will send a reminder 13:04:41 dsr: but they are away until the end of the month 13:04:52 kaz: please cc me when you contact him 13:05:03 q? 13:05:03 q? 13:05:04 q? 13:05:07 ack kaz 13:05:37 zkis: security and provisioning; even though we are not provising them, we still need to get client keys, etc. to talk to OCF devices 13:05:44 ... so that is non-trivial 13:06:10 ... we will have to provide some guidelines on how to do it 13:06:12 s/provising/provisioning/ 13:06:31 mm: and I'm not sure where we find OCF implementations that actually do this... 13:06:48 mk: anyone who brings device needs to figure this out 13:06:55 q? 13:07:00 ack zk 13:07:11 ... the credentials can't go into TD, they have to be provisioned somehow 13:07:24 ack m 13:07:35 mk: ok, out of time... 13:08:01 mk: please do update info 13:08:15 ... even seimens has to do this 13:08:18 -> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_4-10_November_2017,_Burlingame,_CA,_USA#PlugFest_.284-5_Nov_2017.29 plugfest wiki 13:08:26 ... and next to-do is to update the current practices 13:08:46 -> http://w3c.github.io/wot/current-practices/wot-practices.html current practices 13:08:48 ... with focus on use cases 13:09:23 mm: question on node-wot release? 13:09:31 mm: what is timing of node-wot updates? 13:09:39 s/mm: question on node-wot release?// 13:09:50 mk: will only be done just before the plugfest... 13:10:08 ... will have to use current systems, and intercept 13:10:28 ... need to work on a roadmap after cleanup 13:11:01 mm: good topic for next meeting 13:11:09 mk: may not be available next two weeks... 13:11:25 dape: hope we can get it done sooner than two weeks before the plugfest 13:11:39 mk: would also be good to get test thing done early 13:11:49 ... and that has a dependency on the scripting api 13:12:28 barryleiba has left #wot 13:12:33 mm: also, McCool to chair next two meetings, Matthias will not be available 13:12:45 [adjourned] 13:13:02 rrsagent, draft minutes 13:13:02 I have made the request to generate http://www.w3.org/2017/09/13-wot-minutes.html kaz 14:07:56 zkis_ has joined #wot 16:05:12 naomi has joined #wot 16:16:24 Zakim has left #wot 16:38:55 naomi has joined #wot 17:06:28 naomi has joined #wot 17:34:22 naomi has joined #wot 18:05:43 naomi has joined #wot 18:36:39 naomi has joined #wot 19:03:59 naomi has joined #wot 19:08:19 zkis_ has joined #wot 19:32:10 naomi has joined #wot 20:01:54 naomi has joined #wot 20:29:56 naomi has joined #wot 20:34:16 zkis_ has joined #wot 21:00:43 naomi has joined #wot 21:30:00 naomi has joined #wot 21:40:35 naomi has joined #wot 22:08:39 naomi has joined #wot 22:48:52 Karen has joined #wot 23:04:19 Karen has joined #wot