W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2006

RE: Variable name type change in VoiceXML 2.1 CR

From: Matt Oshry <matto@tellme.com>
Date: Fri, 20 Jan 2006 00:29:29 -0800
Message-ID: <B8E24C3AF01492459438BFA2D6ECBF7305999AE0@EXCH.sea.tellme.com>
To: "David Scarratt" <dscarratt@holly.com.au>
Cc: <www-voice@w3.org>


Thanks for your observation. The Voice Browser Working Group agrees that the revised schema is too restrictive, and it will be fixed in a forthcoming update to the VoiceXML 2.1 specification.


Matt Oshry

-----Original Message-----
From: www-voice-request@w3.org [mailto:www-voice-request@w3.org] On Behalf Of David Scarratt
Sent: Tuesday, January 17, 2006 9:15 PM
To: www-voice@w3.org
Subject: Variable name type change in VoiceXML 2.1 CR

The type 'RestrictedVariableName.datatype' in vxml-datatypes.xsd changed from being

   <xsd:restriction base="xsd:NMTOKEN">

(the same as for VoiceXML 2.0) in the VoiceXML 2.1 20040728 working draft schema to

  <xsd:restriction base="xsd:token">
   <xsd:pattern value="([a-zA-Z]|[a-zA-Z$][a-zA-Z0-9_$]*[a-zA-Z0-9_])"/>

in the VoiceXML 2.1 candidate recommendation schema, but I can find no comment about the change.  It seems intended to implement some of the additional constraints listed in the accompanying 'xsd:documentation' 
section; but since the VoiceXML 2.0 specification indicates that "the variable naming convention is as in ECMAScript", which allows Unicode letters in names, while the new pattern apparently restricts variable names to a subset of ASCII, it breaks backwards compatibility.

For example, the following document is a conforming VoiceXML 2.0 document, but the same document with "version='2.1'" (and correct schema
location) would not be a conforming VoiceXML 2.1 document:

   <?xml version="1.0" encoding="iso8859-1"?>
   <vxml version="2.0" xmlns="http://www.w3.org/2001/vxml"

     <var name="café"/>


Could someone clarify this for me?

David Scarratt
Senior Engineer, Holly Connects
Received on Friday, 20 January 2006 08:29:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:38 UTC