29872 2016-09-26 10:06:49 +0000 [FO31] escape=yes in parse-json() and json-to-xml() 2016-12-16 14:59:10 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 3.1 Candidate Recommendation PC All CLOSED FIXED P2 normal --- 1 mike mike public-qt-comments oldest_to_newest 127532 0 mike 2016-09-26 10:06:49 +0000 The rules for fn:parse-json say: If the escape option is set to true, escape sequences are retained in their escaped form, whether or not they represent valid characters. (This is in rule 3 underneath the options table. I would have expected to find it in the "escape=true" row of the table, but never mind.) This rule means that, for example, parse-json("\u0025" map{"escape":true()}) returns "\u0025" rather than "%". For the fn:json-to-xml() function I cannot find a corresponding rule. There doesn't seem to be anything that dictates whether "\u0025" should end up as <string escaped="true">\u0025</string> or as <string>%</string>. I suggest we adopt the same rule (and move it into the table, in both cases.) 127572 1 mike 2016-09-27 22:18:19 +0000 The changes were agreed and have been applied. 128329 2 mike 2016-12-16 14:59:10 +0000 This decision was subsequently reversed: see comment #11 et seq of bug #28812.