This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
fn-base-uri-23 expects the URI to be escaped: http:%5C%5Cexample.com%5C%5Cexamples Should that really be escaped? The query is as follows: fn:string(fn:base-uri(<anElement xml:base="http:\\example.com\\examples">Element content</anElement>)) In http://www.w3.org/TR/xquery-operators/#func-string we read: If $arg is an atomic value, then the function returns the same string as is returned by the expression " $arg cast as xs:string " (see 17 Casting). And in http://www.w3.org/TR/xquery-operators/#casting-to-string: If ST is xs:anyURI, the type conversion is performed without escaping any characters. Thanks, Marc
Marc: Thanks for raising this issue. After the Testing Task Force disccussed this issue, we decided that there are no statements in the specs to justify escaping, and thus changed the expected results to "http:\\example.com\\examples" as you suggested. Please close this bug if you agree. Thanks, Carmelo
I confirm this is resolved in XQTS 0.9.4
I believe this resolution is incorrect, and the URI should be escaped. The XDM specification says in 5.2 "The dm:base-uri accessor returns the base URI of a node as a sequence containing zero or one URI reference", and refers to [XML Base] for further information. The Base URI specification says in 3.1 "processors must encode and escape [special] characters to obtain a valid URI reference from the attribute value"
Michael: I will bring this to the Task force once more. perhaps the WG have an opinion? Carmelo
Marc/Michael: Given that the Working group will be deciding on this in the near future, we (task force) decided to allow both expected outcomes for the time being. I will leave the bug open for now. Thanks, Carmelo
Given the resoultion of bug 3415 not allowing escaping of special characters, I removed the alternate expected results. Thanks, Carmelo