27360 2014-11-18 15:29:10 +0000 "string value" is not defined for atomic values 2014-11-25 16:43:16 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Serialization 3.1 Working drafts PC All RESOLVED FIXED P2 normal --- 1 josh.spiegel cmsmcq andrew_coleman public-qt-comments oldest_to_newest 115058 0 josh.spiegel 2014-11-18 15:29:10 +0000 In section 9 it says: "An atomic valueXP31 in the data model instance of any other type is serialized to a JSON string by outputting the string value of the item." Where "string value" is linked to this definition: "The term string value is defined in Section 5.12 string-value Accessor DM31. Every node has a string value. For example, the string value of an element is the concatenation of the string values of all its descendant text nodes." String value is not defined for atomic values. 115297 1 andrew_coleman 2014-11-21 15:15:50 +0000 Good point. I propose replacing: "An atomic valueXP31 in the data model instance of any other type is serialized to a JSON string by outputting the string value of the item." with the following: "An atomic valueXP31 in the data model instance of any other type is serialized to a JSON string by outputting the result of applying the fn:string function to the item." 115301 2 josh.spiegel 2014-11-21 16:36:58 +0000 The input is a single atomic value in this case so I think calling fn:string is equivalent to $value cast as xs:string. So you could be more specific and say "... a JSON string by outputting the result of casting the value to xs:string." But this is editorial - I think your proposal is correct.