29736 2016-07-18 10:45:11 +0000 [FO31] C.2 Schema for the result of fn:json-to-xml 2016-12-16 19:55:28 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 3.1 Candidate Recommendation PC Windows NT CLOSED FIXED P2 normal --- 1 tim mike public-qt-comments oldest_to_newest 126966 0 tim 2016-07-18 10:45:11 +0000 Shouldn't key be use="required" in the following? <xs:attributeGroup name="key-group"> <xs:attribute name="key" type="xs:string"/> <xs:attribute name="escaped-key" type="xs:boolean" use="optional" default="false"/> </xs:attributeGroup> 126968 1 tim 2016-07-18 11:46:22 +0000 Also, we read <xs:simpleType name="finiteNumberType"> <xs:restriction base="xs:double"> <!-- exclude positive and negative infinity, and NaN --> <xs:minExclusive value="-INF"/> <xs:maxExclusive value="INF"/> </xs:restriction> But NaN is not excluded. 126970 2 mike 2016-07-18 12:05:50 +0000 Yes, I think it should (I always forget that attributes are optional by default, XSD is so inconsistent...) 126997 3 mike 2016-07-20 10:43:07 +0000 I have added use="required" as suggested in comment #0 (the WG agreed this change). I had overlooked comment #1, and this didn't come up in discussion. I believe the schema is correct here. Any minInclusive or maxInclusive constraint for xs:double has the effect of excluding NaN. For example, minExclusive says: A value in an ·ordered· ·value space· is facet-valid with respect to ·minExclusive· if and only if the value is greater than {value}, according to the datatype's order relation. NaN is not greater than negative infinity, therefore specifying a minExclusive of -INF also excludes NaN. This is elaborated in XSD 1.1 part 2 section 3.3.4.1 Note: Any value ·incomparable· with the value used for the four bounding facets (·minInclusive·, ·maxInclusive·, ·minExclusive·, and ·maxExclusive·) will be excluded from the resulting restricted ·value space·. In particular, when NaN is used as a facet value for a bounding facet, since no float values are ·comparable· with it, the result is a ·value space· that is empty. If any other value is used for a bounding facet, NaN will be excluded from the resulting restricted ·value space·; to add NaN back in requires union with the NaN-only space (which may be derived using the pattern 'NaN'). I'm marking this RESOLVED, but please re-open if you think this is still a problem.