W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2013

[Bug 21619] wrong results when handeling -0 negativeZero

From: <bugzilla@jessica.w3.org>
Date: Tue, 09 Apr 2013 08:44:18 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-21619-523-588pQIlcQC@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21619

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
(In reply to comment #2)
> It's odd that decimal doesn't support -0 while float and double does.

Well, in my view the concept of negative zero is pretty odd to start with, but
who are we to argue?
 The
> XMLSchema 1.1 it not very clear, defines the value space of decimal by using
> the value space of integer, while the value space of integer says only: "The
> ·value space· of integer is the infinite set {...,-2,-1,0,1,2,...}." 

I think we can be glad that the XSD designers took a few concepts as given,
rather than attempting to formalize the whole system of arithmetic...
> 
> If this means that there is no -0 as a decimal, which means that the test
> case prod-OrderByClause/orderBy20 and orderBy21 have the wrong result. 
> 
I have no idea why these tests include more than one permitted result, but the
reason they include -0 in the result is that the query is returning the
orderData elements, not their atomized values. However (I think), an
implementation is permitted to retain the typed value rather than the string
value, and to reconstitute the string value on serialization, and such an
implementation could legitimately output <orderData>0</orderData> rather than
<orderData>-0</orderData>.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 9 April 2013 08:44:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:52 UTC