- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Wed, 08 Sep 2010 23:06:00 +0300
- To: "JOHNSTON, MICHAEL J (MICHAEL J)" <johnston@research.att.com>
- CC: "public-xg-htmlspeech@w3.org" <public-xg-htmlspeech@w3.org>
On 09/08/2010 10:50 PM, JOHNSTON, MICHAEL J (MICHAEL J) 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. Sounds reasonable. Web app might want to process the microphone input data somehow before pushing it to recognizer. https://wiki.mozilla.org/Audio_Data_API > 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. Oh, you seem to want to support remote speech recognizers? Why would we need to define this all this way. If the speech input can be captured as data by the web page, it can stream the data using XMLHttpRequest or WebSockets to server. -Olli > > 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 Wednesday, 8 September 2010 20:06:33 UTC