W3C

- DRAFT -

voice interaction

17 Jun 2020

Attendees

Present
debbie, jon, jim
Regrets
dirk
Chair
debbie
Scribe
debbie

Contents


<scribe> scribe:debbie

jim: we should review architecture and then interfaces
... this architecture is more detailed than master plan
... of OVN
... OVN should do something similar
... adopt useful components from W3C

debbie: will go over architecture

https://www.w3.org/community/voiceinteraction/ is our home page

https://w3c.github.io/voiceinteraction/voice%20interaction%20drafts/paArchitecture.htm

debbie: reviews architecture diagram

jim: these could be common business activities
... is there a way that a dialog could be loaded on demand

provider selection service is like DNS for url's

debbie: provider selection service is probably not part of dns

jim: should be able to extend DNS

debbie: DNS might be complicated to work with
... we should learn more about DNS

jim: ICANN is the organization responsible for DNS
... accounts/authentication

debbie: it could be service-specific or generic across the platform

jon: this would enable a platform-agnostic identification?

debbie:

jim: accounts are business-specific

debbie: your bank is not going to delegate authentication

jim: why is core NLP in the blue box?

debbie: should top row be moved to orange box
... ipa providers are for example enterprises
... provider NLU has specialized intents and data for that enterprise

jim: what else should I have asked?

debbie: more back end stuff

jim: where are interfaces?
... dialog broker is used in OVN, it figures out what service is needed

debbie: this seems like the provider selection service

jim: pictures need to address multimodal, emotion detection, generation is limited
... how does this relate to the MMI Architecture?

debbie: TTS and ASR could be generalized
... Dialog management is the equivalent of the Interaction Manager
... TTS and ASR are modality components

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/06/17 16:13:17 $

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)

Present: debbie jon jim
Regrets: dirk
No ScribeNick specified.  Guessing ScribeNick: ddahl
Found Scribe: debbie

WARNING: No "Topic:" lines found.


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: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


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]