RE: VoiceXML 2.1: Error handling requirements

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-3':

The language in C.3 of VoiceXML 2.1 will be modified to clarify that the undefined behavior is specific to how a conforming VoiceXML 2.1 processor handles a document that specifies a version attribute with a value other than 2.0 or 2.1. The statement was meant to clarify issue 88 [3] from the comments on the Last Call Working Draft of VoiceXML 2.1.

Please indicate before 14 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
[3] http://www.w3.org/TR/voicexml21/voicexml21-disp.html#R88-1

-----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:16 PM
To: www-voice@w3.org
Subject: VoiceXML 2.1: Error handling requirements


Dear Voice Browser Working Group,

  http://www.w3.org/TR/2005/CR-voicexml21-20050613/ appendix C.3 states "When a Conforming VoiceXML 2.1 Processor encounters a non-Conforming VoiceXML 2.0 or 2.1 document, its behavior is undefined." This seems to contradict other sections, e.g. section 5 states for the <data> element 

  Exactly one of "src" or "srcexpr" must be specified;
  otherwise, an error.badfetch event is thrown.

Assuming that a document that violates this requirement is not con- forming, the document does define error processing. Please remove this contradiction.

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 Tuesday, 8 November 2005 05:07:21 UTC