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

Re: CfC: to add Speech API to Charter; deadline January 24

From: Glen Shires <gshires@google.com>
Date: Fri, 20 Jan 2012 09:37:35 -0800
Message-ID: <CAEE5bchB-roTdCnnMSFyChxXfTE27tzW=Urod03F3pmLjv=wVg@mail.gmail.com>
To: Arthur Barstow <art.barstow@nokia.com>
Cc: public-webapps <public-webapps@w3.org>, Adrian Bateman <adrianba@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, public-xg-htmlspeech@w3.org
Some of the reasons we believe that the JavaScript Speech API is best
suited for WebApps, instead of it's own working group, include:

1. Speech is likely to become a core API, like other WebApps deliverables
such as File API. It is important that it be compatible and consistent
with, and interact well with other JavaScript API components.  In
particular, speech provides a new method for accepting user input,
producing user output and interacting with the features, and controlling
the flow, of other JavaScript API components.

2. WebApps provides a balanced web-centric view for new JavaScript APIs.
 The XG group consisted of a large number of speech experts, but only a few
with broad web API expertise. We believe the formation of a new WG would
have a similar imbalance, whereas the WebApps WG can provide valuable,
balanced guidance and feedback.

3. The scope of this effort is well-defined and bounded. All that have
responded to this CfC have agreed that JavaScript API portions of the XG
Final Report are relevant to WebApps, and that the wire protocol portions
of the XG Final Report are not relevant to WebApps (and should be pursued
in another group, such as IETF).  The differing opinions seem only about
the specific starting point of this effort, whether to base it on the full
JavaScript API in the XG's Final Report [1] or a subset of that JavaScript
API, which supports the majority of use cases, as proposed by Google [2].
 For this first recommendation-track document, we believe a subset will
accelerate implementation, interoperability testing, standardization and
ultimately developer adoption. However, in the spirit of consensus, we are
willing to broaden this subset to include additional API features in the XG
Final Report.

[1] http://www.w3.org/2005/Incubator/htmlspeech/XGR-htmlspeech/
[2]
http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/att-1696/speechapi.html

Bjorn Bringert
Satish Sampath
Glen Shires


On Fri, Jan 20, 2012 at 3:58 AM, Arthur Barstow <art.barstow@nokia.com>wrote:

> The deadline for comments is extended to January *24*.
>
>
> On 1/20/12 6:55 AM, ext Arthur Barstow wrote:
>
>> The deadline for comments is extended to January.
>>
>> Andrian, Maciej - I would appreciate it you would please provide some
>> feedback on this CfC.
>>
>> On 1/12/12 7:31 AM, ext Arthur Barstow wrote:
>>
>>> Glen Shires and some others at Google proposed [1] that WebApps add
>>> Speech API to WebApps' charter and they put forward the Speech Javascript
>>> API Specification [2] as as a starting point. Members of Mozilla and Nuance
>>> have voiced various levels of support for this proposal. As such, this is a
>>> Call for Consensus to add Speech API to WebApps' charter.
>>>
>>> Positive response to this CfC is preferred and encouraged and silence
>>> will be considered as agreeing with the proposal. The deadline for comments
>>> is January 19 and all comments should be sent to public-webapps at
>>> w3.org.
>>>
>>> -AB
>>>
>>> [1] http://lists.w3.org/Archives/**Public/public-webapps/**
>>> 2011OctDec/1696.html<http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/1696.html>
>>> [2] http://lists.w3.org/Archives/**Public/public-webapps/**
>>> 2011OctDec/att-1696/speechapi.**html<http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/att-1696/speechapi.html>
>>>
>>>
>>
>
Received on Friday, 20 January 2012 17:38:44 GMT

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