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

RE: Variable name type change in VoiceXML 2.1 CR

From: Pandey, Arvind (Arvind)** CTR ** <pandeya@lucent.com>
Date: Thu, 9 Feb 2006 12:30:20 +0530
Message-ID: <3BE48DD0EC7D3948BC183931D9150C210404441B@ii0015exch001u.iprc.lucent.com>
To: "'David Scarratt'" <dscarratt@holly.com.au>, www-voice@w3.org

Hi all,

I am working on VXML interpreter. I have 2 vxml files a.vxml and b.vxml 
b.vxml is application root file and mentioned in the a.vxml as application
I am assigning 2 root variables c and d from leaf (a.vxml) and values are
assigned but if I try to transit from a.vxml to b.vxml and play a prompt in
B.vxml then c and d are undefined. I want to know ur opinion regarding this.
Bcoz if we are using goto then apllication context should not be
re-initialised. But I guess its taking b.vxml as a new application and
getting re-initialized.

Can any one exactly what the problem might be.

Lucent Technologies
Bell Labs Innovation

-----Original Message-----
From: www-voice-request@w3.org [mailto:www-voice-request@w3.org]On
Behalf Of David Scarratt
Sent: Friday, January 20, 2006 1:49 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 Thursday, 9 February 2006 20:59:53 UTC

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