[voiceinteraction] minutes September 23, 2020

https://www.w3.org/2020/09/23-voiceinteraction-minutes.html

 

and below as text

   [1]W3C

 

      [1] http://www.w3.org/

 

                               - DRAFT -

 

                           voice-interaction

 

23 Sep 2020

 

Attendees

 

   Present

          debbie, jon, dirk

 

   Regrets

 

   Chair

          debbie

 

   Scribe

          ddahl

 

Contents

 

     * [2]Topics

         1. [3]architecture

     * [4]Summary of Action Items

     * [5]Summary of Resolutions

     __________________________________________________________

 

   <scribe> scribe:ddahl

 

architecture

 

   [6]https://w3c.github.io/voiceinteraction/voice%20interaction%2

   0drafts/paArchitecture-1-1.htm

 

      [6] https://w3c.github.io/voiceinteraction/voice interaction
drafts/paArchitecture-1-1.htm

 

   dirk: added id to output

 

   debbie: what if the provider intent doesn't match any core

   intents

 

   dirk: one option would be to fall back to a core error handler

 

   debbie: then the provider couldn't give the user the right

   information

 

   dirk: that is a misconfiguration

 

   debbie: that means someone has to do that mapping every time

   you add a provider

   ... could you let the provider selection service forward the

   native intents to the user

 

   dirk: could update the text to show this

   ... built in core intents, like errors, greetings

 

   debbie: like VoiceXML builtins

   ... noinput, help, errors, nomatch

   ... point 6 in 4.1.2 assumes the Dialog Manager is doing slot

   filling

   ... there are also non-task oriented dialogs

   ... like open-ended chatbots

   ... could the provider handle the dialog

   ... in some systems the slots are almost created on the fly

 

   dirk: we assume that we know all slots and intents in advance

 

   debbie: a completely NN based system might not even have the

   idea of slots

 

   dirk: the Dialog Manger would be a Deep Learning system

 

   debbie: individual dialogs could be open-ended, like talking

   about pets

 

   dirk: some components could be omitted

 

   debbie: how about a diagram of the minimal system

 

   jon: that would be great

   ... here are the three or 4 components that are part of an IPA

   ... what is the least common denominator

 

   debbie: that would help us prioritize

   ... we could talk about what the minimal system cannot do

   ... and then introduce more components

   ... should you tell the user they're being handed off?

   ... suddenly hearing different TTS

   ... do we need to have transparency about who's handling dialog

 

   jon: other provider may be tapping into different data sources

 

   dirk: how much must the dialog know about the provider it's

   handing over to?

   ... should the provider be handed over data

 

   debbie: for example, your name

 

   jon: what about preferences, should they be handed over

 

   dirk: this is related to data exchange among providers

 

   debbie: can providers pass you on to other providers?

 

   dirk: in this diagram control comes back to Dialog Manager

 

   debbie: some of these issues relate to issues in VoiceXML

 

   dirk: we should look back at VoiceXML to see if there is any

   guidance

 

   debbie: will look at VoiceXML

 

Summary of Action Items

 

Summary of Resolutions

 

   [End of minutes]

     __________________________________________________________