- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 25 Sep 2006 16:20:24 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3486 frans.englich@telia.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|XQuery |XPath Resolution|FIXED | ------- Comment #14 from frans.englich@telia.com 2006-09-25 16:20 ------- Yes, David and I seem to be in agreement on the current state(comments #12 and #13). Summarized: It is currently possible to make the static base URI relative by setting it as so from the external environment. This makes all assumptions(references in #0) on that the base URI is absolute not hold. Therefore, there are two possible approaches for this: 1) Either re-write all relevant sections to not assume the base URI is absolute; or 2) Make it an error if the base URI is not absolute. I think the latter is the correct solution. Proposed fix: In 2.1.1 Static Context(XPath20/XQuery10) change: "[Definition: Base URI. This is an absolute URI, used when necessary in the resolution of relative URIs (for example, by the fn:resolve-uri function.)] The URI value is whitespace normalized according to the rules for the xs:anyURI type in [XML Schema]." by appending a sentence, such that it becomes: "[Definition: Base URI. This is an absolute URI, used when necessary in the resolution of relative URIs (for example, by the fn:resolve-uri function.)] The URI value is whitespace normalized according to the rules for the xs:anyURI type in [XML Schema]. It is a static error if the URI is not absolute[new XPST* error code]." This can affect XSL-T, I'm not the one to tell.
Received on Monday, 25 September 2006 16:20:27 UTC