This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Oops I discovered while commenting on bug 3248: Step 5 of the algorithm for precisionDecimalCanonicalMap begins "Otherwise, it will be the case that nV is less than 1E−6 or greater than 1E6." Actually, it should read "Otherwise, it will be the case that nV is less than 1E−6 or greater than 1E6 or aP is less than zero." I believe the actual subalgorithm under Step 5 is correct even in this added case.
Agreed 12 September 2008.
Fixed in the editorial proposal file:///C:/Documents%20and%20Settings/david_e3/Local%20Settings/Temporary%20Internet%20Files/OLK7/datatypes%200809dpmisc.html#rf-timezoneOffset Search on "6031" to find the relevant bit.
Seems the published draft [1] doesn't contain a fix for this bug. There is an "Editorial Note: Fix for bug 6031." (which shouldn't be there), but not the actual fix. [1] http://www.w3.org/TR/2009/WD-xmlschema11-2-20090130/
The status-quo version of Datatypes now has the following text for step 5 of the algorithm in question: Otherwise, it will be the case that nV is less than 1E−6 or greater than 1E6, or that aP is less than zero. From this fact, I infer that the correction has now been made successfully and that this bug report can be marked RESOLVED. Dave, as the originator of the issue, please CLOSE or REOPEN the bug to signal that you do or do not agree with the resolution. If the WG does not hear otherwise from you by this Friday, we will assume you are content.