The spec is sloppily worded. It says the value is "a list of namespace
prefixes" and then says it can include "#default"; but "#default"
clearly isn't a namespace prefix, and there is no way it could be
declared, so the error condition saying it must be declared clearly
doesn't apply to this case.
the wording is improved in 2.0:
The value of the attribute is a whitespace-separated list of tokens,
each of which is either a namespace prefix, or #default, or #all. The
namespace bound to each of the prefixes is designated as an excluded
namespace. It is a static error if there is no namespace bound to the
prefix on the element bearing the [xsl:]exclude-result-prefixes
attribute.
Michael Kay
Software AG
home: Michael(_dot_)H(_dot_)Kay(_at_)ntlworld(_dot_)com
work: Michael(_dot_)Kay(_at_)softwareag(_dot_)com
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com] On Behalf Of
Johannes Dobler
Sent: 16 January 2003 16:33
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] exclude-result-prefixes
Is the following stylesheet correct? It designates the
default namespace as
excluded without a declaration of the default namespace:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
version="1.0"
exclude-result-prefixes="#default">
...
</xsl:stylesheet>
The xslt rec says: "It is an error if there is no namespace
bound to the
prefix on the element bearing the exclude-result-prefixes or
xsl:exclude-result-prefixes attribute.", so I would expect
its not correct.
I'm asking because Xalan and Saxon accept such a stylesheet.
regards,
Johannes
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list