This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
According to XQ31, the xs:decimal type minimum value for the maximum number of decimal digits (totalDigits facet) is 18. The test same-key-006 requires greater precision than is required by the specification. xs:decimal("1.00000000000000000000000000000000001")
Would you like an alternate result? FOCA0001?
(In reply to Josh Spiegel from comment #1) > Would you like an alternate result? FOCA0001? Either that, or reduce the decimals to use the minimum 18 digits. xs:decimal("1.00000000000000001") xs:decimal("1.00000000000000002") I have to say, I'm struggling with a few of these tests as there is no built-in arbitrary (or sufficiently high) precision decimal in .NET to which I can convert a double, float or integer/decimal.
I guess that would work too since they still map to the same double. > I have to say, I'm struggling with a few of these tests as there is no built-in arbitrary (or sufficiently high) precision decimal Mike suggested at some point that implementations like yours could fake it by using strings. It sounds plausible to me but I haven't fully thought it through.
We're off-topic here, but some people recommend using the J# library. We're having to use a 3rd party library for xs:decimal in our Javascript product, it's not the end of the world...
(In reply to Michael Kay from comment #4) > We're off-topic here, but some people recommend using the J# library. > > We're having to use a 3rd party library for xs:decimal in our Javascript > product, it's not the end of the world... I'm going to ask for this to be put on the agenda for next week. I'll post to the mailing list my thoughts on the subject.
At the meeting on 2016-06-14, the WG agreed to adopt the solution in comment #2. Action A-646-04 will track this.