- From: Young, Milan <Milan.Young@nuance.com>
- Date: Tue, 4 Oct 2011 12:41:59 -0700
- To: Dan Burnett <dburnett@voxeo.com>, <public-xg-htmlspeech@w3.org>
I'd like some discussion on how the parameters set and queried in the API map to protocol messages. I think there are two dimensions to consider: * Standard and extension parameters. Could we use a naming convention to distinguish? * Parameters bound to a particular request and those set/queried on a session level. What syntax in API allows the browser to make use of these separate channels? I'm also interested to know if we can begin solidifying how continuous speech results will be represented in the protocol. I sent out a response to the proposal from Satish and Michael last week and suspect we're pretty much in agreement on the flow of information. Perhaps it's time to pin this down to actual headers and message formatting. Thanks -----Original Message----- From: public-xg-htmlspeech-request@w3.org [mailto:public-xg-htmlspeech-request@w3.org] On Behalf Of Dan Burnett Sent: Tuesday, October 04, 2011 12:04 PM To: public-xg-htmlspeech@w3.org Subject: Reminder: send questions Group, Please remember to send any questions you have about how the protocol relates to the Web API in advance of our call this week so Robert can be ready to address them. The most recent version of the protocol on the mailing list is here [1]. -- dan [1] http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Sep/0012.ht ml
Received on Tuesday, 4 October 2011 19:43:48 UTC