13:58:27 RRSAgent has joined #multimodal 13:58:27 logging to http://www.w3.org/2016/11/07-multimodal-irc 13:59:06 ddahl has joined #multimodal 14:01:31 dirk has joined #multimodal 14:02:22 scribe: ddahl 14:02:30 chair:Debbie_Dahl 14:02:35 topic:actions 14:03:09 regrets: helena 14:03:15 agenda: https://lists.w3.org/Archives/Member/w3c-mmi-wg/2016Nov/0000.html 14:03:29 action-454? 14:03:29 action-454 -- Deborah Dahl to Turn bullet list into text -- due 2016-09-05 -- OPEN 14:03:29 https://www.w3.org/2002/mmi/Group/track/actions/454 14:03:41 debbie: that was working on the use cases 14:03:45 ...for robots 14:04:05 action-456? 14:04:05 action-456 -- Kazuyuki Ashimura to Generate a picture based on the tpac flip chart idea -- due 2016-10-10 -- OPEN 14:04:05 https://www.w3.org/2002/mmi/Group/track/actions/456 14:04:09 -> https://lists.w3.org/Archives/Member/w3c-mmi-wg/2016Nov/0001.html Kaz's diagram 14:04:50 -> https://www.w3.org/2002/mmi/kaz/images/MMI-as-UI-for-WoT.svg SVG version diagram 14:05:22 -> https://www.w3.org/2002/mmi/kaz/images/MMI-as-UI-for-WoT.png PNG version 14:06:27 debbie: what is the protocol between MMI and WoT? 14:07:23 ...the line between the MMI and WoT boxes? 14:07:43 kaz: there are several possibilities 14:08:01 debbie: maybe Life Cycle events? 14:08:29 dirk: what is the main purpose of this? 14:09:02 kaz: MMI architecture could be the UI for the WoT framework 14:10:09 kaz: EMMA could be used for interacting with devices 14:11:12 kaz: WoT scripting also thinking about event handling and discovery, want to ask MMI to look at WoT proposal 14:11:38 debbie: we can look at that 14:12:34 -> https://github.com/zolkis/wot/blob/master/proposals/restructured-scripting-api/intel-proposal.md Intel's proposal for WoT scripts 14:13:45 kaz: a developer would be writing scripts to this API 14:14:13 ...all the clients and servers need to use this API, not connect directly 14:14:52 dirk: arrow between the boxes needs to be a WoT protocol, not Life Cycle 14:15:15 kaz: this proposal doesn't handle events or data itself 14:15:59 kaz: the detailed protocol is hidden 14:16:38 debbie: you could put a layer between the MMI and the WoT that would make the WoT look like a MC 14:17:13 kaz: the Automotive WG is looking at a low level socket interface rather than a scripting API 14:17:59 kaz: this one is not directly handling protocols and data, but is more high level, it's more of a wrapper around a socket connection 14:18:19 ...API definition depends on the policy of each standardization group 14:18:34 ...W3C should clarify the layers of the socket interfaces 14:18:55 ...low level, sockets, high level API's 14:19:19 kaz: that should be handled by the TAG 14:20:10 debbie: is there a process for raising a question to the TAG? 14:20:35 ...do we send an email? 14:21:29 kaz: many of the TAG visited Tokyo last week. I helped moderate a session about the Web Incubator Community Group 14:22:40 https://www.w3.org/community/wicg/ 14:23:04 kaz: in the W3C we can send proposals to the TAG, but this is also a mechanism for the public 14:23:53 debbie: what's the question? what's the best way to evolve the web to non-traditional platforms 14:24:18 kaz: the web consists of browsers, but also servers and other related components 14:24:42 ...browsers are important, but that's not all 14:25:12 ...wondering how to integrate script discussion and UI discussion with MMI discussion 14:25:56 dirk: what is the problem between scripting and MMI? 14:27:12 kaz: the MMI architecture has a complete set of life cycle control, but the WoT group has to think about how to integrate devices and what kind of newly created script should be used 14:27:46 ..how to integrate their proposals with our framework 14:28:43 kaz: dirk, what kind of protocol do you use in your work, and how do you convert? 14:29:31 dirk: we used public/subscribe middleware so that we didn't care where something was deployed 14:30:26 kaz: what should we do if we need to access specific devices? 14:31:32 debbie: I've always used middleware between the IM and the device 14:32:13 kaz: MMI IM should be another WoT servient 14:32:39 dirk: is this more like an application using this servient? 14:33:54 kaz: WoT is an MC from the MMI viewpoint 14:35:11 kaz: should there be one WoT servient that manages all the WoT servients? 14:35:26 ...in one application? 14:37:18 debbie: if the WoT is one MC then we don't care about how it's organized internally 14:37:34 kaz: we need to know who to talk with 14:38:19 debbie: what are examples of those servients? 14:38:39 kaz: from the WoT viewpoint, each servient handles a capability and a device 14:39:13 ...kaz: each servient should be attached to a device 14:39:38 ...like a rice cooker or refrigerator 14:40:34 ...the WoT box could contain the servients for the whole hourse 14:40:41 s/hourse/house 14:41:02 dirk: but we don't have the Russian doll kind of nesting like MMI 14:41:55 kaz: each module has server and client capability 14:42:50 ...but some servients can act more like an IM and some are more like modality components 14:45:43 debbie: isn't the RM more of a processor? 14:46:20 kaz: RM could be split into processor and descriptiong 14:46:30 s/descriptiong/description 14:48:14 dirk: in MMI the behaviors are mostly defined by ExtensionNotification 14:50:16 kaz: we should respond to the WoT proposal and hen we can have a joint discussion 14:50:32 s/hen/then 14:50:59 debbie: is the scripting link a good place to start? 14:52:05 ...someone needs an action to look the scripting proposal 14:54:39 kaz: we should look at the updated scripting proposal but we can start commenting on the discovery part 14:55:38 close action-456 14:55:38 Closed action-456. 14:55:57 action: kaz to update the WoT/MMI relationship diagram 14:55:57 Created ACTION-460 - Update the wot/mmi relationship diagram [on Kazuyuki Ashimura - due 2016-11-14]. 14:56:40 action-457? 14:56:40 action-457 -- Kazuyuki Ashimura to Make a strawman/template diagram for relationships between entities in a use case -- due 2016-10-10 -- OPEN 14:56:40 https://www.w3.org/2002/mmi/Group/track/actions/457 14:57:03 kaz: will do that 14:57:25 ...also need to merge dirk's update to the use cases 14:57:42 action-459? 14:57:42 action-459 -- Kazuyuki Ashimura to Coordinate with helena about her library software for the github -- due 2016-10-31 -- OPEN 14:57:42 https://www.w3.org/2002/mmi/Group/track/actions/459 14:58:02 kaz: will coordinate with helena 14:58:43 kaz: helena could create a subfolder of the MMI repository, but I need to talk with her about licensing 15:04:17 rrsagent, format minutes 15:04:17 I have made the request to generate http://www.w3.org/2016/11/07-multimodal-minutes.html ddahl 15:13:05 rrsagent, make logs public 15:13:06 rrsagent, make log public 15:13:10 rrsagent, draft miutes 15:13:10 I'm logging. I don't understand 'draft miutes', kaz. Try /msg RRSAgent help 15:13:17 s/rrsagent, draft miutes// 15:13:22 rrsagent, draft minutes 15:13:22 I have made the request to generate http://www.w3.org/2016/11/07-multimodal-minutes.html kaz 15:13:36 Meeting: MMI WG 15:13:45 present: Debbie, Dirk, Kaz 15:13:51 Meeting: MMI WG 15:13:51 rrsagent, draft minutes 15:13:51 I have made the request to generate http://www.w3.org/2016/11/07-multimodal-minutes.html kaz 17:32:21 Zakim has left #multimodal