This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2654 - Wrong note for resolve-uri()
Summary: Wrong note for resolve-uri()
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 1.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Ashok Malhotra
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2006-01-05 17:22 UTC by Michael Kay
Modified: 2006-11-16 18:50 UTC (History)
0 users

See Also:


Description Michael Kay 2006-01-05 17:22:21 UTC
The spec of resolve-uri() includes the non-normative note:

If $relative is the zero-length string, returns the value of the base-uri
property from the static context in the first form (if the base-uri property is
not initialized in the static context an error is raised [err:FONS0005]) and
$base in the second form.

I think the last part of this (the second form) is true only if $base is an
absolute URI. We've rather avoided saying what the result of resolving against a
relative URI should be, because the RFCs themselves are not very explicit on the

The author of test fn-resolve-uri-2 has his own theories...

I propose removing the first paragraph of the Note.
Comment 1 Ashok Malhotra 2006-01-18 15:57:46 UTC
On the Jan 17 joint WG telcon, the WGs agreed to make the change suggested by
Michael Kay.