- From: Deborah Dahl <Dahl@conversational-Technologies.com>
- Date: Tue, 5 Oct 2021 12:13:12 -0400
- To: <public-voiceinteraction@w3.org>
1. Publicity: Any updates? See marketing plan at https://github.com/w3c/voiceinteraction/edit/master/marketing-plan.md 2. W3C Technical Plenary -- any questions? See schedule and registration information at https://lists.w3.org/Archives/Public/public-voiceinteraction/2021Sep/0004.html a. voice agent interoperability breakout session proposal https://www.w3.org/wiki/TPAC/2021/SessionIdeas#Voice_Agent_Interoperability Exact date and time TBD, but will be during the week of October 18-22. Our session will be open to the public. b. Regular group call, same time of day but October 27 and with a different URL (TBD) and the possibility of outside observers https://www.w3.org/wiki/TPAC/2021/GroupMeetings 3. Interfaces discussion Let's look at whether the Multimodal Architecture + EMMA is suitable for describing the information in input path 5 in Figure 3 https://w3c.github.io/voiceinteraction/voice%20interaction%20drafts/paArchitecture-1-2.htm#walkthrough input path 5 description: "The IA Service forwards the received data simultaneously to the ASR in the local path and to the Provider Selection Service in the remote path. " Note that there are 2 paths labeled "5" -- the local path where all the ASR, NLP, and Dialog Management happens locally and the remote path where the speech and metadata is forwarded to the Provider Selection Service and then to the IPA Providers. I think we should focus on the remote path, since that is more complex, but we can also discuss the local path if there's interest. EMMA spec: https://w3c.github.io/emma/emma2_0/emma_2_0_editor_draft.html MMI Architecture spec: https://www.w3.org/TR/mmi-arch/ Zoom information: https://lists.w3.org/Archives/Member/internal-voiceinteraction/2020Dec/0000.html
Received on Wednesday, 6 October 2021 03:25:23 UTC