12:05:02 RRSAgent has joined #wot-ap 12:05:02 logging to http://www.w3.org/2016/03/23-wot-ap-irc 12:05:06 present+ Louay_Bassbouss 12:05:33 Claes has joined #wot-ap 12:05:39 Zakim has joined #wot-ap 12:05:49 Zakim, please pick a scribe 12:05:49 I don't who is present, jhund 12:06:22 Zakim, please pick a scribe 12:06:22 I don't who is present, jhund 12:07:22 present+ Claes_Nilsson 12:07:43 scribe: TK 12:07:47 scribeNick: taki 12:08:01 dape has joined #wot-ap 12:08:41 Johannes: Topics are Plugfest face-to-face. And, Interaction model of discovery. 12:09:40 https://github.com/louaybassbouss/wot/blob/di-flows-bindings/TF-DI/DiscoveryFlowsAndBindings.md 12:11:08 LB: Discusses discovery patterns and flows. 12:11:42 LB: Consumer, Client looks for things. Server offers things. 12:12:02 LB: Registry. Manages thing description. 12:12:28 LB: Generator is a pattern. How to generate description from templates. 12:12:44 LB: Each pattern has three paragraphs. 12:13:31 LB: First flow, we already had at plugfest. Registry, Thing Provider and Consumer. 12:14:06 LB: First step, query. Last step is to get Thing description. Only focuses on discovery. 12:14:22 LB: Consumer and Provider use the same registry. 12:14:42 LB: Sparcle query, for example. 12:15:29 LB: Second pattern. Registry advertises URIs. 12:16:02 LB: Consumer doesn't need to know URI of registry. 12:16:20 LB: Third pattern. There is no registry. 12:16:40 LB: Each provider advertises URIs. 12:17:03 LB: Suitable for home. Offline use. 12:17:27 LB: SSDP and bluetooth low energy can be used. 12:17:45 LB: Consumer and provider need to be in the same network. 12:18:40 LB: Flow 4. Similar to 3. Suitable for mechanism without filitering. 12:19:09 LB: Last pattern. Provider is not compatible with WoT. 12:19:21 LB: Consumer can discover this. 12:19:54 LB: BLE, not compatible with WoT. But you can get meta-deta of this device. 12:20:21 LB: Consumer, given this meta-data, can send this data to Generator. 12:21:06 LB: Consumer will get a Thing description that has all information that contains BLE binding. 12:21:18 LB: Does't have to repeat this again. 12:21:48 LB: Second section is bindings. 12:22:00 LB: SSDP, mDNS etc. 12:22:16 LB: We can use it in Plugfest. 12:23:05 LB: We need specific type. W3C Things. Provider needs to know the type. 12:23:07 LB: 12:23:58 LB: In addition to location, I added new header, URI to the Thing description. 12:24:20 LB: Thing disappear, byebye message can be sent. 12:25:04 LB: Optional parameters for sending query. We can discover things that are "light". 12:25:20 LB: Sparkle query, or others can be used. 12:26:03 LB: New parameter, Link to description. Query is used or not is another option. 12:26:26 LB: This is just one idea to get Description. 12:26:32 rrsagent, make minutes 12:26:32 I have made the request to generate http://www.w3.org/2016/03/23-wot-ap-minutes.html Yingying 12:26:49 LB: We will do the same for other subsections. 12:27:44 q+ 12:27:49 MK: This is one way to advertise. 12:28:02 q+ 12:28:16 MK: Server pattern should also be considered. 12:28:32 LB: 5 patters are not the whole picture. 12:28:52 LB: Your point is similar to pattern 2, or 3. 12:29:42 LB: This is just SSDP binding. 12:30:02 LB: I will add other bindings. Will add things like resource directory. 12:30:03 ack j 12:31:08 JH: How to abstract those flows, so that we can design APIs. Filter objects, URI of thing provider so on. Any inputs? 12:31:26 JH: What if I have server that serve multiple things possible? 12:31:45 LB: You always send input, and get result. 12:31:55 LB: result description. 12:32:49 LB: Depending on technology, you need address of registry in flow 1. 12:34:04 LB: We discussed last time, each discovery technology uses different filters. 12:34:21 LB: But we can use the same filter. 12:34:40 JH: Servient hosting multiple things? 12:35:12 LB: All the flows, servers serve multiple things. In most cases, multiple things are used. 12:35:30 LB: Servers can send multiple description. 12:35:32 ack C 12:36:02 CN: IETF Core. Binding should be defined. Resource directory. 12:36:11 present+ Katsuyoshi_Naka 12:36:26 present+ Daniel_Peintner 12:36:39 LB: BLE, Zigbee, for example. If we want to use existing discovery protocols, we need bindings. 12:36:50 q+ 12:36:58 ack dape 12:37:02 rrsagent, make minutes 12:37:02 I have made the request to generate http://www.w3.org/2016/03/23-wot-ap-minutes.html Yingying 12:37:37 DP: We would need specific binding. SSDP. How much work to enable SSDP for plugfest? 12:37:41 rrsagent, make logs public 12:38:04 LB: Not very complex. Depends on platform. Modules for SSDP available. 12:38:13 rrsagent, make minutes 12:38:13 I have made the request to generate http://www.w3.org/2016/03/23-wot-ap-minutes.html jhund 12:38:27 LB: Advertising things, discover things, 10 lines of code. 12:38:48 title: Web of Things TF AP call 12:39:00 Chair: Johannes 12:39:18 LB: We have experiences and modules. Node-JS makes it very simple. 12:39:39 LB: We need to agree on Messages. 12:40:10 LB: We use property. td....w3c.org. This new header. 12:40:32 LB: Implementation was not complex with Node-JS on Android. 12:40:49 s/td....w3c.org/TD.WOT.W3C.ORG/ 12:40:58 https://github.com/fraunhoferfokus/peer-ssdp 12:41:13 JH: Your presentation is enough for implementation? 12:41:26 LB: For SSDP, I think yes. 12:42:03 LB: If you see the binding. You see query header. We should agree on language, such as sparkle. 12:42:34 JH: You need to register things? 12:43:09 LB: We can use the same registry we used in plugfest. Client discovers this end point. 12:43:56 JH: Registry needs to be enhanced. 12:44:08 JB: I will do the same for mDNS. 12:44:39 s/JB/LB/ 12:45:04 LB: We should use the same technology, such as both side use SSDP. 12:45:17 JH: Browser can use it? 12:45:41 LB: Browser can't use it. You can use Cordova for that. 12:45:58 q+ 12:46:04 JH: Registry is a client in that case. 12:46:42 JH: Can we come up with one or two ways to implement for plugfest? 12:47:20 LB: SSDP, mDNS, Eddystone. 12:47:35 LB: Android and Cordova. 12:47:53 LB: We can still test Android against Node-JS. 12:48:48 LB: We can add columns. Things are discoverable, which technology. Client supports discovery, which technology. 12:49:24 DP: We already have column for discovery. Technology part is missing. 12:49:41 DP: Current registry needs to support for SSDP, for example. 12:50:14 LB: Registry runs on NodeJS? 12:50:22 DP: It is Java. 12:51:11 LB: Advertiser and registry can run on the same machine. 12:51:59 LB: We can also support query. 12:53:21 JH: Looking at meeting page. 12:53:22 rrsagent, make minutes 12:53:22 I have made the request to generate http://www.w3.org/2016/03/23-wot-ap-minutes.html Yingying 12:53:32 JH: Seems there are not big changes. 12:54:14 JH: We have F2F page. Hotel, registration fee. 12:54:35 JH: Preparation on Sunday. 12:54:47 JH: Monday is open day and plugfest. 12:55:02 JH: Tuesday and Wednesday are reguar meeting. 12:55:42 JH: Sebastian invites Bosch. I am approaching MIT. 12:56:13 JH: We have presentation from Soumya. 12:56:39 JH: Sunday preparation starts at 11am. 12:57:02 JH: We would like to know people come in the meeting or not. 12:57:36 JH: Please describe what you bring for plugfest. 12:57:55 JH: so that we can come up with scenarios. 12:58:14 JH: If anyone already knows implementation, please describe. 12:58:37 JH: If you know any other presenter at Open Day, please let us know. 12:58:42 present: Johannes_Hund, Chao_Ma, Claes_Nilsson, Daniel_Peintner, Frank_Reusch, Katsuyoshi_Naka, Kazuaki_Nimura, Louay_BassBouss, Michael_Koster, Nan_Wang, Takuki_Kamiya, Arne_Broering 13:00:08 arne has joined #wot-ap 13:00:15 JH: Thank you for participating. Louay, thank you for presenting today. 13:00:40 JH: I hope to see you in Canada. 13:01:04 rrsagent, make minutes 13:01:04 I have made the request to generate http://www.w3.org/2016/03/23-wot-ap-minutes.html Yingying 13:01:06 oh, thanks Taki for scribing!