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

Re: Request to change WebSpeech to remove usage of SpeechSynthesisVoiceList

From: ᛏᚮᛘᛘᚤ <tommyw@google.com>
Date: Wed, 6 Feb 2013 16:01:30 +0100
Message-ID: <CALLKCfNrnpYEYAksuh0=Rsr3T0J5p2VQKDEE7YOazsMthjSnDw@mail.gmail.com>
To: Glen Shires <gshires@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>
FYI the "Media Capture and Streams" spec did this with MediaStream and
MediaStreamtrackList and it turned out OK imho.


On Tue, Feb 5, 2013 at 7:56 AM, Glen Shires <gshires@google.com> wrote:

> 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 Wednesday, 6 February 2013 15:01:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 6 February 2013 15:01:57 GMT