W3C home > Mailing lists > Public > public-xg-htmlspeech@w3.org > October 2011

Re: Proposal for <reco> tag

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Thu, 06 Oct 2011 18:30:48 +0300
Message-ID: <4E8DC9A8.4020007@helsinki.fi>
To: Glen Shires <gshires@google.com>
CC: public-xg-htmlspeech@w3.org
On 10/04/2011 08:56 PM, Glen Shires wrote:
> Some of the goals for the <reco> tag that have been discussed in this
> group are:
>
> 1. Make it easy for developers, at least "keep the simple things simple".
>      Even though he was discussing the <tts> tag, many of the considerations
>      that Charles listed also apply to <reco>
> http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Jul/0027.html
>
>         - Helps the API be more declarative.
>         - Can control features through the standard DOM
>         - Better for standard HTML developers (the main target?)

What is "standard HTML developers"? :)

>         - Provides a standard place to add event handlers.
>         - Allows for visual control (examples: listening indicator,
> cancel button)
>         - Can support GUI related interaction considerations: focus and
> visibility.
Need to be careful with click-jacking related problems.


>
> 2. Enable a markup-affordance-based permissions model (click to speak)
Click-to-speak can or cannot be a "permission model".


  as
>      Satish describes.
> http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Sep/0019.html.
>      Preventing click-jacking is important if this is to be used for as
> one of the
>      permissions models.  Olli and Satish have described ways to handle
> this:
> http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Jul/0004.html
>
> 3.  From the User/UI perspective, the <reco> tag can show a visual indicator
>      (for example, an icon of a microphone) that:
>         - Provides an indication to the user that speech input can be
> used for these fields.
>         - By clicking on the icon, the user can simultaneously indicate
> which field he
>           wishes to speak into, and that he grants permission for audio
> to be captured.
This is a click-jacking problem.



>
> I believe the following proposal achieves all of these goals.
>
> The <reco> tag would have attributes that mirror most of the attributes,
> event-attributes and methods of the SpeechInputService. For example:
>
> <reco continuous="true" languages="en-AU" grammars="<builtin:datetime>"
>           onresult="processResult()"/>
>
> A comma-separated list of items can also be specified, for example:
>
> <reco continuous="true" languages="en-AU, en-GB"
>           grammars="<builtin:datetime>, http://example.com/mygrammar.xml">
>
> The reco tag would not explicitly bind to input fields or other tags,
> instead it would use simple javascript to achieve this.  Keeping the
> "keeping simple things simple" mindset, bindings can be achieved with
> inline javascript code that developers can easily cut-and-paste along
> with the rest of the markup.  See attached html file for examples.
Yeah, I like this kind of approach. Binding using javascript is trivial.


  (If
> you open this html file in Chrome, the examples are functional...click
> on the microphone icon to see them in action. I've emulated the reco tag
> using Chrome's current experimental syntax.
(IMO Chrome behavior has one form of click-jacking problem)



   I've also attached a
> screenshot in case you don't have Chrome handy.)  The use of javascript
> also provides the flexibility to enable advanced developers to create
> complex interactions, while keeping the browser implementation and
> syntax simple.
Yup.

Though, permission handling isn't clear yet.
User should somehow give permission to web page, and web page should
also get notified if user denies the permission so that speech UI 
related GUI parts can be hidden.




-Olli

>
> While these examples are not purely declarative in the strict sense,
> they achieve the spirit of this goal in that developers can easily
> specify speech input, without having to connect multiple diverse
> sections of the file together (they don't have to connect the javascript
> section of the file to the html markup section). Instead, developers can
> use the common practice of copying snippets of markup to "keep the
> simple things simple".
>
Received on Thursday, 6 October 2011 15:31:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 6 October 2011 15:31:16 GMT