- From: Deborah Dahl <Dahl@conversational-Technologies.com>
- Date: Wed, 9 Sep 2020 12:20:34 -0400
- To: <public-voiceinteraction@w3.org>
- Message-ID: <053101d686c5$25631ca0$702955e0$@conversational-Technologies.com>
https://www.w3.org/2020/09/09-voiceinteraction-minutes.html and below as text [1]W3C [1] http://www.w3.org/ - DRAFT - Voice Interaction 09 Sep 2020 Attendees Present debbie, jon, dirk Regrets Chair debbie Scribe ddahl Contents * [2]Topics 1. [3]branding 2. [4]use case walkthrough * [5]Summary of Action Items * [6]Summary of Resolutions __________________________________________________________ <scribe> scribe: ddahl debbie: hoping to try to go through architecture and use case <scribe> agenda: connect use case to architecture dirk: dialog strategy, branding, replace TTS by NLG debbie: there could also be a voice interaction with audio files or hybrid audio and TTS jon: what about voice registry and W3C architecture dirk: we can do that in a follow-up call ... dialog strategy added to document version 1.1 [7]https://w3c.github.io/voiceinteraction/voice%20interaction%2 0drafts/paArchitecture-1-1.htm [7] https://w3c.github.io/voiceinteraction/voice interaction drafts/paArchitecture-1-1.htm dirk: in section 3.2.2 ... actually 3.2.2.1 ... dialog registry may have to be omitted for some dialog strategies ... should not make any assumptions about the exact strategy debbie: we could give an example of VoiceXML as a frame-based strategy dirk: SCXML could be an example of state-based ... Trindikit would be information state update, could be starting to be commercialized debbie: amazon could be an example of frame-based because of slot-filling dirk: dialog manager would be a black box ... could there be a standard for dialog representation debbie: maybe would reduce interest on the part of people with a powerful dialog manager ... could separate dialog definition from execution ... in VoiceXML FIA is separate from the form ... maybe sometime we would want to have a dialog representation language dirk: Conversational Interfaces Community Group [8]https://www.w3.org/community/conv/ ... was defining a dialog scripting language ... programming relying on states [8] https://www.w3.org/community/conv/ debbie: where do we put the dialog strategy dirk: not visible, because it defines dynamic behavior ... executed by the dialog manager <scribe> ACTION:dirk to add examples of dialog strategies branding dirk: in this architecture, there's no way to have platform branding ... this could be solved by having a dedicated dialog that does routing forward and backward ... there would be a dedicated core dialog, with its own TTS, or forward the audio directly to IPA ... replace TTS by NLG ... TTS could be part of NLG, "output" would make it more general debbie: how about "user input" and "system output" and explain in text ... there is a huge use case for visual output ... gestures and gaze are probably not going to be used very soon ... biometrics are common now dirk: we should give some hints about multimodality but most use cases are voice use case walkthrough debbie: how do we represent that dirk: numbers in diagram referring to text ... sequence diagram would be hard to understand debbie: make steps in use case more explicit and number them <scribe> ACTION: debbie to update use case debbie: two separate diagrams ... first step is to expand on use case, then draw a second diagram ... should be able to do a bulleted list by tomorrow dirk: can update the diagram tomorrow <scribe> ACTION:dirk to update diagram with numbers referring to use case Summary of Action Items [NEW] ACTION: debbie to update use case [NEW] ACTION: dirk to add examples of dialog strategies [NEW] ACTION: dirk to update diagram with numbers referring to use case Summary of Resolutions [End of minutes] __________________________________________________________ [12] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
Received on Wednesday, 9 September 2020 16:20:49 UTC