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 7029 - [FO] resolve-uri(): missing "or" in erratum FO.E1
Summary: [FO] resolve-uri(): missing "or" in erratum FO.E1
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 1.0 (show other bugs)
Version: 2nd Edition Recommendation
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2009-06-16 17:52 UTC by Michael Kay
Modified: 2012-03-29 08:05 UTC (History)
1 user (show)

See Also:


Description Michael Kay 2009-06-16 17:52:53 UTC
Erratum FO.E1 introduces the text:

If $base is not a valid URI according to the rules of the xs:anyURI data type, if it is not a suitable URI to use as input to the chosen resolution algorithm (for example, if it is a relative URI reference, if it is a non-hierarchic URI, or if it contains a fragment identifier), then an error is raised [err:FORG0002].

There should be an "or" after the first comma. Without it, the sentence can be read as requiring both the "if" conditions outside the parentheses to be true, rather than either one of them.

I would also suggest adding another example within the parentheses: "if it contains a space". A wannabe-URI - that is, a string that becomes a valid URI after escaping, for example "file:///c:/test dir/" - is not a suitable URI to use as input to the resolution algorithms described in the RFCs, so the error should be raised.

It would also be useful to cover this in test cases.
Comment 1 Michael Kay 2009-06-30 09:24:15 UTC
Reclassified as editorial.
Comment 2 Michael Kay 2012-03-29 08:05:24 UTC
This is fixed in the current 3.0 draft, and it is on the list of candidate errata for the 1.0/2.0 draft, so I am marking it as resolved/closed.