On Tuesday, February 08, 2011 2:09:08 pm Chris Davis wrote:
> >> Why would the MRCP server be providing a semantic interpretation of its
> >> own
>
> That's just Nuance.
>
> >>How should a conforming VoiceXML interpreter handle cases like this?
>
> use the SWI_meaning tag and pull out the value as the semantic
> interpretation.
> so.. the following:
>
> <SWI_meaning>
> {SWI_literal:1 2 3 4}
> </SWI_meaning>
>
> results in the input var being:
>
> "1 2 3 4"
So change behaviour such that (spec in black, changes in red):
A field-level result fills the associated input item in the following manner:
1. If the interpretation is a simple result, this is assigned to the input
item variable.
2. If the interpretation is a structure and the slot name matches a property,
this property's value is assigned to the input item variable.
3. If the interpretation is a structure and has a "SWI_meaning" property,
parse that property as a JSON interpretation, and go to step 1.
4. If the interpretation contains only a single "SWI_literal" property, this
property's value is assigned to the input item variable.
5. Otherwise, the full semantic result is assigned.
Correct?
Thanks,
Luke