W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2008

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

From: <bugzilla@wiggum.w3.org>
Date: Tue, 12 Feb 2008 19:38:13 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1JP0xJ-0004aq-B6@wiggum.w3.org>

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





------- Comment #7 from mike@saxonica.com  2008-02-12 19:38 -------
Anders has stated that he believes no change is needed to the XDM
specification. 

I'm not comfortable with this.

In 6.1.1 and 6.2.1 we say "base URI, possibly empty" which is fine.

But in 6.1.3 (construction from an Infoset) we say:

The following infoset properties are required: [children] and [base URI].
The following infoset properties are optional: [unparsed entities].

with similar text in 6.2.3 and 6.5.3

This gives the strong impression that when creating an XDM document from an
InfoSet, there must be a base URI, and I don't think this is the case. I don't
think it's good enough to argue that "required" leaves open the possibility of
the value existing but being empty; if we want to make that kind of subtle
distinction then we need to be a lot more formal.

The Infoset spec does not explicitly discuss that the [Base URI] property can
be absent or unknown, but it is clearly something that can happen in practice.
I think XDM should make it clear, in discussing construction from an Infoset in
the sections cited, that if the infoset [Base URI] property value is absent or
unknown (these are the terms Infoset uses) then the XDM property will be empty.
Received on Tuesday, 12 February 2008 19:38:33 GMT

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