W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2006

[Bug 3081] Editorial suggestion for xpath-default-namespace

From: <bugzilla@wiggum.w3.org>
Date: Wed, 05 Apr 2006 20:41:44 +0000
To: public-qt-comments@w3.org
Message-Id: <E1FREoy-0008U2-EA@wiggum.w3.org>


------- Comment #3 from mike@saxonica.com  2006-04-05 20:41 -------
x-d-n only affects the interpretation of unprefixed QNames that appear
statically somewhere in the stylesheet. It has no effect at run-time, and it
has no effect on names written in the form of string literals. Perhaps that's
the distinction you are grappling with.

It's also true, as you're suggesting, that the list of names it affects are
essentially the names of elements appearing in source documents. For names of
objects in the stylesheet (and for names of attributes anywhere), the rule is
"no prefix means no namespace". For names of constructed elements, the rule is
"no prefix means use the default namespace (xmlns='uri')". Type names were
included, I  think, because of a feeling that types would often be in the same
namespace as the input document and so should be treated consistently.

I'm not sure I understand why you draw out the content of an xsl:key element as
a special case. The content consists of XSLT instructions, and they are
affected by x-d-n in exactly the same way as XSLT instructions anywhere else in
the stylesheet.
Received on Wednesday, 5 April 2006 20:41:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:11 UTC