W3C home > Mailing lists > Public > public-speech-api@w3.org > February 2013

Re: Request to change WebSpeech to remove usage of SpeechSynthesisVoiceList

From: Glen Shires <gshires@google.com>
Date: Mon, 4 Feb 2013 22:56:13 -0800
Message-ID: <CAEE5bcj4udhc4U8h3kCmBO-HFAQ_SCcwSemU_5m4+4ScM7-8-w@mail.gmail.com>
To: Tommy Widenflycht (ᛏᚮᛘᛘᚤ) <tommyw@google.com>
Cc: Hans Wennborg <hwennborg@google.com>, Chris Fleizach <cfleizach@apple.com>, "public-speech-api@w3.org" <public-speech-api@w3.org>, James Craig <jcraig@apple.com>
One option for a similar change to SpeechGrammarList is to move its methods
to its parent as shown below.

Remove SpeechRecognitionResultList and change:

interface SpeechRecognition : EventTarget {
        attribute sequence<SpeechGrammar> grammars;

        void addGrammarFromURI(in DOMString src, optional float weight);
        void addGrammarFromString(in DOMString string, optional float
weight);
        ...
}


However, I prefer the current syntax because the encapsulation of methods
is cleaner.  Any thoughts or other proposals?

/Glen Shires


On Mon, Feb 4, 2013 at 10:36 PM, Glen Shires <gshires@google.com> wrote:

> I've updated the errata with the above change:
> https://dvcs.w3.org/hg/speech-api/rev/58e2afd5d423
>
> As always, the current errata is at:
> http://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi-errata.html
>
>
> Should we consider a similar change to SpeechGrammarList? (It's not as
> straight-forward because the object has methods.) Any proposals?
>
> /Glen Shires
>
>
> On Tue, Jan 22, 2013 at 3:43 PM, Glen Shires <gshires@google.com> wrote:
>
>> I agree, this makes for a cleaner, more modern IDL and doesn't affect the
>> JavaScript syntax.  So unless there is disagreement, I will add the
>> following to the errata on Feb 4.
>>
>> Remove SpeechSynthesisVoiceList and change:
>>
>> interface SpeechSynthesis {
>>         sequence<SpeechSynthesisVoice> getVoices();
>> };
>>
>> Remove SpeechRecognitionResultList and change:
>>
>> interface SpeechRecognitionEvent : Event {
>>         readonly attribute sequence<SpeechRecognitionResult> results;
>> };
>>
>>
>>
>> Also, we might consider a similar change to SpeechGrammarList, but it's
>> not as straight-forward because this object has methods. Any proposals?
>>
>> Glen
>>
>>
>> On Thu, Jan 17, 2013 at 12:34 AM, Tommy Widenflycht (ᛏᚮᛘᛘᚤ) <
>> tommyw@google.com> wrote:
>>
>>> Yeah, I am doing exactly the same to the WebRTC stuff in WebKit. The
>>> recentish support for sequence<> in WebKit rocks. And the change
>>> wouldn't break anything either.
>>>
>>> /Tommy
>>>
>>>
>>> On Thu, Jan 17, 2013 at 9:27 AM, Hans Wennborg <hwennborg@google.com>
>>> wrote:
>>> > On Wed, Jan 16, 2013 at 9:19 PM, Chris Fleizach <cfleizach@apple.com>
>>> wrote:
>>> >> Hi,
>>> >>
>>> >> I think that instead of using the custom SpeechSynthesisVoiceList
>>> object, we can use a normative Javascript array to return the list of voices
>>> >> in getVoices().
>>> >>
>>> >> The IDL change would change from
>>> >>
>>> >> interface SpeechSynthesis {
>>> >>         SpeechSynthesisVoiceList getVoices();
>>> >> };
>>> >>
>>> >> to
>>> >>
>>> >> interface SpeechSynthesis {
>>> >>         sequence<SpeechSynthesisVoice> getVoices();
>>> >> };
>>> >>
>>> >> Then the SpeechSynthesisVoiceList can be removed.
>>> >>
>>> >> Thanks for your consideration
>>> >
>>> > +tommyw
>>> >
>>> > I guess this would apply to the other lists in the spec too? I.e.
>>> > SpeechGrammarList and SpeechRecognitionResultList?
>>> >
>>> > Seems like this would both simplify the spec and implementation a bit.
>>> >
>>> > Thanks,
>>> > Hans
>>>
>>>
>>
>
Received on Tuesday, 5 February 2013 06:57:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 5 February 2013 06:57:31 GMT