111-15: VoiceXML 2.1: encoding of external scripts

Bjoern,

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

The VBWG has decided to defer formal specification of the expected behavior to a future version of the specification. The purpose of VoiceXML 2.1 is to formally define a small set of features commonly used throughout the industry while maintaining complete backwards compatibility with VoiceXML 2.0. Clarification of 111-15 does not meet those criteria.

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:15 PM
To: www-voice@w3.org
Subject: VoiceXML 2.1: encoding of external scripts


Dear Voice Browser Working Group,

  http://www.w3.org/TR/2005/CR-voicexml21-20050613/ inherits the <script> element defined in VoiceXML 2.0. The definition of that element includes a "charset" attribute which is defined as

  The character encoding of the script designated by src. UTF-8 and
  UTF-16 encodings of ISO/IEC 10646 must be supported (as in [XML])
  and other encodings, as defined in the [IANA], may be supported.
  The default value is UTF-8.

It's unclear when implementations would use the value of the attribute to decode external scripts. For example, it seems that implementations must ignore the attribute when the script is transported via a MIME- like mechanism like HTTP and the encoding is specified in the charset parameter in the Content-Type field. Please change VoiceXML such that VoiceXML 2.1 implementations process script content in a manner con- sistent with

  http://www.ietf.org/internet-drafts/draft-hoehrmann-script-types-03.txt

and other applicable specifications.

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