This document was generated from CDN thread
Created by: null on 02-10-2003 09:42:52 PM
Hi,
I am using Audium 3.3. Now with the form with confirm element, I am using a external grammar named AirportName.xml. The browser I am using is Voice genie, and speech works xml format for the grammar. Now the doubts I have are,
when I set the url for the grammar file under voice grammar box in settings, what would be the slotname for the form element?? Do i need one?
I am trying to capture the various aliases for airport names defined in the grammar file, and return the intended value. The confirm would try to play back the return value of the element (hopefully the one intended by the user from his utterance). Is the return value stored under the element data 'value' ? if not, how do i play back the return value when confirming, using say smart.
I included the grammar file AirportNames.xml as an attachment.
I know you dealt with this topic with Srini a couple of times, but I figured , it might be different in my case due to the difference in browser and audium version.
thank you
venk.
Subject: RE: Grammar problems
Replied by: null on 03-10-2003 03:49:02 PM
Hi Venk,
For your AirportName.xml grammar to work with the Audium Form element on SpeechGenie, and return the intended interpretation for each utterance, you would need to do two things:
1) Have your grammar return a tag/slot (say under the name 'result') in the root rule, which should inherit the return value from the child rule tag (named 'value' in your grammar), in a format like the following:
[code:1:aa5cb3a63e]<rule id = "ROOT" scope = "public">
<one-of>
<item>
<ruleref tag="result=Airports.value;" uri="#Airports"/>
</item>
</one-of>
</rule>[/code:1:aa5cb3a63e]
This is because the SpeechWorks OSR engine only returns the slot/value pairs associated with the root rule. So you should assign properties of the child object to the parent objects all the way to the root, in order to access the slot/value pairs from the root rule. Note that your current grammar returns only the actual utterance recognized by the speech engine, not the intended interpretation.
2) Name the tag in your root rule however you want, and configure the Form Slot Name setting in the builder to match your tag name accordingly (in the above case, set it to result). Please refer to the Element Specification for more details on how Slot Name should be set.
Once both 1) and 2) are updated, you should be able to access the return values intended by your grammar, using the 'value' element data played back with SayItSmart in the string format.
Regards,
rachel