VoiceXML 2.0: Official Response #12 to Candidate Recommendation Issues

The Voice Browser Working Group (VBWG) is now completing its resolution
of 
issues raised during the review of the Candidate Recommendation version
of
VoiceXML 2.0 [1]. Our apologies that it has taken so long to respond.

Following the process described in [2] for advancement to Proposed
Recommendation, this is the VBWG's formal response to the issues you
raised.

Please indicate before 26 November 2003 whether you are satisfied with
the
VBWG's resolutions, whether you think there has been a misunderstanding,
or
whether you wish to register an objection.

If you do not think you can respond before 26 November, please let me
know.
The Director will appreciate a response whether you agree with the
resolutions
or not. However, if we do not hear from you at all by 26 November 2003,
we
will assume that you accept our resolutions.

Below you will find a summary of the VBWG's responses to each of your
issues. Please use the issue identifiers when responding.

Thank you,

Scott McGlashan
Co-chair, Voice Browser Working Group

[1] http://www.w3.org/TR/2003/CR-voicexml20-20030220/ 
[2] http://www.w3.org/2003/06/Process-20030618/ 


-----------------------------------------------
Issues you raised and VBWG responses
-----------------------------------------------

Issues: CR19-1, CR19-2
http://lists.w3.org/Archives/Public/www-voice/2003AprJun/0016.html

Issue CR19-1
1. What did you say?
--------------------
In a real dialog in a noisy environment or when a user is not
concentrated, it can happen that a user does not understand properly a
system prompt and wants the system to repeat it. The last prompt should
be
repeated without increasing the prompt counter in order to repeat really
the same prompt. It is not possible to do it in the current version of
VoiceXML.

I suggest the following solution: Add an atribute to the <reprompt> tag,
which allows to repeat prompts without increasing the prompt counter.

CR19-1 Resolution: rejected 

This will be considered for a future version of the language. 


                   ------------------------------------------------

Issue CR19-2
2. detection and handling of multiple fills of one slot
-------------------------------------------------------
VoiceXML provides no means for detection and handling the situation when
a
slot value is re-specified.

In real conversation it can happen that a participant specifies a piece
of
information twice with different value. The normal reaction is that the
other participant detects this situation and asks the first one for a
clarification. VoiceXML has no means for doing this.

I suggest the following solution: Define a standard event, e.g.
slotredefinition.slotname that would be thrown in such a case and the
old
value would be contained in the _message variable in the <catch> tag's
anonymous scope.

CR19-2 Resolution: rejected 

This can be done within current specification by storing the values and
when new input is received, comparing the stored values with the latest
values. A future version of the language may provide a more flexible
approach along the lines you suggest.

Received on Wednesday, 19 November 2003 14:33:38 UTC