- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Tue, 23 Nov 2010 16:24:26 +0200
- To: Bjorn Bringert <bringert@google.com>
- CC: Deborah Dahl <dahl@conversational-technologies.com>, Olli@pettay.fi, public-xg-htmlspeech@w3.org
On 11/23/2010 04:10 PM, Bjorn Bringert wrote: > Sounds good to me. Did s/page/app/ for consistency with other requirements: > > "When speech input is used to provide input to a web app, it should be > possible for the user to select alternative input methods." Sounds good. -Olli > > On Tue, Nov 23, 2010 at 1:55 PM, Deborah Dahl > <dahl@conversational-technologies.com> wrote: >> Yes, that seems to capture the idea, although perhaps we could make it more generic and not tie it specifically to filling input fields. >> >> "When speech input is used to provide input to a web page, it should be >> possible for the user to select alternative input methods." >> >>> -----Original Message----- >>> From: Bjorn Bringert [mailto:bringert@google.com] >>> Sent: Tuesday, November 23, 2010 7:11 AM >>> To: Deborah Dahl >>> Cc: Olli@pettay.fi; public-xg-htmlspeech@w3.org >>> Subject: Re: R23. Speech as an input on any application should be able to be >>> optional >>> >>> Ok, so how about this? >>> >>> "When speech input is used to fill an input field, it should be >>> possible for the user to select alternative input methods." >>> >>> /Bjorn >>> >>> On Mon, Nov 22, 2010 at 2:42 PM, Deborah Dahl >>> <dahl@conversational-technologies.com> wrote: >>>> I think the point of the requirement is that our spec should not do anything >>> that means that speech is required to be used for a specific input. We can't >>> prevent webapps from disabling mouse and keyboard input because that's >>> outside of the scope of our work. I think this is similar to our requirements >>> around raw audio capture. It might be possible to capture raw audio (for >>> example, using the Media Capture API http://www.w3.org/TR/media- >>> capture-api/) in ways that have nothing to do with our spec, but that doesn't >>> mean we shouldn't have appropriate safeguards in our spec. >>>> >>>>> -----Original Message----- >>>>> From: public-xg-htmlspeech-request@w3.org [mailto:public-xg- >>> htmlspeech- >>>>> request@w3.org] On Behalf Of Olli Pettay >>>>> Sent: Monday, November 22, 2010 7:19 AM >>>>> To: Bjorn Bringert >>>>> Cc: public-xg-htmlspeech@w3.org >>>>> Subject: Re: R23. Speech as an input on any application should be able to >>> be >>>>> optional >>>>> >>>>> On 11/18/2010 08:36 PM, Bjorn Bringert wrote: >>>>>> This doesn't seem like a requirement on the API, but a requirement on >>>>>> how application authors use it. >>>>> >>>>> >>>>> I agree. Webapps can always effectively disable all the mouse and >>>>> keyboard input if they really want to and require speech. >>>>> That would be a silly app, but I don't see any way to prevent it. >>>>> >>>>> >>>>> -Olli >>>>> >>>>>> >>>>>> /Bjorn >>>>>> >>>>>> On Thu, Nov 18, 2010 at 5:37 PM, 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 23 [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#r23 >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Bjorn Bringert >>> Google UK Limited, Registered Office: Belgrave House, 76 Buckingham >>> Palace Road, London, SW1W 9TQ >>> Registered in England Number: 3977902 >> >> > > >
Received on Tuesday, 23 November 2010 14:25:13 UTC