- From: Deborah Dahl <Dahl@conversational-Technologies.com>
- Date: Wed, 18 Nov 2020 12:03:42 -0500
- To: <public-voiceinteraction@w3.org>
- Message-ID: <1d0301d6bdcc$c51034c0$4f309e40$@conversational-Technologies.com>
https://www.w3.org/2020/11/18-voiceinteraction-minutes.html
and below as text
[1]W3C
[1] http://www.w3.org/
- DRAFT -
Voice Interaction Community Group
18 Nov 2020
Attendees
Present
debbie, jon, dirk
Regrets
Chair
debbie
Scribe
ddahl
Contents
* [2]Topics
* [3]Summary of Action Items
* [4]Summary of Resolutions
__________________________________________________________
<scribe> scribe:ddahl
architecture document
[5]https://w3c.github.io/voiceinteraction/voice%20interaction%2
<https://w3c.github.io/voiceinteraction/voice%20interaction%252>
0drafts/paArchitecture-1-1.htm
[5] https://w3c.github.io/voiceinteraction/voice interaction
drafts/paArchitecture-1-1.htm
debbie: review changes in the introduction and additional
standards
dirk: specialized assistants in Amazon ecosystem need a trigger
word
... should describe how these are triggered somewhere in the
document
jon: expect that 25% of enterprises will have a voice assistant
by 2025
... can share that data
... they have to be interoperable
... David added IPA in ASR and ISO-2476-12 for DIT++
... TEI (text encoding initiative)
debbie: MRCP (Media Resources Control Protocol)
jon: Open Agent Architecture for provider selection service
... in accounts and authentication (OATH) and Open ID
... in Core NLU -- abstract meaning representation
... can send links
... also ARPA NGRAM
... which is the same as the SRI-LM format
debbie: should we add a column for the responsible standards
body?
... we don't need to go into that
... may not be worth the effort
... some may be obsolete or not adopted
dirk: should add a disclaimer at the beginning
debbie: some may be standards that we would adopt and others
might just be informative
dirk: could add dialog modeling language from the other
community group
debbie: not saying anything about quality or usefullness
... of these standards and some are de facto standards or
proposals
... also, what about audio formats and codecs?
... or is that too low-level (ogg vorbis, speex)
dirk: this could be endless
... this could be important if you need to forward audio
debbie: we won't talk about audio codecs, but they need to be
agreed upon
... could we use whatever the Audio Working Group uses?
dirk: doesn't see that in Web Audio document
[6]https://www.w3.org/TR/webaudio
[6] https://www.w3.org/TR/webaudio
<scribe> ACTION: debbie to investigate web audio to see if they
say anything
debbie: agnostic to low level protocols, e.g. web sockets and
http
... but then it won't work if the service doesn't understand
the protocol
dirk: WebRTC
... what about IPA Service?
debbie: there is an open source smart speaker called Mycroft,
is there an open way to configure it?
dirk: that's more of an IPA client
... the closest might be a web service
debbie: would REST be an example?
dirk: what about "core intent set"?
debbie: DAMSL is relevant but more abstract than core intents
... core intents are more specific
dirk: a core intent could be "help"
debbie: some core intents are defined in VoiceXML ("builtins")
-- help, nomatch, noinput and error
<scribe> ACTION: debbie to start editing in these changes,
review next call
debbie: should publish when these edits and caveats are added
... maybe the beginning of the year would be a good goal
<scribe> ACTION: debbie to look into host key problem
Summary of Action Items
[NEW] ACTION: debbie to investigate web audio to see if they
say anything
[NEW] ACTION: debbie to look into host key problem
[NEW] ACTION: debbie to start editing in these changes, review
next call
Summary of Resolutions
[End of minutes]
__________________________________________________________
Received on Wednesday, 18 November 2020 17:03:57 UTC