- From: Dave Burke <daveburke@google.com>
- Date: Thu, 9 Sep 2010 23:10:05 +0100
- To: "JOHNSTON, MICHAEL J (MICHAEL J)" <johnston@research.att.com>
- Cc: "public-xg-htmlspeech@w3.org" <public-xg-htmlspeech@w3.org>
- Message-ID: <AANLkTi=i-8kaJuaFjRPYwCxR3+gMG5ery-GSCBD8i9CB@mail.gmail.com>
I think selection of the speech engine should be a user-setting in the browser, not a Web developer setting. We had a similar conversation in Geolocation where some folks wanted a URI to point to a specific location server. We rightly removed it. Also, the security bar is much higher for an audio recording solution that can be pointed at an arbitrary destination for obvious reasons. Dave On Wed, Sep 8, 2010 at 8:50 PM, JOHNSTON, MICHAEL J (MICHAEL J) < johnston@research.att.com> wrote: > > Here is one of the specific requirements we have for adding speech to HTML: > > Requirement: > > The HTML+Speech standard must allow specification of the speech resource > (e.g. speech recognizer) to be used for processing of the audio > collected from the user. For example, this could be specified > as URI valued attribute on the element supporting speech recognition. > When audio is captured from the user it will then be streamed over http > to the specified URI. > > best > Michael > > > > > > > ======================================= > > REQUIREMENTS, USE CASES, and PROPOSALS > > ======================================= > > I think the best way to begin is to ask right up front for the items we > are interested in: requirements, use cases, and proposals for changes to > HTML. > > > > If you have requirements, use cases, or proposals for changes to HTML, > please send them in to this list. When the trickle slows we'll look at what > we have and decide on next steps. For expediency, please plan to send in > any such materials by Monday, September 13. > > > >
Received on Thursday, 9 September 2010 22:11:19 UTC