W3C home > Mailing lists > Public > public-speech-api@w3.org > May 2012

Re: Custom parameters

From: Satish S <satish@google.com>
Date: Thu, 10 May 2012 22:02:27 +0100
Message-ID: <CAHZf7RkqBV_+LVhqgL+htx4ycFdRRZ+NFWF04nBtge2unwMULQ@mail.gmail.com>
To: Glen Shires <gshires@google.com>
Cc: public-speech-api@w3.org
Yes. serviceURI in itself has a lot of custom fields such as the URI scheme
and parts in the URI and custom parameters will fit with that well. Some
recognizers may prefer a REST like convention and others may use name/value
pairs in the URI.

Cheers
Satish


On Thu, May 10, 2012 at 3:31 PM, Glen Shires <gshires@google.com> wrote:

> Note that the serviceURI can be used to point to local or remote services,
> so it could be used to pass custom parameters to either local or remote
> services.
>
> On Thu, May 10, 2012 at 2:02 AM, Satish S <satish@google.com> wrote:
>
>> - void setCustomParameter(in DOMString name, in DOMString value);
>>> - attribute SpeechParameterList parameters;
>>
>>
>> I see custom parameters being useful in the custom recognizer case but
>> not for the default case. Since custom recognizers are most useful in the
>> remote  service scenario (because local custom recognizers aren't
>> guaranteed to be present in every user machine) and the remote service
>> protocol is out of our scope, I think we should remove these from the
>> SpeechRecognition interface and add later if required when the protocol is
>> ready and it is clear how parameters would be passed to the remote
>> recognizers.
>>
>> Web apps can also pass custom parameters as url parameters in the
>> serviceUri attribute.
>>
>> Cheers
>> Satish
>>
>> On Thu, May 10, 2012 at 7:30 AM, Glen Shires <gshires@google.com> wrote:
>>
>>> I've added to the draft spec the features/changes for which we have
>>> reached a consensus. Namely:
>>>
>>> - attribute integer maxNBest;
>>> - attribute DOMString serviceURI;
>>> - void setCustomParameter(in DOMString name, in DOMString value);
>>> - attribute SpeechParameterList parameters;
>>>
>>> We welcome discussion and feedback on this editor's draft.
>>> Please send your comments to the public-speech-api@w3.org mailing list,
>>> and please use a new subject line for each new topic, so that the threads
>>> are easier to follow.
>>>
>>> Full draft: http://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html
>>> Diffs: http://dvcs.w3.org/hg/speech-api/rev/067f706eef96**
>>>
>>> Glen Shires
>>>
>>>
>>
>
Received on Thursday, 10 May 2012 21:02:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 10 May 2012 21:02:58 GMT