W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2005

[Bug 1235] [XSLT] Namespace fixup for QName-valued content is unduly onerous

From: <bugzilla@wiggum.w3.org>
Date: Tue, 14 Jun 2005 13:19:28 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DiBKC-0005gy-0a@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1235





------- Additional Comments From mike@saxonica.com  2005-06-14 13:19 -------
At the XSL WG telcon on 9 Jun 2005, the WG decided that we didn't want to
perform namespace fixup for this case: but rather than making an outright ban on
the combination of validation=preserve with copy-namespaces=no, we would raise a
dynamic error if this leads to the data becoming invalid - that is, if it causes
typed QName values to be copied without their namespaces being copied.

The specific change is to replace the text of the new error 0950:

<old>
It is a static error if the copy-namespaces attribute of hte xsl:copy or
xsl:copy-of instruction has the value no when its explicit or implicit
validation property has the value preserve. This is because the validity of the
content may depend on the namespace context.
</old>

<old>
It is a type error if the copy-namespaces attribute of the xsl:copy-of
instruction has the value no, and its explicit or implicit validation property
has the value preserve, and the content of a node being copied includes
namespace-sensitive content, that is the typed value of the node contains an
value of type xs:QName or xs:NOTATION or a type derived or constructed
therefrom. This is because the validity of the content may depend on the
namespace context.
</old>

I propose also to merge this with error 0955, which describes a very similar
error condition for attribute nodes.

Michael Kay
Received on Tuesday, 14 June 2005 13:19:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:38 GMT