W3C home > Mailing lists > Public > www-voice@w3.org > April to June 2003

RE: VoiceXML feature request

From: Scott McGlashan <scott.mcglashan@pipebeach.com>
Date: Thu, 24 Apr 2003 14:04:35 +0200
Message-ID: <2764A29BE430E64A92EB56561587D2E7108374@se01ms02.i.pipebeach.com>
To: "Pavel Cenek" <pavel.cenek@itek.norut.no>, <www-voice@w3.org>

Dear Pavel,

Thank you for your input on the next version of the W3C VBWG dialog
language. We will take them into consideration as we start to work on
the requirements over the next few months. 

Thanks

Scott
Co-Chair, W3C VBWG


-----Original Message-----
From: Pavel Cenek [mailto:pavel.cenek@itek.norut.no] 
Sent: Friday, April 11, 2003 09:51
To: www-voice@w3.org
Subject: VoiceXML feature request



    Dear VBWG,

I am sending you some suggestions of new features for a next version of
VoiceXML. I believe that they would be helpful for dialog designers and
that the suggested features are a logical extension of current VoiceXML.

Any comments are welcome.


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.

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.


    Best regards

       Pavel Cenek


-- 

========================================================================
  Pavel Cenek   Ph.D. student         email: xcenek@fi.muni.cz
  Laboratory of Speech and Dialogue   www: http://www.fi.muni.cz/~xcenek
  Faculty of Informatics, MU Brno     lab page:
http://www.fi.muni.cz/lsd

  Currently affiliated with Norut IT  http://www.itek.norut.no/itek/
  Tromsoe, Norway as guest researcher
========================================================================
  Elvira - VoiceXML platform          http://gin2.itek.norut.no/elvira/
  Core technology for building dialogue applications and voice browsers
========================================================================
Received on Thursday, 24 April 2003 08:04:41 GMT

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