29273 2015-11-09 15:49:52 +0000 [SER31] Adaptive Serialization: serialization of strings, result of fn:string 2015-11-18 13:41:44 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Serialization 3.1 Candidate Recommendation PC Windows NT RESOLVED FIXED P2 normal --- 1 christian.gruen cmsmcq abel.braaksma andrew_coleman mike public-qt-comments oldest_to_newest 124135 0 christian.gruen 2015-11-09 15:49:52 +0000 The spec states that, for adaptive serialization, "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." Ampersand characters should probably be represented as "&". The same rule could be applied to value of any other type: Right now, the spec says that "VAL is the result of applying the fn:string() function", but it may not immediately be clear how the result is going to look like if fn:string() yields ampersands or quotes. 124137 1 mike 2015-11-09 16:55:40 +0000 >Ampersand characters should probably be represented as "&". I don't agree. XQuery doesn't require ampersands to be escaped in a string literal, and XPath doesn't even allow it. We shouldn't encourage users to think of using XML escaping outside XML text and attribute nodes. 124138 2 christian.gruen 2015-11-09 17:02:24 +0000 > I don't agree. XQuery doesn't require ampersands to be escaped in a string > literal, and XPath doesn't even allow it. We shouldn't encourage users to > think of using XML escaping outside XML text and attribute nodes. I didn’t reflect about XPath; but the XQuery grammar for string literals is as follows: [222] StringLiteral ::= ('"' (PredefinedEntityRef | CharRef | EscapeQuot | [^"&])* '"') | ("'" (PredefinedEntityRef | CharRef | EscapeApos | [^'&])* "'") So I was assuming that ampersands would always need to be escaped? And otherwise, "&" would be ambiguous, as long as the ampersand character *may* be escaped? 124139 3 mike 2015-11-09 17:23:00 +0000 Yes, of course, you are right: XQuery requires ampersands to be escaped in string literals. I have never understood why. 124254 4 andrew_coleman 2015-11-18 13:41:44 +0000 The WG decided to adopt the proposal described in the following message https://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0035.html This also addresses bug 29272