14:57:39 RRSAgent has joined #voiceinteraction 14:57:39 logging to https://www.w3.org/2022/06/01-voiceinteraction-irc 14:57:52 meeting: Voice Interaction Community Group 14:58:00 chair: debbie 14:58:09 scribe: ddahl 15:10:24 present: debbie,michael,noreen,bev 15:10:42 topic: promotional work 15:11:10 debbie: jim put together a proposal for voice workshop at W3C 15:11:27 ...should try another way to promote that 15:13:15 michael: jon was at the European Voice Lunch 15:15:26 debbie: check to see if I sent bev the 100 word abstract 15:17:09 debbie: can resend 15:17:15 ...if you can use it 15:18:23 debbie: the second topic was reviewing the interfaces document 15:19:18 ...but let's skip that and talk about the MMI Architecture/Interfaces comparison 15:26:05 debbie: reviews MMI architecture 15:27:17 ...sessionid and Context seem to be the same 15:28:10 ... requestid and RequestID are the same 15:29:05 ...MMI has a Data event vs. three fields for Interfaces document 15:34:49 ...Content/ContentURL isn't in the Interfaces document 15:36:22 jim: we shouldn't tell the component what to do 15:38:17 debbie: maybe we used to have a single system communicating vs now we have more collaborating systems 15:39:21 jim: only one message type (Start) vs. collection of messages where the name implies the action 15:43:41 jim: only one message type, with the first field the action that's being requested and the other fields are parameters for that action 15:45:00 debbie: one messge e.g. "voiceInteractionMessage", with an action like start, stop, acknowledge 15:46:25 debbie: fields could be contingent on actions 15:46:55 jim: a specific message type has a fixed set of fields 15:48:26 ...could we define new messages? 15:52:21 noreen: start is like a presence detection message in a chatbot 15:52:54 debbie: we should think about presence detection 15:54:04 jim: how do these instructions map to messages? 15:56:04 debbie: how generic do we want the messages to be? 15:56:24 jim: the messages should be pretty generic, like in MMI Architecture 15:57:08 bev: messages should be kept at a high level 15:57:35 ...do we have a list of protocols? 15:57:49 debbie: like HTTP or REST? 15:58:30 ...try to stay at top of protocol stack 15:59:54 debbie: we should list messages 16:00:21 jim: we should call these actions 16:00:27 debbie: what about events? 16:02:31 bev: thinks actions is good 16:03:23 jim: could be messages, actions, or events 16:04:56 rrsagent, format minutes 16:04:56 I have made the request to generate https://www.w3.org/2022/06/01-voiceinteraction-minutes.html ddahl 16:05:01 rrsagent, make logs public 17:14:06 ddahl has left #voiceinteraction