W3C home > Mailing lists > Public > public-xg-htmlspeech@w3.org > March 2011

RE: An early draft of a speech API

From: Robert Brown <Robert.Brown@microsoft.com>
Date: Wed, 16 Mar 2011 22:16:10 +0000
To: Satish Sampath <satish@google.com>, "Olli@pettay.fi" <Olli@pettay.fi>
CC: Olli Pettay <Olli.Pettay@helsinki.fi>, "Young, Milan" <Milan.Young@nuance.com>, "public-xg-htmlspeech@w3.org" <public-xg-htmlspeech@w3.org>, Bjorn Bringert <bringert@google.com>
Message-ID: <113BCF28740AF44989BE7D3F84AE18DD19877AE7@TK5EX14MBXC118.redmond.corp.microsoft.com>
>> Since all 3 proposals address the default recognizer case without any external dependencies, I think it would be ideal to finalise a concrete recommendation for that without getting blocked on remote recognizers.

Sorry Satish, I disagree.  Unfortunately, we all agree on the least valuable part.  There's no point recommending that.  We should either commit to solving the valuable problems, or defer the work for another year while the microphone and network specs iron out.

-----Original Message-----
From: public-xg-htmlspeech-request@w3.org [mailto:public-xg-htmlspeech-request@w3.org] On Behalf Of Satish Sampath
Sent: Wednesday, March 16, 2011 3:06 PM
To: Olli@pettay.fi
Cc: Olli Pettay; Young, Milan; Robert Brown; public-xg-htmlspeech@w3.org; Bjorn Bringert
Subject: Re: An early draft of a speech API

There is a good momentum behind the recent WHATWG proposal update for real time communication at http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#video-conferencing-and-peer-to-peer-communication.
The previous <device> tag version of this proposal was already being prototyped and implemented by various vendors in the browser space.
Notably, Opera released a prototype recently at http://my.opera.com/core/blog/2011/03/14/web-meet-device and Ericsson Labs showed a prototype in webkit at https://labs.ericsson.com/developer-community/blog/beyond-html5-implementing-device-and-stream-management-webkit.

The fact that browser vendors are getting involved in this spec proposal should encourage our XG to build upon this spec for the remote recognizer use cases. I think this would be better than the DAP device API which browser vendors have not picked up. However this proposal is still a moving target and will likely evolve quickly.

Since all 3 proposals address the default recognizer case without any external dependencies, I think it would be ideal to finalise a concrete recommendation for that without getting blocked on remote recognizers. That will allow browser vendors to implement the default recognizers without having to wait for implementations to pick up the DAP or WHATWG proposal for the audio capture part. We should of course work on the remote recognizer proposal in parallel, but I don't see why it should be a reason to gate a proposal for the simpler use case with the default recognizer.

--
Cheers
Satish
Received on Wednesday, 16 March 2011 22:16:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:16:49 UTC