3303 2006-05-29 15:13:25 +0000 fn-base-uri-23 expects the uri to be escaped? 2006-09-08 13:21:05 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite 0.9.0 PC Windows XP RESOLVED FIXED P2 normal --- 1 marc.van.cappellen carmelo oldest_to_newest 9902 0 marc.van.cappellen 2006-05-29 15:13:25 +0000 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 9921 1 carmelo 2006-06-01 20:40:28 +0000 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 10083 2 marc.van.cappellen 2006-06-17 20:32:10 +0000 I confirm this is resolved in XQTS 0.9.4 10117 3 mike 2006-06-19 15:33:54 +0000 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" 10138 4 carmelo 2006-06-19 21:35:44 +0000 Michael: I will bring this to the Task force once more. perhaps the WG have an opinion? Carmelo 10425 5 carmelo 2006-07-07 13:26:12 +0000 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 11514 6 carmelo 2006-09-08 13:21:05 +0000 Given the resoultion of bug 3415 not allowing escaping of special characters, I removed the alternate expected results. Thanks, Carmelo