- From: Deborah Dahl <Dahl@conversational-Technologies.com>
- Date: Wed, 2 Oct 2019 11:12:22 -0400
- To: <public-voiceinteraction@w3.org>
- Message-ID: <06c201d57933$ca92f7e0$5fb8e7a0$@conversational-Technologies.com>
Present: Debbie, Dirk Chair: Dirk Scribe: Debbie Regrets: Brian Dirk: try to find a new time Dirk: start with Phil Archer message https://lists.w3.org/Archives/Public/public-voiceinteraction/2019Sep/0007.ht ml Dirk: 4 points, 1. updates to SSML Debbie: there's a lot interest, but not a priority for us right now Dirk: 2. defining additional hooks for Web pages to aid voice-driven navigation Debbie: probably not a priority either Dirk: 3. "The voice assistant platforms include a lot of proprietary technologies that are very unlikely to be standardised" ...we should find a way to find somethings to standardize Debbie: usually don't standarize technologies, mostly API's ... 4. good agreement around the room that a W3C workshop would be well worth exploring. Dirk: that would be a good idea Debbie: yes Debbie: big players don't always have to be on board, sometimes even a single person can get something going Debbie: W3C workshops are organized by the W3C, have a program committee, meet, produce a report ... also some discussions at SpeechTEK Dirk: talk about the use case https://lists.w3.org/Archives/Public/public-voiceinteraction/2019Sep/0005.ht ml Debbie: (reviews use case of travel planning) Dirk: authentication could be something for the future Debbie: add use case to next version Dirk: can you create template and add use case? ...in the github repository (https://github.com/w3c/voiceinteraction/tree/master/voice%20interaction%20d rafts ) ...new document "Intelligent personal assistant architecture" Debbie: there should be an overview ...boxes would be connected by API's Debbie: what to standardize? ...format of dialog registry ...interface between the red parts and the blue parts ...what contacts the Provider Selection Service? Dirk: possibly the dialogs themselves Dirk: information needed is utterance string, url Debbie: maybe separate "core provider" into its own box Debbie: revise use case to be independent of the architecture Dirk: add explanation of how the use case is reflected in the architecture, in addition to the pure use case Dirk: how to gain more momentum? Ask group when they could attend a call Debbie: having a document will give people something to react to
Received on Wednesday, 2 October 2019 15:12:47 UTC