- From: Bjorn Bringert <bringert@google.com>
- Date: Wed, 8 Dec 2010 15:37:54 +0000
- To: Olli@pettay.fi
- Cc: Dan Burnett <dburnett@voxeo.com>, public-xg-htmlspeech@w3.org
As Olli says, this requirement can't be fully compatible with our requirements that the user must be notified when recording occurs. If the web app could customize everything about the recognition UI, it could make the notification invisible. /Bjorn On Wed, Dec 8, 2010 at 11:35 AM, Olli Pettay <Olli.Pettay@helsinki.fi> wrote: > Because of possible security reasons, some customization may not be > possible, some may. > In other words, web app author must not be able to control everything in > the speech GUI. > > R13 has two parts. One is the "include a clickable graphic to invoke speech > recognition", the other one is "indicate the progress of the recognition > through various states". > It is the first one which *may* need to be limited a bit. > And the latter one is already implicitly handled in the requirement for > different kinds of events. > > -Olli > > > On 12/08/2010 12:39 PM, Dan Burnett 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 13 [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/0024.html >> [2] >> >> http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2010Oct/att-0001/speech.html#r13 >> >> >> >> > > > -- Bjorn Bringert Google UK Limited, Registered Office: Belgrave House, 76 Buckingham Palace Road, London, SW1W 9TQ Registered in England Number: 3977902
Received on Wednesday, 8 December 2010 15:38:24 UTC