RE: VoiceXML 2.1: mixing 2.0 and 2.1 functionality

Bjoern,

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.1 [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 issue you raised, identified as '111-11':

The Working Group considered a number of scenarios in which VoiceXML 2.0 and VoiceXML 2.1 functionality might be mixed and produce undesirable results. One such scenario involves an application root document with its version set to '2.1' and a leaf document with its version set to '2.0'. The application root document contains an event handler that contains a tag specific to VoiceXML 2.1 (e.g. <foreach>). Since event handlers are executed as-if-by-copy, the interpreter must decide how to handle the <foreach> tag should the event get thrown while executing the 2.0 document. One interpreter might choose to throw 'error.unsupported.element.foreach'; another might choose to execute the <foreach>; yet another might choose to throw 'error.badfetch' when resolving the 2.1 application root associated with the 2.0 leaf.

To reach consensus, the group concluded that this decision should be driven by the compatibility requirements of the platform vendor and should not be mandated by the specification. In general, the group wishes to discourage the mixing of document versions within an application; hence, the statement "a VoiceXML application should not mix documents of both types."

Please indicate before 17 November 2005 whether you are satisfied with the VBWG's resolution, 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 14 November, please let me know. The Director will appreciate a response as to whether or not you agree with the resolution. However, if we do not hear from you at all by 14 November 2005, we will assume that you accept our resolutions.

Thank you,

Matt Oshry
Chief Editor, VoiceXML 2.1

[1] http://www.w3.org/TR/2005/CR-voicexml21-20050613/
[2] http://www.w3.org/2004/02/Process-20040205/tr.html#cfi

-----Original Message-----
From: www-voice-request@w3.org [mailto:www-voice-request@w3.org] On Behalf Of Bjoern Hoehrmann
Sent: Sunday, June 26, 2005 2:15 PM
To: www-voice@w3.org
Subject: VoiceXML 2.1: mixing 2.0 and 2.1 functionality


Dear Voice Browser Working Group,

  http://www.w3.org/TR/2005/CR-voicexml21-20050613/ notes that "The handling of a single application that mixes VoiceXML 2.0 and VoiceXML
2.1 functionality is platform-specific." So far it seems that VoiceXML
2.1 is a superset of VoiceXML 2.0, so it's not really clear how one could mix functionality. Please either remove this note or change the document such that it is clear what kind if functionality mix should be avoided by authors so they can avoid implementation-defined behavior.

regards,
--
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

Received on Thursday, 10 November 2005 23:05:31 UTC