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

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

--- Comment #14 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
(In reply to Jonathan Robie from comment #13)
> <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>
> 
> I think that fixes the problem.  Am I missing anything?
Are you sure about the "MUST be at least 18"? I thought we had established in
an earlier discussion that it must be at least 18 if you support XSD 1.0, and
at least 16 if you support XSD 1.1 (see
https://www.w3.org/TR/xmlschema11-2/#partial-implementation, first bullet).

> I was told to implement comment #8 and comment #11, which contradict
I believe the contradiction came from comment #8 being accepted with the
provision of comment #11 to remove the line on the actual limit (i.e., to *not*
mention the 16 or 18 digit limit). 

I think we should either choose to mention both, or neither, but not one limit.

> So I added one sentence to the existing statement in Conformance:
I can't find your changes in the current internal draft. Do you mean to say you
made only this change, or did you also incorporate MK's proposal of comment #8,
mentioning the error?

Do we keep a change-log? I mean, is XP31 supposed to link and mention every bug
that results in changes to the spec? I searched for 29419, but didn't see it.

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

Received on Tuesday, 14 June 2016 14:46:54 UTC