30197 2017-11-16 18:50:15 +0000 [SER31] Adaptive serialization does not specify xs:float, and no decimal format for xs:decimal and xs:float 2018-01-03 13:46:32 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Serialization 3.1 Recommendation PC Windows NT CLOSED WORKSFORME P2 normal --- 1 abel.braaksma cmsmcq andrew_coleman public-qt-comments oldest_to_newest 128969 0 abel.braaksma 2017-11-16 18:50:15 +0000 This applies to the Adaptive Output Method: For xs:double the specified format is scientific notation. For xs:float, such format is not specified, which I think is an oversight. It should probably be the same as xs:double, albeit with less precision. Also, for neither xs:decimal and xs:float, the decimal format properties are specified. This was discussed earlier through bug 29824, but only applied to xs:double, not the other two. 129016 1 andrew_coleman 2017-12-14 10:40:04 +0000 I agree that xs:float should follow the same rule as xs:double. I can make that change in the errata doc. xs:decimal is specified as follows: - An instance of xs:integer or xs:decimal is serialized by converting the value to a string using the fn:string function. F&O specifies this behaviour: https://www.w3.org/TR/xpath-functions-31/#casting-to-string which in turn references the schema spec: https://www.w3.org/TR/xmlschema-2/#decimal-canonical-representation I don't think the decimal format properties are relevant to this. 129021 2 andrew_coleman 2017-12-19 16:52:21 +0000 The WG discussed this and decided that the current rule for serializing xs:float is well defined and expresses the desired intent. - An atomic value of any other type is serialized using the syntax of a constructor function... 129043 3 abel.braaksma 2018-01-03 13:46:02 +0000 Ok, if that was intentional (and I can see now why it is), than it wasn't a bug. Thanks and happy New Year!