W3C

– DRAFT –
Voice Interaction Community Group

09 February 2022

Attendees

Present
anastasios, debbie, dirk, jim, jon, ulrike, votis
Regrets
-
Chair
Debbie
Scribe
ddahl

Meeting minutes

changes to interface document

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

dirk: changed diagram to focus on major interfaces

jim: not sure what half circle notation means

dirk: will add legend explaining notation
… also added sequence diagram

dirk: only shows calls to external processing

jim: walks through sequence diagram

dirk: will add "External processes" to "APIs/Data"
… will add three labels to "APIs/Data"
… will update both documents

debbie: reviews overall work of group

dirk: reviews architecture

debbie: would be good to get comments on the public mailing list

dirk: if there are questions we need to improve how we describe things

public mailing list is public-voiceinteraction@w3.org

jim: what if there is no IPA, what does it mean to send the interpretation back?

dirk: sendInterpretation needs to be corrected

jim: what is response to "callServices"?

dirk: there should be a response, for example to indicate errors

jim: every message should have a response

ulrike: what is the small square?

dirk: just shows that there is some activity going on there

dirk: this is just one turn, there might be multiple turns

jim: if neither IPA or service calls are present, what is the content of the response? must one of these be present?

dirk: no

debbie: the external services are not necessarily called

dirk: should add a local call

debbie: maybe add text that some client input can be completely handled on the local side

jim: we need a box under the "opt service call" that there might be some dialog processing

ulrike: can all three items occur?
… external IPA, external service call, and local following one clientInput

jim: squares are optional but they're independently optional

dirk: optional things are independent of each other in the general case?
… should we explain that?

ulrike: I think it's clear

dirk: added service call interface, semantic interface

debbie: semantics should be aligned with JSON
… should be able to add multi-intents and nbest intents
… also nested entities

jim: tables are more useful than text

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).