[Bug 29736] [FO31] C.2 Schema for the result of fn:json-to-xml

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29736

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 20 July 2016 10:43:17 UTC