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

Dear Guillaume,

Thank you for your additional comments [2] on VoiceXML 2.0 Candidate
Recommendation [1]. 

We will review your comments in the group and get back to you as soon as
possible with our official response.

Thanks again,

Scott McGlashan
Co-Chair VBWG

[1] VoiceXML 2.0, W3C Candidate Recommendation, 20 February 2003
http://www.w3.org/TR/2003/CR-voicexml20-20030220/

[2] Email from Guillaume Berche to www-voice@w3.org 
http://lists.w3.org/Archives/Public/www-voice/2003JanMar/0099.html

-----Original Message-----
From: Guillaume Berche [mailto:guillaume.berche@eloquant.com] 
Sent: Wednesday, March 26, 2003 16:50
To: www-voice@w3.org
Subject: Comments on VXML Candidate Recommendation 20 February 2003
(part 2)



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 Tuesday, 8 April 2003 06:22:56 UTC