W3C home > Mailing lists > Public > www-voice@w3.org > July to September 2002

RE: More VXML comments and clarification suggestions

From: Scott McGlashan <scott.mcglashan@pipebeach.com>
Date: Mon, 5 Aug 2002 16:47:22 +0200
Message-ID: <2764A29BE430E64A92EB56561587D2E7107E8B@se01ms02.i.pipebeach.com>
To: "Guillaume Berche" <guillaume.berche@eloquant.com>, <www-voice@w3.org>

Hi Guillaume,

thank you for your comments. 

The deadline for comments on VoiceXML 2.0 Last Call Working Draft was
the 24th May 2002. 

While the Voice Browser Working Group may address your comments, I
cannot guarantee that due to your comments being submitted after the
deadline. I will let you know if we do address your comments.

thanks again,

Scott
[leader, VBWG Dialog Team]

-----Original Message-----
From: Guillaume Berche [mailto:guillaume.berche@eloquant.com]
Sent: Thursday, August 01, 2002 18:02
To: www-voice@w3.org
Subject: More VXML comments and clarification suggestions



Hello,

Following are additional suggestions for clarifications of the VXML 2.0
W3C
Working Draft from 24 April 2002.

1 - Precise the behavior if Reprompt is executed outside of a catch
element

Suggested text addition to section "5.3.6 REPROMPT":
"If a Reprompt is executed outside of a catch element (such as in a
block or
filled elements) then an "error.semantic" event is thrown.


2 - Precise which event should be thrown for malformed ECMAScript
expressions in Var, Assign, Script, and ECMAScript expression evaluation
(such as the "cond" attribute, and expr attribute variants).

Suggested text addition to Appendix C, FIA:
"During the execution of the FIA, various ECMAScript expressions are
evaluated such as the "cond" attribute of input or prompt items and the
different variants of "expr" attribute. If the evaluation of such an
ECMAScript expression defined in the document results in an error then
an
"error.semantic" event is thrown. These events are handled in the same
way
than events thrown during execution as documented in the beginning of
this
section."


3 - Precise that the Block's prompt queuing occurs during prior to
execute
the Block.
In the example below, it seems unclear from the specifications whether
the
second prompt would be heard because prompts are executable content and
the
definition of "execute" states that as soon as a "<goto> is executed,
the
transfer takes place immediately, and the remaining executable content
is
not executed." However, the collect phase states that appropriate
prompts
elements should be selected for the input item (including blocks).
<block>
	This is my first prompt text
	<goto next="#another_dialog"/>
	This is my second prompt text
</block>

Suggested modifications to the appendix C:
"   else if ( a <block> was chosen )
   {
       Set the block's form item variable to a defined value.

       Execute the block's executable context (except for prompts which
were
previously queued in the select phase).
   }"



I hope this can help. Any comment on this is welcomed.

Best regards,

------------------------------------------
Guillaume Berche
Eloquant, ZA Le malvaisin
38240 Le Versoud, France
guillaume.berche@eloquant.com
+33 04 76 77 46 92
------------------------------------------
Received on Monday, 5 August 2002 10:38:59 GMT

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