- From: Deborah Dahl <Dahl@conversational-Technologies.com>
- Date: Wed, 24 Feb 2021 13:30:32 -0500
- To: <public-voiceinteraction@w3.org>
Reminder -- we're going to talk about publication on our next call (March
10), so this would be a good time to comment on the draft.
Here's the link:
https://w3c.github.io/voiceinteraction/voice%20interaction%20drafts/paArchit
ecture-1-1.htm
minutes:
https://www.w3.org/2021/02/24-voiceinteraction-minutes.html
and below as text.
[1]W3C
[1] https://www.w3.org/
- DRAFT -
voice interaction
24 February 2021
[2]IRC log.
[2] https://www.w3.org/2021/02/24-voiceinteraction-irc
Attendees
Present
bev, debbie, dirk, jimLarson, jon
Regrets
-
Chair
debbie
Scribe
ddahl
Contents
1. [3]review Debbie's updates
2. [4]Summary of action items
Meeting minutes
<BC> Hello
review Debbie's updates
[5]https://github.com/w3c/voiceinteraction/commit/
cd5aefa00cee887583e89d5aedc3158057224548
[5]
https://github.com/w3c/voiceinteraction/commit/cd5aefa00cee887583e89d5aedc31
58057224548
dirk: should say something about input and output of NLG, can
make use of the context to determine best form of output
debbie: anything about "dialog"?
debbie: change "support" to "supply"
debbie: we'll talk about publishing next time (March 10)
debbie: brief definition of "data provider"
jim: examples of data providers?
dirk: could be a bank, temperature sensor, IoT thing
. we should add examples of data providers
bev: could be added to the use case
dirk: we could add that to the use case
debbie: external services
debbie: how is that different from a data provider?
dirk: it's a subset of data providers
jim: could make a change in the world, like send something to
printer
<BC> relying parties too
debbie: IPA providers
debbie: external service, broader than data
dirk: services also executing
bev: are users included, or just services?
<BC> Users?
debbie: I think users are more at the beginning of the
interaction
debbie: back to IPA providers
<BC> Ok
bev: need to make sure we define IPA's
dirk: IPA's that could forward requests to another IPA
dirk: request could be forwarded to Alexa
jon: or from Alexa to your bank
dirk: forwarding requests has been covered
jon: IPA's enable interactions by users
<BC> @jon +1
debbie: we should add acknowledgements before publishing
Action: debbie to make editorial changes that we've discussed
Action: jon, jim, bev to read and comment by March 8
debbie: then return to interfaces document, JSON version of
EMMA
debbie: try to align ideas with OVN, since there is overlap?
jim: have whiteboard session to get together and chat about
common ideas
. on Tuesdays
jon: could also be on another session or larger workshop
debbie: should focus on problems, not specific architectures
jon: there are two or three big questions -- e.g. how is a
dialog shared between agents
jon: focus on one-two questions
jim: W3C seminar on how to voice applications work together
jim: focused W3C-like seminar, more whiteboard talks, visit to
OVN regular meeting
debbie: start with whiteboard?
jon: jim and I will work offline
jim: what will happen after this document is published?
dirk: would like to see it reflected in IPA implementations
jim: this is meant to be an inspiration to developers
. we can give presentations, etc.
bev: information architecture community group
. several members are interested in helping
debbie: they could just join voice interaction
. bev can post to IA group
<BC> Thank you
debbie: link to the architecture document [6 ]https://
w3c.github.io/voiceinteraction/voice%20interaction%20drafts/
paArchitecture-1-1.htm
[6] https://w3c.github.io/voiceinteraction/voice interaction
drafts/paArchitecture-1-1.htm
Summary of action items
1. [7]debbie to make editorial changes that we've discussed
2. [8]jon, jim, bev to read and comment by March 8
Received on Wednesday, 24 February 2021 18:30:46 UTC