- From: Satish Sampath <satish@google.com>
- Date: Thu, 9 Sep 2010 16:55:23 +0100
- To: "Eric S. Johansson" <esj@harvee.org>
- Cc: public-xg-htmlspeech@w3.org
>> - Web app developers should not have to run their own speech >> recognition services. > > Nor should they be excluded from running their own speech recognition > services For reasons of privacy. I dictate confidential information. I don't > want anything concerning my dictations leaving my machine. I think these two points are about different things. The first is about the web app developer not being forced to run and specify a recognition server for each use of speech recognition in html, whereas the second seems to be about allowing the UA to interface with a speech recognizer present in the local machine. Is that correct? > For reasons of privacy, the user should not be forced to store anything > about their speech recognition environment on the cloud. I think this is satisfied if as mentioned above the UA can interface with a local recognizer so the speech data doesn't have to be sent over to a server. > I see no mention of retrieval of contents of a text area for editing > purposes. Look at NaturallySpeaking's Select-and-Say functionality. It works > very nicely for small grain text editing. I'm also experimenting with speech > user interfaces for non-English text dictation. The basic model is selected > region by speech, run the selected region through transformation, edit the > transformed text by speech, run text through reverse transform and replace > selected region with new text. This seems related to a global voice IME than a speech aware/enabled web application, i.e. using voice to dictate text and select+edit portions of it should be possible in any web page, rather than just in pages which have speech-enabled features. However I can see complex web apps such as email clients which use speech input for command-and-edit cases (such as "Change subject to 'Pictures from our recent trip'" or "In subject change 'recent trip' to 'hawaii trip'") and these could be implemented by the web app. -- Cheers Satish
Received on Thursday, 9 September 2010 15:55:54 UTC