29822 2016-09-14 09:42:48 +0000 [SER31] Adaptive output method, xs:anyURI 2016-09-23 09:33:46 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Serialization 3.1 Candidate Recommendation PC Windows NT RESOLVED FIXED https://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/html/Overview.html#adaptive-output P2 normal --- 1 tim cmsmcq andrew_coleman public-qt-comments oldest_to_newest 127386 0 tim 2016-09-14 09:42:48 +0000 The specification reads: "An instance of xs:string or xs:untypedAtomic is serialized by enclosing the value in double quotation marks and doubling any quotes within the value; or optionally by enclosing the value in apostrophes and doubling any apostrophes within the value. The resulting value is then serialized using the Text output method described in 8 Text Output Method." ... "An atomic value of any other type is serialized using the syntax of a constructor function: xs:TYPE("VAL") where TYPE is the name of the primitive type, and VAL is the result of applying the fn:string() function. For example, xs:date("2015-07-17"). The resulting string is then serialized using the Text output method described in 8 Text Output Method." xs:anyURI isn't an xs:string, so it is handled by the final rule. This means xs:anyURI('"') will be output as xs:anyURI(""") Personally, I'd like to see xs:anyURI be treated just like xs:string and xs:untypedAtomic. 127443 1 cmsmcq 2016-09-20 15:34:56 +0000 If the text says "enclosing the value in double quotation marks and doubling any quotes within the value", surely a URI consisting of a single double-quotation mark would be serialized as xs:anyURI("""") not as xs:anyURI(""") or am I missing something? 127444 2 cmsmcq 2016-09-20 15:36:24 +0000 Ah. Sorry for the confusion in comment 1. I now see what you're saying. 127514 3 andrew_coleman 2016-09-23 09:33:46 +0000 At the meeting on 2016-09-20, the WG agreed to handle xs:anyURI the same as xs:string. This change has been applied to the spec.