Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The answers you want are in the <a href="http://www.w3.org/TR/semantic-interpretation/" rel="nofollow noreferrer">SISR</a> specification which provides a mechanism for attaching meaning to input paths. Rewriting your example:</p> <pre><code>&lt;?xml version="1.0"?&gt; &lt;grammar xmlns="http://www.w3.org/2001/06/grammar" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2001/06/grammar http://www.w3.org/TR/speech-grammar/grammar.xsd" xml:lang="en" version="1.0" mode="voice" scope="dialog" tag-format="semantics/1.0-literals"&gt; &lt;rule id="keep"&gt; &lt;one-of&gt; &lt;item&gt; &lt;one-of&gt; &lt;item&gt;exit&lt;/item&gt; &lt;item&gt;exit the system&lt;/item&gt; &lt;/one-of&gt; &lt;tag&gt;exit&lt;/tag&gt; &lt;/item&gt; &lt;item&gt; &lt;one-of&gt; &lt;item&gt;another&lt;/item&gt; &lt;item&gt;another mailbox&lt;/item&gt; &lt;/one-of&gt; &lt;tag&gt;another&lt;/tag&gt; &lt;/item&gt; &lt;item&gt; &lt;one-of&gt; &lt;item&gt;play&lt;/item&gt; &lt;item&gt;play back&lt;/item&gt; &lt;/one-of&gt; &lt;tag&gt;play&lt;/tag&gt; &lt;/item&gt; &lt;/one-of&gt; &lt;/rule&gt; &lt;/grammar&gt; </code></pre> <p>Several things to know:</p> <ul> <li>I chose the literal tag format (notice the tag-format attribute of the grammar element). It could have also been implemented using "semantics/1.0" and the contents of the tag would have looked like: out="exit";</li> <li>TellMe tag-format values may need to be different, but their <a href="http://msdn.microsoft.com/en-us/library/ee800148.aspx" rel="nofollow noreferrer">development guide</a> implies they follow the standards.</li> <li>Once you have it working, don't hesitate to create filler grammars (in SRGS speak, rules). Filler rules would be rules without any SI (no tag elements) and contain common phrases people add to responses. For example, a trailing rule that could be added at the end of your grammar:</li> </ul> <blockquote> <pre><code> &lt;/one-of&gt; &lt;item repeat="0-1"&gt;&lt;ruleref uri="#trailing"/&gt;&lt;/item&gt; &lt;/rule&gt; &lt;rule id="trailing&gt; &lt;one-of&gt; &lt;item&gt;please&lt;/item&gt; &lt;item&gt;thank you&lt;/item&gt; &lt;/one-of&gt; &lt;/rule&gt; &lt;/grammar&gt; </code></pre> </blockquote> <p>This would support more natural types of responses. This may or may not be important depending on your calling base. Filler grammars can be very large, but tend to be highly reusable. You can also add filler at the beginning of input. In rich speech applications, a the most significant gain in the tuning process involves updating the grammar to contain the actual phrases spoken by the caller versus what the developer or VUI designer thought would be spoken.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload