7029 2009-06-16 17:52:53 +0000 [FO] resolve-uri(): missing "or" in erratum FO.E1 2012-03-29 08:05:43 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 1.0 2nd Edition Recommendation PC Windows NT CLOSED FIXED P2 minor --- 1 mike mike jim.melton public-qt-comments oldest_to_newest 25591 0 mike 2009-06-16 17:52:53 +0000 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. 25822 1 mike 2009-06-30 09:24:15 +0000 Reclassified as editorial. 66220 2 mike 2012-03-29 08:05:24 +0000 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.