- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Thu, 18 Aug 2011 20:59:25 +0300
- To: "public-xg-htmlspeech@w3.org" <public-xg-htmlspeech@w3.org>
- CC: "DRUTA, DAN (ATTSI)" <dd5826@att.com>
On 08/18/2011 08:08 PM, DRUTA, DAN (ATTSI) wrote: > Today, In the protocol meeting a general question has being raised > regarding the protocol work and general browser interoperability. I > will try to summarize it and turn it into an action/agenda item for > our future meetings. > > In our set of agreed requirements and design decisions the group > concluded that it must be possible for a web application to specify > the speech engine and that the speech engine implementations must be > specified by URI. (except the default one) > Since we agreed on these design principles it > became increasingly evident that in order to successfully fulfill the > requirements we need participation from the browser vendors in > supporting the common protocol being worked in the subgroup formed > for this very reason. As not all the browser vendors participate in > this subgroup, I propose for our upcoming call that we should have a > readout regarding this topic, feedback from our browser vendor > members and clear commitment statements regarding the support for the > common protocol Yes, I would expect that support for protocol / non-default-engines will be there after the basic support for default engine has been implemented. I assume that some implementations will be done this way partly because certain browsers release a new version quite often (every 6 weeks or so) which affects a bit how new APIs are released, and partly because it is valuable to get feedback from the web developers about the API before implementing the rest of the thing. > and it's extensions. I'm not sure which extensions you're talking about. The protocol itself should be stable and standardized. The protocol may allow sending non-standard messages between client and service, but the way that happens should be part of the protocol spec. -Olli > This will help the group address > any interoperability concerns in order to finalize the report. > > Best Regards, Dan ____________________________ Dan DRUTA| AT&T > Service Standards > > >
Received on Thursday, 18 August 2011 17:59:54 UTC