Re: SpeechRecognitionAlternative.interpretation when interpretation can't be provided from Conversational on 2012-08-15 (public-speech-api@w3.org from August 2012)

From: Conversational <dahl@conversational-technologies.com>
Date: Wed, 15 Aug 2012 09:19:38 -0400
To: Hans Wennborg <hwennborg@google.com>
Cc: "public-speech-api@w3.org" <public-speech-api@w3.org>
Message-Id: <121B4C10-0561-45DD-A625-EB9CEAD46247@conversational-technologies.com>

If there isn't an interpretation I think it would make the most sense for the attribute to contain the literal string result. I believe this is what happens in VoiceXML. 

Sent from my iPhone

On Aug 15, 2012, at 9:04 AM, Hans Wennborg <hwennborg@google.com> wrote:

> Hi all,
> 
> For the interpretation attribute, the spec draft currently says:
> 
> "The interpretation represents the semantic meaning from what the user
> said. This might be determined, for instance, through the SISR
> specification of semantics in a grammar."
> 
> My question is: for implementations that cannot provide an
> interpretation, what should the attribute's value be? null? undefined?
> 
> Thanks,
> Hans
> 
>

Received on Wednesday, 15 August 2012 13:20:09 UTC