Page 1 of 1

SWI_literal: does it accept properties as per SISR?

Posted: Mon Dec 24, 2007 3:02 pm
by moshe
In grammar fiiles, I'd like to know if the I can use properties attached to SWI_literal.

According to the SISR spec, I can use a construct such as

Code: Select all

<tag>out.foo="bar"</tag>
and in my field element use

Code: Select all

<field name="alpha" slot="foo">
and, on recognition, the field element's alpha will contain "bar."

I'd like to know if:

(a) Whether

Code: Select all

<tag>SWI_literal.foo="bar"</tag>
is supported. My current code isn't working, and if SWI_literal cannot have properties, that'd explain why my code is not working.

(b) If the slot attribute is supported, i.e., if

Code: Select all

<field name="alpha" slot="foo">
is supported.

Clarification of IVR issues

Posted: Thu Dec 27, 2007 2:05 pm
by support
Using the IVR system:

"(a)" is not supported, the SWI_literal cannot have properties.

"(b)" is supported, the slot attribute of the <field> tag is supported.

Posted: Thu Dec 27, 2007 2:49 pm
by moshe
How can I get an interpretation and slot to work if SWI_literal.answer is not supported? Do I use

Code: Select all

<tag>answer="foo"</tag>
and

Code: Select all

slot="answer"
or something else?

IVR code

Posted: Thu Dec 27, 2007 3:07 pm
by support
Yes, using the <tag> that will work. Here is an example IVR code snippet:

<var name="name"/>
...
<tag>
name="Garfield"
</tag>
...
<field name="title" slot="name" />

In this IVR example, the field title gets the string value "Garfield".