W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2016

[Bug 29419] [XP31] edge case with negative integer literals (UnaryExpr) and limits for -9223372036854775808, which cannot be parsed

From: <bugzilla@jessica.w3.org>
Date: Tue, 14 Jun 2016 18:40:19 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29419-523-a9vcwvlChy@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29419

Jonathan Robie <jonathan.robie@gmail.com> changed:

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

--- Comment #16 from Jonathan Robie <jonathan.robie@gmail.com> ---
Today, we decided to resolve this as follows.

For XPath, add the following note to the section on literals:

<add>
The XSD specification allows implementations to impose a limit (which
must not be less than 18 digits) on the size of integer and decimal
values. The full range of values of built-in subtypes of xs:integer,
such as xs:long and xs:unsignedLong, can be supported only if the
limit is 20 digits or higher. Negative numbers such as the minimum
value of xs:long (-9223372036854775808) are technically unary
expressions rather than literals, but implementations may prefer to
ensure that they are expressible.
</add>

For XQuery, add the following sentence:

<quote>
For the xs:decimal type, the maximum number of decimal digits (totalDigits
facet) (MUST be at least 18). <add>This limit SHOULD be at least 20 digits in
order to accommodate the full range of values of built-in subtypes of
xs:integer, such as xs:long and xs:unsignedLong.</add>
</quote>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 14 June 2016 18:40:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:00 UTC