- From: Robert Brown <Robert.Brown@microsoft.com>
- Date: Wed, 1 Jun 2011 19:43:11 +0000
- To: Robert Brown <Robert.Brown@microsoft.com>, "Michael Johnston (AT&T)" <johnston@research.att.com>, "Satish Sampath (Google)" <satish@google.com>, "Marc Schroeder (DFKI)" <marc.schroeder@dfki.de>, "Milan Young (Nuance)" <Milan.Young@nuance.com>, Michael Bodell <mbodell@microsoft.com>, "Dan Burnett (Voxeo)" <dburnett@voxeo.com>, HTML Speech XG <public-xg-htmlspeech@w3.org>
FYI, the protocol group will have a conf call 30 minutes before tomorrow's call. Same number, etc. Others are welcome to dial in. -----Original Message----- From: public-xg-htmlspeech-request@w3.org [mailto:public-xg-htmlspeech-request@w3.org] On Behalf Of Robert Brown Sent: Tuesday, May 31, 2011 5:02 PM To: Michael Johnston (AT&T); Satish Sampath (Google); Marc Schroeder (DFKI); Milan Young (Nuance); Michael Bodell; Dan Burnett (Voxeo); HTML Speech XG Subject: Next steps for protocol work It was good seeing everybody in London last week. Personally, I'm very happy with the progress we made. London was also fun to visit (it's always warm and sunny, right?), and Google were great hosts (thanks!). As discussed last Tuesday, we'll break into a sub-group to focus on the protocol so that we can get it done by August (and another sub-group for the API). PARTICIPANTS Here's who I have listed for the protocol work: - Owner/coordinator: Robert (me) - Active participants/contributors: Milan, Marc, Satish, Michael J (I'll coordinate logistics with you in a separate thread.) - Observers/reviewers: everybody else DELIVERABLE I propose the following points for the deliverable: 1. Our final deliverable is a protocol specification to be incorporated into the Final Report. IIRC the schedule we agreed on is to deliver a "last call" version at the end of July, with the final version at the end of August. 2. This protocol spec should... a.) represent the consensus of the XG participants and note any areas of disagreement (as with everything in the Final Report). b.) support the functionality of the API. Although the API is being designed in parallel, the requirements are by now quite stable and progress on the protocol shouldn't be blocked. c.) be sufficiently detailed to enable vendors of user agents and speech services to implement interoperable prototypes. Does this seem reasonable? Please let me know any alterations/additions/etc you'd like to see. Thanks, /Rob
Received on Wednesday, 1 June 2011 19:43:39 UTC