- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Mon, 01 Nov 2010 23:45:36 +0100
- To: Satish Sampath <satish@google.com>
- CC: public-xg-htmlspeech@w3.org
On 10/29/2010 05:08 PM, Satish Sampath wrote: > Thanks Dan. > > Regarding the API proposal from Google at > http://www.w3.org/2005/Incubator/htmlspeech/2010/10/google-api-draft.html, > this is derived from our earlier API document which was posted in this list. > > The main changes in the latest API include: > - is simpler in some areas such as error management > - focuses only on a small subset of input element types which text input > - we have added the ability for the web page to give feedback on the > recognition quality. For e.g. user can view all the hypotheses and > select a different result as their top match. > - formatted in W3C draft style for easier reading. > > We are happy to discuss the latest proposal over email as well if there > are comments before the F2F. Few *random* comments about the proposal. In the examples the code <input ... onspeechchange="startSearch"> doesn't work. It should be <input ... onspeechchange="startSearch(event)"> I wonder which syntax of SRGS we should be using. In the old days I've used ABNF, and I think it is easier to write it by hand than the XML form. XML form is probably easier for some tools. Though, there are probably tools to convert XML->ABNF and vice versa. But anyway, if we're going to use SRGS, we need to specify which form the content author can use. I don't quite understand why you have decided to bind speech results automatically some seemingly random input element types. Why not just have something more generic and let the page author to set the value to whatever element she/he wants to. Making the classical "multimodal pizza" example to work using the proposal would need some hacks; first get the value to some input element, and using script set the value of checkboxes and radiobuttons. Related to this, 5.6 is a bit odd. Why should input element work differently than textarea? Even if there was automatic speech recognition result binding to input element, I'd assume, that for example saying a phone number, number by number, should work. I don't quite understand SpeechInputResultCollection.feedback(). What is the use case for that? 'continue' may cause some UI problems. The UI must do something like start the recognition when there is a mousedown, and stop it when there is mouseup. Otherwise user might not realize that the recognizer is on; for example if someone interrupts the user so that she/he doesn't look at the screen for awhile and doesn't notice that the recognizer is running. About grammars. The proposal seems to allow only one active grammar. I think allowing more could be useful for content authors. They could reuse some generic grammars, and then have some hopefully smaller application specific grammar. br, -Olli > > Cheers > Satish > > > On Fri, Oct 29, 2010 at 1:42 AM, Dan Burnett <dburnett@voxeo.com > <mailto:dburnett@voxeo.com>> wrote: > > Group, > > Here is the agenda for our meeting(s). It's fairly high-level > because we won't know in advance which requirements require the most > time for discussion. We will discuss the requirements we have > already agreed need live discussion (#29 so far), then continue > through the other requirements as described in last week's email [1] > and get as far as we can. > > Note that there is a time slot below when Google would like to > present their API proposal [2] for background. If anyone else has a > proposal they'd like to show we can extend that time slot by up to > 30 minutes and distribute the time evenly among the presenters. > > -- dan > > [1] > http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2010Oct/0024.html > > > ========================= > = Tuesday, 2 November 2010 = > ========================= > (currently assigned to be in Saint Clair 3A -- Level 2 -- Saint Clair) > 1400-1530 Session 1 > > 1400-1415 Welcome and Introductions > 1415-1530 Requirements > > 1530-1600 Break > 1600-1800 Session 2 > > 1600-1630 Google presents their API proposal > (http://www.w3.org/2005/Incubator/htmlspeech/2010/10/google-api-draft.html) > 1630-1800 Requirements (continued) > > > ========================= > = Thursday, 4 November 2010 = > ========================= > (currently assigned to be in Saint Clair 2 -- Level 2 -- Saint Clair) > 0830-1030 Session 1: Requirements (continued) > > 1030-1100 Break > 1100-1230 Session 2 > > 1100-1145 Requirements (continued) > 1145-1230 Planning/next steps > > > > >
Received on Monday, 1 November 2010 22:46:15 UTC