This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2087 - R-097: Problem with canonical rep'n of float/double
Summary: R-097: Problem with canonical rep'n of float/double
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.0 only
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-09 03:27 UTC by Sandy Gao
Modified: 2009-04-21 19:24 UTC (History)
0 users

See Also:


Attachments

Description Sandy Gao 2005-09-09 03:27:50 UTC
The existing text for the canonical representation for float/double reads:

Specifically, the exponent must be indicated by "E". Leading zeroes and the 
preceding optional "+" sign are prohibited in the exponent. For the mantissa, 
the preceding optional "+" sign is prohibited and the decimal point is 
required. For the exponent, the preceding optional "+" sign is prohibited. 
Leading and trailing zeroes are prohibited subject to the following: number 
representations must be normalized such that there is a single digit to the 
left of the decimal point and at least a single digit to the right of the 
decimal point. 
The problem is that the single digit to the left of the decimal point is 
allowed to be zero. This allows 1.0E1, 0.1E02 and 0.01E3 etc. as legal 
canonical representations for the same number.

See the following for a suggested resolution: 
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001OctDec/0214.html
Comment 1 Sandy Gao 2005-09-09 03:30:06 UTC
Discussed at the Feb. 14 concall:
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Feb/0087.html 

The WG agreed that this is an error. Datatypes editors to draft erratum 
similiar to what was proposed in the email. 

Status 04/24: Erratum text has been proposed as part of the text for issue R-22 
(see bug 2000 and E2-40)