W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > September 2005

FW: XSLT and XML 1.1

From: Grosso, Paul <pgrosso@ptc.com>
Date: Fri, 30 Sep 2005 15:09:12 -0400
Message-ID: <CF83BAA719FD2C439D25CBB1C9D1D302DB97D5@HQ-MAIL4.ptcnet.ptc.com>
To: <public-xml-core-wg@w3.org>


Feel free to reply directly to the XSL WG if you
have something timely to say.


-----Original Message-----
From: w3c-xsl-wg-request@w3.org [mailto:w3c-xsl-wg-request@w3.org] On
Behalf Of Michael Kay
Sent: Friday, 2005 September 30 13:27
To: w3c-xsl-wg@w3.org
Cc: w3c-query-editors@w3.org
Subject: XSLT and XML 1.1

There were a couple of issues (2278, 2276) leading to actions to modify
text describing support for XML 1.1. Here's the revised XSLT section
4.1, so
that anyone can scream if I've got it wrong:

<div2 id="xml-versions">
<head>XML Versions</head>

<p>The data model defined in [XDM] is capable of representing either an
1.0 document (conforming to [XML 1.0] and [XML Namespaces]) or an XML
document (conforming to [XML 1.1] and [XML Namespaces 1.1]), and
it makes no distinction between the two. In principle, therefore, XSLT
can be used with either of these XML versions.</p>

<p>Construction of the data model is outside the scope of this
specification, so XSLT 2.0 places no
formal requirements on an XSLT processor to accept input from either XML
documents or XML 1.1 documents
or both. This specification does define a serialization capability (see
<specref ref="serialization"/>),
though from a conformance point of view it is an optional feature.
facilities are described for
serializing the data model as either XML 1.0 or XML 1.1 (and controlling
choice), there is again no
formal requirement on an XSLT processor to support either or both of
XML versions as serialization

<p>Because the data model is the same whether the original document was
1.0 or XML 1.1, the semantics
of XSLT processing do not depend on the version of XML used by the
document. There is no reason in principle why all the input and output
documents used in a single transformation must conform to the same
of XML.</p>

<p>Some of the syntactic constructs in XSLT 2.0 and XPath 2.0, for
the productions Char and NCName, are defined by reference to the XML and
Namespaces specifications. There are slight variations between the XML
and XML 1.1 versions of these productions. Implementations
<rfc2119>may</rfc2119> support either version; for interoperability it
<rfc2119>recommended</rfc2119> that an XSLT 2.0 processor that
the 1.1 versions <rfc2119>should</rfc2119> also provide a mode that
the 1.0 versions. It is thus implementation-defined whether the XSLT
processor supports XML 1.0 with XML Namespaces 1.0, or XML 1.1 with XML
Namespaces 1.1, or supports both versions at user option.</phrase></p>

<note><p>The term <emph>XML Namespaces 1.0</emph> is used here to refer
<bibref ref="NAMES"/>, which was actually published without a version

<p>At the time of writing there is no published version of <bibref
ref="XMLSCHEMA"/> that references the
XML 1.1 specifications. This means that data types such as
<code>xs:NCName</code> and <code>xs:ID</code> are
constrained by the XML 1.0 rules, and do not allow the full range of
permitted by XML 1.1. 
This situation will not be resolved until a new version of <bibref
ref="XMLSCHEMA"/> becomes available; in the meantime, it is
<rfc2119>recommended</rfc2119> that implementers wishing to support XML
should consult <bibref ref="SCHEMA-AND-XML-1.1"/> for guidance. An XSLT
processor that supports XML 1.1 <rfc2119>should</rfc2119> implement the
rules in later versions of <bibref ref="XMLSCHEMA"/> as they become


An observation about this: XQuery seems to be emphasizing that if you do
anything the 1.1 way, you must do everything the 1.1 way. The XSLT text
seems rather to be emphasizing the ability to mix and match, perhaps
reflecting the fact that we see the language being used to convert
1.0 and 1.1 and vice versa.

Michael Kay
Received on Friday, 30 September 2005 19:07:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:35 UTC