22:58:59 RRSAgent has joined #wot-ap 22:58:59 logging to http://www.w3.org/2015/06/02-wot-ap-irc 23:00:14 Meeting: WoT IG Task force on Protocols and APIs 23:00:26 trackbot, start meeting 23:00:28 RRSAgent, make logs public 23:00:28 Zakim has joined #wot-ap 23:00:30 Zakim, this will be 23:00:30 I don't understand 'this will be', trackbot 23:00:31 Meeting: Web of Things Interest Group Teleconference 23:00:31 Date: 02 June 2015 23:01:35 webex: https://mit.webex.com/mit/e.php?MTID=mc3e594ff9016da23da014de4eb63327d 23:02:07 present+ Johannes_Hund 23:02:21 Chair: Johannes_Hund 23:02:32 do we have a scribe? 23:04:37 thank you very much taki! 23:04:43 Agenda: https://lists.w3.org/Archives/Public/public-wot-ig/2015Jun/0002.html 23:04:48 scribe: TK 23:04:52 scribeNick: taki 23:05:45 kaz_ has joined #wot-ap 23:06:57 JH: Three agenda points 23:07:04 JH: Preliminaries 23:07:11 JH: Architecture and modeling 23:07:21 JH: and representation of driver model 23:07:34 JH: How we can fit it into architecture model 23:07:41 JH: any other topics? 23:08:24 KZ: nothing posted yet in IRC 23:08:37 JH: It is now wot-ap channel 23:09:01 s/KZ/KA/ 23:09:17 J_G_Lynn has joined #wot-ap 23:09:30 Ari_Keranen has joined #wot-ap 23:10:00 Agenda: https://lists.w3.org/Archives/Public/public-wot-ig/2015Jun/0002.html 23:10:35 JH: We don't have dates yet for the next F2F. Beginning of July likely. 23:11:15 JH: Architecture model, and draft primitives of APIs & Protocols. Do we agree we provide them to IG for F2F? 23:11:30 JH: any other additions or opinions? 23:11:44 JH: I take we have agreement there. 23:12:10 JH: Another topic is architecture model. 23:12:31 JH: Daniel provided first draft, based on Joerg provided on mailing list. 23:13:07 JH: W3C wiki does not link in images, so we host document there. 23:13:25 JH: PlantUML code is in the document. Using Graviso. 23:13:55 JH: I suggested people to review the document and get familiar with the tool. 23:14:11 JH: any opinions about the tool? 23:15:03 TK: I played around with it a bit, and found it useful for making charts. 23:15:45 JH: The models shown there reflects also what Dave has shown us. 23:16:35 JH: ... JH introducing what's described in the architecture documents... 23:17:40 JH: You need github account. 23:17:52 JH: It can track who edited what. 23:18:05 JH: History of updates. 23:18:27 JH: Contributions are welcome. 23:19:32 JH: Next, Description of driver model 23:20:40 KN: We need to modify two parts. Real implementation of legacy device is one. 23:21:22 KN: LockServientBT needs additional parts. 23:22:16 KN: needs to be connected LockServientBT 23:23:40 KN: I don't think the one described by Siemens as related to driver is not related to driver. 23:24:57 JH: ScriptAPI needs to be there in those two figures, and the APIs will be the same, correct? 23:26:47 KN: Wireless vs. Wired connection is handled by Resources, action, etc box 23:27:23 KN: From ScriptAPI, they are transparent 23:28:27 KN: Adapter should show the same API 23:29:03 JH: Whether it is bluetooth or any other connection, the API is the same. 23:29:25 JH: Do you have github account? 23:29:41 KN: I am not yet familiar with the tool. 23:30:38 ACTION: jhund to mail the wiki dump to have easier changes 23:30:38 Created ACTION-8 - Mail the wiki dump to have easier changes [on Johannes Hund - due 2015-06-09]. 23:31:33 JH: We will have two kinds of scripting API. 23:31:47 JH: One on client side and one on servient side. 23:32:17 JH: two APIs should not change regardless of the protocols to connect devices. 23:34:15 JH: Resource model, resources and properties. How those model maps to legacy protocols. If you map to HTTP 1.1, events needs polling. We need to collect requirements. 23:34:39 AK: Addressing those devices. Most protocols have it. 23:35:30 JH: We should state what assumption we have for the abstract modeling. 23:36:29 JH: Not sure if we can say which protocol is suitable over another. 23:37:06 AK: Implicit assumption should be stated explicitly. 23:37:40 JH: "Can this protocol address this in this protocol?" this sort of assumption. 23:38:33 JH: There is a spot suitable for describe assumptions. 23:39:52 AK: URL-like addressing. Something close enough. Bluetooth qualify as legacy? 23:40:56 JH: Not necessarily. I am not sure, but bluetooth may also have such addressing ability. 23:41:10 AK: That's something we definitely need to look at. 23:42:01 JH: You raised a good point. Mappable or not relates to driver discussion. 23:43:07 JH: IP-over-legacy, and gateway model. Not mually exclusive. 23:45:21 AK: Ability of addressing and modifying. 23:45:24 rrsagent, draft minutes 23:45:24 I have made the request to generate http://www.w3.org/2015/06/02-wot-ap-minutes.html kaz 23:46:04 JH: Properties, event sources and actions. We assume protocols can represent three kinds of patterns. 23:47:11 AK: There are some protocols that cannot do event sources. i.e. "out of scope" 23:48:44 JH: I suggest guidelines. We address vs. out of scope. 23:49:43 JH: If you have some legacy protocol. When do you want to have driver? 23:50:23 JH: When do you want to use WOT protocols? 23:51:08 JH: Properties, actions and events. Some protocols can map directly, others not. 23:52:18 KN: Device maker needs to fill the gap. 23:53:06 JH: We will make two guidelines. 23:53:30 JH: Mappability, and whether to use protocol adapter vs driver. 23:53:54 JH: Other point to discuss here? 23:54:20 JH: Next meeting will be in one week. 9am central european summer time. 23:55:00 JH: Thank you for participation, thank you for Nimura-san for architecture model. Thank you Ari for bringing up questions. 23:55:59 rrsagent, draft minutes 23:55:59 I have made the request to generate http://www.w3.org/2015/06/02-wot-ap-minutes.html jhund 00:01:57 Present: jhund, Ari_Keranen, J_G_Lynn, k_nimura, taki, (kaz) 00:02:45 rrsagent, draft minutes 00:02:45 I have made the request to generate http://www.w3.org/2015/06/02-wot-ap-minutes.html kaz 00:06:55 taki has joined #wot-ap 01:09:56 taki has left #wot-ap 05:00:54 kaz has joined #wot-ap 06:52:24 Zakim has left #wot-ap