RE: [voiceinteraction] minutes March 10, 2021

https://www.w3.org/2021/03/10-voiceinteraction-minutes.html

 

and below as text

 

   [1]W3C

 

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

 

                             - DRAFT -

                   Voice Interaction Community Group

 

10 March 2021

 

   [2]Agenda. [3]IRC log.

 

      [2]
<https://lists.w3.org/Archives/Public/public-voiceinteraction/2021Mar/0001.h
tml>
https://lists.w3.org/Archives/Public/public-voiceinteraction/2021Mar/0001.ht
ml

      [3]  <https://www.w3.org/2021/03/10-voiceinteraction-irc>
https://www.w3.org/2021/03/10-voiceinteraction-irc

 

Attendees

 

   Present

          debbie, jim

 

   Regrets

          Bev, Jon (partial)

 

   Chair

          Debbie

 

   Scribe

          ddahl

 

Contents

 

    1. [4]Jim's suggestions

 

Meeting minutes

 

  Jim's suggestions

 

   Jim's comments: [5]https://lists.w3.org/Archives/Public/

   public-voiceinteraction/2021Mar/0002.html

 

      [5]
https://lists.w3.org/Archives/Public/public-voiceinteraction/2021Mar/0002.ht
ml

 

   jim: the document should discuss interfaces

 

   debbie: there's another document called "interfaces", very

   rudimentary

 

   jim: who is the audience?

 

   debbie: one audience is developers for application developers

   . also platform developers

 

   jim: there should be a sentence describing audience

 

   debbie: we should add that

 

   jim: what is the problem?

 

   debbie: I think it's interoperability

 

   jim: I think that's the main purpose

   . describe principles about how the partition was arrived at

   . general software principles could be referenced

   . there is a nice hierarchical partitioning

 

   debbie: we were using a traditional partitioning for

   conversational systems

 

   jim: this should be included in the document

 

   debbie: agree

 

   jim: 2.1 this is a specialized IPA

 

   debbie: it was supposed to be general, maybe we should remove

   this because it's not consistent with the later walkthrough

 

   jim: what is the difference between general and specialized IPA

 

   debbie: the general IPA does general things, but it's a portal

   to more specialized IPA's

 

   jim: the general IPA is something like current smart speakers

   . our audience will be building specialized IPA's, not the

   general IPA's

   . maybe the document should focus on specialized IPA's

 

   debbie: I think we have to talk about both because they have to

   interoperate

 

   jim: the target should be specialized IPA's

 

   debbie: what's the role of standards with specialized IPA's

 

   jim: they could share components like ASR or TTS

   . maybe only the front end is generalized

   . a generalized IPA can answer anything in the world

   . it could be a portal to a specialized IPA

 

   debbie: the generalized IPA knows about public information

 

   jim: generalized IPA could be a portal to a specialized IPA

   . much like a web browser

   . a specialized IPA knows information about a particular

   business

 

   debbie: more general, e.g. government, nonprofit, school

   . we should not drop this because we need them to interoperate

   . we should have more explanation about the difference

   . between general and specialized IPA's

 

   jim: this document provides information for specialized IPA's

   . there will be few generalized IPA's

 

   jim: begin architecture section with 3 high level boxes and

   then expand

 

   debbie: I like the idea of making it more multimodal

 

   jim: more IPA's will have screens

   . move ASR and TTS out of dialog box into client box

 

   +1

 

   jim: what is a "session"?

 

   debbie: we should define what we mean by "session"

 

   jim: may extend over days, multiple users could come and go

   . standards committees have ongoing sessions with multiple

   meetings

 

   debbie: credentials

 

   next time restart at "client activation strategy"

 

 

    Minutes manually created (not a transcript), formatted by

    [6]scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).

 

      [6] https://w3c.github.io/scribe2/scribedoc.html