This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As a follow-on from RQ-150 (clarify the minimum implementation limits for decimal, and get them right), the WG recognized the need to specify analogous limits for precisionDecimal.
A separate proposal to resolve this issue is available at http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.b1919.20050831.html It raises the design question: what should the implementation minima for precision decimal be? Should they correspond to decimal32? decimal64? decimal128? (or perhaps the uninvented decimal16?)
I've marked this as a requirement (in the summary, and by making severity = critical), since RQ-150 is a requirement. This may be regarded, however, not as central to RQ-150, so the WG may wish to change these markings.
A proposal to resolve this issue by requiring that implementations of XML Schema support the values representable using the decimal64 type of the draft IEEE 754 spec was approved by the WG in September 2005; the wording (modulo possible confusion about the actual limits to be required) was integrated into the status quo document 8 December 2005.
Although no formal request for closure was made, since the reporter also noted the resolution of this bug over two years ago, I'm marking it closed.