W3C

- DRAFT -

voice-interaction

23 Sep 2020

Attendees

Present
debbie, jon, dirk
Regrets
Chair
debbie
Scribe
ddahl

Contents


<scribe> scribe:ddahl

architecture

https://w3c.github.io/voiceinteraction/voice%20interaction%20drafts/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]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/09/23 16:06:18 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/dialog manager/provider/
Succeeded: s/componetsthat/components that/
Succeeded: s/prioritze/prioritize/
Present: debbie jon dirk
Found Scribe: ddahl
Inferring ScribeNick: ddahl

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]