W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2005

Re: VBWG official response to last call issue

From: Max Froumentin <mf@w3.org>
Date: Fri, 25 Mar 2005 11:35:51 +0000
To: Martin Duerst <duerst@w3.org>
Cc: "MattO" <matto@tellme.com>, <www-voice@w3.org>, <w3c-i18n-ig@w3.org>, public-i18n-core@w3.org
Message-ID: <87y8ccklew.fsf@w3.org>

Martin, all,

Please find below the VBWG's responses to your last call comment on
URIs/IRIs in VoiceXML2.1 

>>VBWG Response: Deferred
>>VoiceXML 2.1 (VXML21) is designed to be completely backwards compatible with
>>VoiceXML 2.0 (VXML2). The VXML21 schema is derived directly from the VXML2
>>schema, and the definition of "URI.datatype" is identical. The VBWG suggests
>>that it would be more appropriate to submit this particular CR to the VBWG
>>as a proposed errata for VXML2. If the CR were adopted for VXML2, the change
>>would be picked up by VXML21 to maintain compatibility.
> So we herewith request the following changes to VXML2, which we understand
> will be carried over to VXML21:
> - Change the XML Schema definition of URI.datatype from:
>   <xsd:simpleType name='URI.datatype'>
>        <xsd:annotation>
>            <xsd:documentation>URI (RFC2396)</xsd:documentation>
>        </xsd:annotation>
>        <xsd:restriction base='xsd:anyURI'/>
>   </xsd:simpleType>
>   to:
>   <xsd:simpleType name='URI.datatype'>
>        <xsd:annotation>
>            <xsd:documentation>IRI (RFC3987)</xsd:documentation>
>        </xsd:annotation>
>        <xsd:restriction base='xsd:anyURI'/>
>   </xsd:simpleType>
> - Add a reference to RFC 3987
> - Update the reference to RFC 2396 to RFC 3986
> - Say clearly in the spec that wherever the term URI is used,
>   this isn't restricted to ASCII only, actually allows IRIs.
> We very much hope that this can be done in time for the next
> publication of VXML21.

After further discussions, the working group proposes:

- not to add an erratum to VoiceXML2.0: RFC3986 was published after
  VoiceXML2.0. And even though 3986 supercedes 2396, referencing
  RFC2396 was not an error and so shouldn't be corrected in an erratum.
  Similarly for RFC3987.

- to change the VoiceXML2.1 schema to reference RFC3986 instead of the
  now obsolete RFC2396.

- not to add a reference to RFC 3987 to VoiceXML2.1. As explained in
  the specification, "VoiceXML 2.1 specifies a set of features
  commonly implemented by Voice Extensible Markup Language platforms."
  Adding IRIs is a new feature, not currently implemented by VoiceXML
  implementations.  Moreover, RFC3987 was finalised too recently in
  the development of VoiceXML2.1: January 2005, 6 months after the
  publication of this Last Call.

- to consider support for RFC2397 in future versions of VoiceXML. 

We hope you are satisfied with these proposals and their rationales.
Please let us know.

Received on Friday, 25 March 2005 11:33:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:01:07 UTC