Meeting minutes
promotional work
debbie: jim put together a proposal for voice workshop at W3C
… should try another way to promote that
michael: jon was at the European Voice Lunch
debbie: check to see if I sent bev the 100 word abstract
debbie: can resend
… if you can use it
debbie: the second topic was reviewing the interfaces document
… but let's skip that and talk about the MMI Architecture/Interfaces comparison
debbie: reviews MMI architecture
… sessionid and Context seem to be the same
… requestid and RequestID are the same
… MMI has a Data event vs. three fields for Interfaces document
… Content/ContentURL isn't in the Interfaces document
jim: we shouldn't tell the component what to do
debbie: maybe we used to have a single system communicating vs now we have more collaborating systems
jim: only one message type (Start) vs. collection of messages where the name implies the action
jim: only one message type, with the first field the action that's being requested and the other fields are parameters for that action
debbie: one messge e.g. "voiceInteractionMessage", with an action like start, stop, acknowledge
debbie: fields could be contingent on actions
jim: a specific message type has a fixed set of fields
… could we define new messages?
noreen: start is like a presence detection message in a chatbot
debbie: we should think about presence detection
jim: how do these instructions map to messages?
debbie: how generic do we want the messages to be?
jim: the messages should be pretty generic, like in MMI Architecture
bev: messages should be kept at a high level
… do we have a list of protocols?
debbie: like HTTP or REST?
… try to stay at top of protocol stack
debbie: we should list messages
jim: we should call these actions
debbie: what about events?
bev: thinks actions is good
jim: could be messages, actions, or events