W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

Re: Speech Recognition and Text-to-Speech Javascript API - seeking feedback for eventual standardization

From: Satish S <satish@google.com>
Date: Wed, 11 Jan 2012 14:54:05 +0000
Message-ID: <CAHZf7RnXYEYxDHByu7cKSVsY-wFmp-cU-Z_RZt=fTcyxce9QAw@mail.gmail.com>
To: Arthur Barstow <art.barstow@nokia.com>
Cc: ext Glen Shires <gshires@google.com>, olli@pettay.fi, public-webapps@w3.org, public-xg-htmlspeech@w3.org, Dan Burnett <dburnett@voxeo.com>, Peter Beverloo <peter@chromium.org>
>
> Per #4 Testing commitment(s): can you elaborate on what you would like to
>> see at this point?
>>
>
> At this point, I think a `warm fuzzy` like "if/when the spec advances to
> Candidate Recommendation, we will contribute to a test suite that is
> sufficient to exit the CR" would be useful.


Yes we will contribute to a test suite that is sufficient for the Candidate
Recommendation.


> Also, what is the next step?
>>
>
> WRT the API you proposed, I think we have enough preliminary feedback for
> me to start a CfC to add the API to WebApps charter. My only concern is the
> open question (at least to me) re the markup part. It seems like it would
> be useful to review the proposed API and markup together. However, a CfC
> for the markup can be done separately (provided sufficient
> interest/commitment is expressed).
>

In the spirit of starting with the basics and iterating we did not include
markup in the proposed API. Markup support also renders cleanly as a layer
on top of the JS API with few additions, so as you suggest if there is
sufficient interest/commitment a separate CfC could be done.
Received on Wednesday, 11 January 2012 15:20:37 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:49 GMT