Michael,
From the list of changes :
<quote>
It is now a recoverable error to generate nodes in the result tree
using a namespace name that is not a valid instance of xs:anyURI. XSLT
1.0 explicitly stated that this was not an error; however, the XPath
2.0 data model assumes that the name of a node is a valid xs:QName,
and the namespace part of a valid xs:QName, if present, must be a
valid xs:anyURI. The fact that this error is recoverable, however,
gives implementations freedom to avoid strict validation of namespace
names if they wish to do so.
</quote>
May I ask why this change was made? Not that I'm inconvenienced by
this - it just seems like an odd thing to explicitly change.
Thanks,
Kenneth
On Fri, 11 Feb 2005 19:23:55 -0000, Michael Kay <mike(_at_)saxonica(_dot_)com>
wrote:
There's a new set of XSLT/XPath/XQuery working drafts published today.
Nothing earth-shattering in them: the XSLT and XPath documents both have a
list of changes right at the end.
http://www.w3.org/TR/xslt20/
http://www.w3.org/TR/xpath20/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--