On Thu, 12 Jan 2012 17:06:34 +0100, Doug Schepers wrote:
As such, the creation of tests should not be left to CR... there should
be a plan in place (e.g. a person, and a loose policy, like "as we
implement, we'll make tests and contribute them to the WG"), and a
person responsible for coll
Hi, folks-
On 1/11/12 9:40 AM, Arthur Barstow wrote:
On 1/10/12 11:25 AM, ext Glen Shires wrote:
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 w
nt: Wednesday, January 11, 2012 6:54 AM
To: Arthur Barstow
Cc: ext Glen Shires; o...@pettay.fi; public-webapps@w3.org;
public-xg-htmlspe...@w3.org; Dan Burnett; Peter Beverloo
Subject: Re: Speech Recognition and Text-to-Speech Javascript API -
seeking feedback for eventual standardization
>
> 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.
On 1/10/12 11:25 AM, ext Glen Shires wrote:
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
On Wed, 11 Jan 2012 22:36:28 +1100, Michael[tm] Smith wrote:
Satish S , 2012-01-11 10:04 +:
The Community Groups [1] page says they are for "anyone to socialize
their
ideas for the Web at the W3C for possible future standardization".
I don't think that page adequately describes the po
"Michael[tm] Smith" , 2012-01-11 20:36 +0900:
> Satish S , 2012-01-11 10:04 +:
>
> > The Community Groups [1] page says they are for "anyone to socialize their
> > ideas for the Web at the W3C for possible future standardization".
>
> I don't think that page adequately describes the potentia
Hi Michael,
Thanks for the info!
On Wed, Jan 11, 2012 at 11:36 AM, Michael[tm] Smith wrote:
> Satish S , 2012-01-11 10:04 +:
>
>> The Community Groups [1] page says they are for "anyone to socialize their
>> ideas for the Web at the W3C for possible future standardization".
>
> I don't think
Satish S , 2012-01-11 10:04 +:
> The Community Groups [1] page says they are for "anyone to socialize their
> ideas for the Web at the W3C for possible future standardization".
I don't think that page adequately describes the potential value of the
Community Group option. A CG can be used for
>
> > It doesn't matter too much to me in which group the API will be developed
> > (except that I'm against doing it in HTML WG).
> > WebApps is reasonably good place (if there won't be any IP issues.)
>
> Starting the work in a Community Group is another option to consider. A
> really good option
Olli Pettay , 2012-01-09 18:12 +0200:
> It doesn't matter too much to me in which group the API will be developed
> (except that I'm against doing it in HTML WG).
> WebApps is reasonably good place (if there won't be any IP issues.)
Starting the work in a Community Group is another option to cons
Art,
Per #2 Editor commitment(s): we confirm that Bjorn Bringert, Satish Sampath
and Glen Shires volunteer as editors. If others would like to help, we
welcome them.
Per #4 Testing commitment(s): can you elaborate on what you would like to
see at this point?
Also, what is the next step?
On Mon,
xg-htmlspe...@w3.org; Dan Burnett
Subject: Re: Speech Recognition and Text-to-Speech Javascript API -
seeking feedback for eventual standardization
On 01/09/2012 04:59 PM, Arthur Barstow wrote:
Hi All,
As I indicated in [1], WebApps already has a relatively large number
of specs in progress and
On 01/09/2012 04:59 PM, Arthur Barstow wrote:
Hi All,
As I indicated in [1], WebApps already has a relatively large number of
specs in progress and the group has agreed to add some new specs. As
such, to review any new charter addition proposals, I think we need at
least the following:
1. Relat
Hi All,
As I indicated in [1], WebApps already has a relatively large number of
specs in progress and the group has agreed to add some new specs. As
such, to review any new charter addition proposals, I think we need at
least the following:
1. Relatively clear scope of the feature(s). (This
:gshi...@google.com]
Sent: Wednesday, January 04, 2012 11:15 PM
To: public-webapps@w3.org
Cc: public-xg-htmlspe...@w3.org; Arthur Barstow; Dan Burnett
Subject: Speech Recognition and Text-to-Speech Javascript API - seeking
feedback for eventual standardization
As Dan Burnett wrote below: The HTML S
>
> 2) How does the draft incorporate with the existing
> API[1]? It seems to me as if it'd be best to define both the attribute
> as the DOM APIs in a single specification, also because they share
> several events (yet don't seem to be interchangeable) and the
> attribute already has an implement
Hi Glen et al.,
I'd like to share two pieces of feedback which came to mind when
reading through the unofficial draft.
1) The primary interfaces are abbreviated as "TTS" and "SpeechReco".
Personally I believe it'd be clearer for authors when these would be
defined as "TextToSpeech" and "SpeechRec
As Dan Burnett wrote below: The HTML Speech Incubator Group [1] has
recently wrapped up its work on use cases, requirements, and proposals for
adding automatic speech recognition (ASR) and text-to-speech (TTS)
capabilities to HTML. The work of the group is documented in the group's
Final Report. [
19 matches
Mail list logo
