W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2007

[Bug 5207] [XQ] Accessing undefined static context base URI and XPST0001

From: <bugzilla@wiggum.w3.org>
Date: Thu, 18 Oct 2007 11:20:07 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1IiTQ7-00048Y-3l@wiggum.w3.org>

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





------- Comment #4 from mike@saxonica.com  2007-10-18 11:20 -------
I can't be certain, but I suspect the intended meaning for element constructors
was the same as for document constructors: the base URI of the element is the
same as the base URI in the static context, which means it's
null/absent/empty/undefined/none if the value in the context is
null/absent/empty/undefined/none. (I wish I understood which of these terms we
should use...)

One could argue that this code isn't "using" the value of the static base URI,
it's only copying it...

It could probably be clarified, except that when you go near base URI,
something always breaks.
Received on Thursday, 18 October 2007 11:20:14 UTC

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