W3C home > Mailing lists > Public > public-xg-htmlspeech@w3.org > September 2011

Re: how to send metadata INFO messages from the API

From: JOHNSTON, MICHAEL J (MICHAEL J) <johnston@research.att.com>
Date: Thu, 15 Sep 2011 14:25:53 -0400
To: HTML Speech XG <public-xg-htmlspeech@w3.org>
Message-ID: <B76C3A5D-8480-43E1-A340-65A1A3548313@research.att.com>
Sorry that should be:

> interface SpeechInputRequest {
> 
> .....
> 
> void sendinfo(in DOMstring info);
> 
> .....

On Sep 15, 2011, at 1:51 PM, JOHNSTON, MICHAEL J (MICHAEL J) wrote:

> One thing I see missing from the API draft is support for the INFO messages for
> sending metadata to the recognizer during recognition.
> 
> In the html+speech protocol we have a generic capability to send metadata to the recognizer, the
> relevant reco-method is INFO (see below).   These messages can be sent during the transmission of
> audio.  This covers multimodal use cases where there may be metadata (e.g. GUI actions, button clicks etc)
> that take place while the user is speaking, which are relevant for processing the user's audio.
> 
> To support this at the API level we need some kind of method on SpeechInputRequest that
> will cause the INFO message to be sent over the protocol.
> 
> e.g.
> 
> interface SpeechInputRequest {
> 
> .....
> 
> void sendinfo(in DOMstring info);
> 
> .....
> 
> 
> Michael
> 
> 
> 
> 
> 
> reco-method  = "LISTEN"             ; Transitions Idle -> Listening
>             | "START-INPUT-TIMERS" ; Starts the timer for the various input timeout conditions
>             | "STOP"               ; Transitions Listening -> Idle
>             | "DEFINE-GRAMMAR"     ; Pre-loads & compiles a grammar, assigns a temporary URI for reference in other methods
>             | "CLEAR-GRAMMARS"     ; Unloads all grammars, whether active or inactive
>             | "INTERPRET"          ; Interprets input text as though it was spoken
>             | "INFO"               ; Sends metadata to the recognizer
> 
> INFO
> 
> In multimodal applications, some recognizers will benefit from additional context. Clients can use the INFO request to send this context. The Content-Type header should specify the type of data, and the data itself is contained in the message body.
> 
> 
Received on Thursday, 15 September 2011 18:25:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 15 September 2011 18:25:48 GMT