On Wed, 25 Jan 2012 00:47:45 +0100, Glen Shires gshi...@google.com wrote:
Art, Charles,
We are very pleased to see the positive responses to the CfC.
Me too. FWIW Opera is happy to have this work done. We think it would
ideally be a joint deliverable (despite the fact that we don't like
On Jan 23, 2012, at 12:39 PM, Arthur Barstow wrote:
On 1/23/12 12:17 PM, ext Charles McCathieNevile wrote:
On Fri, 20 Jan 2012 18:37:35 +0100, Glen Shires gshi...@google.com wrote:
2. WebApps provides a balanced web-centric view for new JavaScript APIs.
The XG group consisted of a large
Microsoft is open to adding this to the WebApps charter.
We certainly want to see work on a speech API for user agents proceed at W3C.
Our priorities for the API are 1) a procedural (JavaScript) API and 2) a
declarative syntax for speech recognition and text-to-speech in HTML. We think
WebApps
On Jan 24, 2012, at 7:50 AM, Dan Burnett wrote:
On Jan 23, 2012, at 12:39 PM, Arthur Barstow wrote:
On 1/23/12 12:17 PM, ext Charles McCathieNevile wrote:
On Fri, 20 Jan 2012 18:37:35 +0100, Glen Shires gshi...@google.com wrote:
2. WebApps provides a balanced web-centric view for new
Art, Charles,
We are very pleased to see the positive responses to the CfC.
In particular, we believe this meets all the criteria that Art suggested in
[1].
1. Relatively clear scope of the feature(s)
The scope is well-defined and bounded. [1] [2]
2. Editor commitment(s)
Google and
On Fri, 20 Jan 2012 18:37:35 +0100, Glen Shires gshi...@google.com wrote:
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
On 1/23/12 12:17 PM, ext Charles McCathieNevile wrote:
On Fri, 20 Jan 2012 18:37:35 +0100, Glen Shires gshi...@google.com
wrote:
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
Barstow [mailto:art.bars...@nokia.com]
Sent: Monday, January 23, 2012 12:39 PM
To: ext Charles McCathieNevile; Glen Shires; Deborah Dahl; Scott
McGlashan;
Kazuyuki Ashimura
Cc: public-webapps; public-xg-htmlspe...@w3.org
Subject: Re: CfC: to add Speech API to Charter; deadline January 24
On 1/23
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
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:
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
11 matches
Mail list logo
