Meeting minutes
<Bev> Hello
mycroft
debbie: could mycroft be used to demonstrate interoperability?
www.mycroft.ai
debbie: open source with open license
tobias: could we do a demo for our work?
debbie: spec progress
… in the W3C, we have Community Groups, don't have official specs, we're just developing ideas
… if specs become popular or if W3C start a Working Group, which does propose formal specs
… Web Speech API was a Community Group, published a few years ago
https://
tobias: should make a plan for 2022 at one of our calls
<Bev> Dirk joined the meeting
tobias: could develop some ideas for what a working group might cover
tobias: develop work packages
<Bev> Discussed workshop at TPAC and in the works
<Bev> Discussed community group maturity and working groups
interfaces document
dirk describes IPA client
bev: on technical architecture, is this for edge computing
dirk: not familiar with edge architecture
bev: uses local resources, not in the cloud
debbie: I think this is supposed to be location-agnostic
dirk: IPA is probably on user's device and dialog is in the cloud
debbie: encourage sending questions to public list
tobias: would the next steps be to specify the interfaces between blocks
debbie: we should work on the main interfaces
… as a priority
tobias: could show how DIN spec goes between client and dialog
dirk: interface could be EMMA between client and dialog
tobias: DIN only differs in a couple of parameters from EMMA
debbie: may want to think about conveying binary data
… like audio
bev: how to detect different types of voice
debbie: EMMA can represent biometrics, but not too much actual work has been done
dirk: thinking of how the MMI Architecture applies
… could align terminology with MMI
tobias: could visualize how a voice command could work through the architecture
dirk: sequence diagrams
ACTION: tobias to create a diagram