RE: R5. Web application must be notified when speech recognition errors and other non-matches occur.

It seems that we have consensus to leave this in as is.

I'm a little unsure that it is clear to say "speech recognition errors and other non-matches" as we may want to distinguish between no matches versus no input versus actual errors (I.e., bad grammars/configuration).  Perhaps we can talk about wording on the call?

-----Original Message-----
From: public-xg-htmlspeech-request@w3.org [mailto:public-xg-htmlspeech-request@w3.org] On Behalf Of Satish Sampath
Sent: Tuesday, November 16, 2010 9:57 AM
To: Olli@pettay.fi
Cc: public-xg-htmlspeech@w3.org
Subject: Re: R5. Web application must be notified when speech recognition errors and other non-matches occur.

Yes, keep as is.

Cheers
Satish



On Tue, Nov 16, 2010 at 11:03 AM, Olli Pettay <Olli.Pettay@helsinki.fi> wrote:
> On 11/16/2010 12:53 PM, Bjorn Bringert wrote:
>>
>> Keep.
>>
>
> Keep.
>
>
> -Olli
>
>
>
>> On Tue, Nov 16, 2010 at 10:51 AM, Dan Burnett<dburnett@voxeo.com>  wrote:
>>>
>>> Group,
>>>
>>> This is the next of the requirements to discuss and prioritize based 
>>> on our ranking approach [1].
>>>
>>> This email is the beginning of a thread for questions, discussion, 
>>> and opinions regarding our first draft of Requirement 5 [2].
>>>
>>> Please discuss via email as we agreed at the Lyon f2f meeting.
>>>  Outstanding
>>> points of contention will be discussed live at an upcoming 
>>> teleconference.
>>>
>>> -- dan
>>>
>>> [1]
>>>
>>> http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2010Oct/002
>>> 4.html
>>> [2]
>>>
>>> http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2010Oct/att
>>> -0001/speech.html#r5
>>>
>>>
>>
>>
>>
>
>
>

Received on Thursday, 18 November 2010 09:01:06 UTC