111-21: VoiceXML 2.1: read-only DOM subset


The Voice Browser Working Group (VBWG) is 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-21':

According to 1.2 of DOM Level 2, if an attempt is made to modify an object where modifications are not allowed, the implementation throws a DOMException whose code property is set to NO_MODIFICATION_ALLOWED_ERR. Throwing such an exception is only necessary if the implementation does not allow the object (e.g. Attribute) to be modified. The VBWG has concluded that it is unnecessary to further clarify this in the VoiceXML 2.1 specification.

Please indicate before 17 February 2006 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 17 February, 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 17 February 2006, 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:14 PM
To: www-voice@w3.org
Subject: VoiceXML 2.1: read-only DOM subset

Dear Voice Browser Working Group,

  http://www.w3.org/TR/2005/CR-voicexml21-20050613/ defines a "read- only" subset of DOM Level 2 Core. The subset however is not defined to be read-only, for example, Attr.value is not read-only. Please change the document such that it is clear what implementations must do when setting such properties is attempted.

It seems they would raise a NO_MODIFICATION_ALLOWED_ERR exception, if that's the case it's unclear whether raising the exception is mandatory, even for implementations that support all of DOM Level 2 Core.

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 Monday, 13 February 2006 07:15:12 UTC