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 3080 - Request that Schema 1.1 not advance until discussions held re: precisionDecimal
Summary: Request that Schema 1.1 not advance until discussions held re: precisionDecimal
Status: CLOSED DUPLICATE of bug 3120
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: PC Windows XP
: P1 major
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard: important, easy, pD cluster
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-04 17:36 UTC by Jim Melton
Modified: 2006-12-08 17:54 UTC (History)
0 users

See Also:


Attachments

Description Jim Melton 2006-04-04 17:36:18 UTC
The XML Query WG and the XSL WG were given a presentation on the precisionDecimal type that is included in the Last Call Working Draft of XML Schema 1.1.  Inevitably, inclusion of a new type in XML Schema requires that the type be considered in the context of XPath, XQuery, and XSLT. 

The integration of precision decimal into XPath, XQuery, and XSLT systems raises a number of questions about the numeric promotion hierarchy, the definitions of operators, and so forth.  In order that these two WGs be able to better understand how this type might, if adopted, be supported in those languages, we ask that you not move forward with precision decimal (i.e., not advance beyond Last Call status) until all three Working Groups (XML Query, XSL, and XML Schema) have had a chance to discuss the issues and reach consensus.  We propose that these discussions be held during the June meeting of the WGs.
Comment 1 Dave Peterson 2006-10-23 18:18:20 UTC
Am marking this a duplicate of 3120; according to the commenter (Jim Melton) they have the same effect; 3120 was (according to Melton) "more analytical, giving some additional reasons", so I'm marking this one the duplicate so that we work with the more complete of the two.

*** This bug has been marked as a duplicate of bug 3120 ***