W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2003

Comments on VXML Candidate Recommendation 20 February 2003 (part 2)

From: Guillaume Berche <guillaume.berche@eloquant.com>
Date: Wed, 26 Mar 2003 16:49:40 +0100
To: <www-voice@w3.org>
Message-ID: <ELEGLIHGLLIBFPCIGAKGEEDADEAA.guillaume.berche@eloquant.com>

Hello,

Following are additional suggestions for clarifications on the VXML
Candidate Recommendation  20 February 2003. Let me know if more detail would
be useful, or please point me to the appropriate specifications section if I
missed it. I hope these comments can help.

Thanks and best regards,

Guillaume.

------------------------------------------
Guillaume Berche
Eloquant, ZA Le malvaisin
38240 Le Versoud, France
guillaume.berche@eloquant.com
-----------------------------------------


1- Precise that timeout attribute of the <prompt/> element only applies if
the prompt element is not empty

The <prompt> element is designed to queue prompt element for play. As a side
effect it also set the timeout for the next input collection. However, the
specifications do not describe the expected behavior if the prompt element
is empty: should tghe side-effect still apply? This would make little sense:
this would be a synonym for a "set next timeout" command without queueing
any prompt.

Suggested addition to section "4.1 Prompts":

"Note that an empty prompt such as "<prompt [...]/>" will be silently
ignored and in particular would not set the timeout of the next input
collection phase"


Dependency: IR testsuite case #539 (389/389.vxml)



2- Precise behavior if "cond" attribute of form item does not resolve into
an EcmaScript boolean value

The VXML specification state the following in section "2.1.3 Form Item
Variables and Conditions":

"cond 	An expression to evaluate in conjunction with the test of the form
item variable. If absent, this defaults to true, or in the case of
<initial>, a test to see if any input item variable has been filled in."

However, the specifications do not detail the expected behavior if the
expression does not resolve to a boolean.

Suggested modification to "2.1.3 Form Item Variables and Conditions"
"cond 	An expression to evaluate in conjunction with the test of the form
item variable. If absent, this defaults to true, or in the case of
<initial>, a test to see if any input item variable has been filled in. If
the evaluation of the expression results into an error or does not resolve
into an ECMAScript boolean value, then an error.semantic event is thrown."
Received on Wednesday, 26 March 2003 10:44:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 October 2006 12:48:56 GMT