- From: <bugzilla@jessica.w3.org>
- Date: Tue, 27 May 2014 15:46:16 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25444 C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cmsmcq@blackmesatech.com --- Comment #5 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> --- The XSLT and XML Query WGs discussed this bug (and the technically equivalent one, bug 20631) in our joint call today. Please note that there is no significant difference, for purposes of these two WGs, between the statuses of New and Assigned. Closing this bug as a duplicate of bug 20631 is not an indication that the WG has changed its mind about anything; it is at most an indication that bug 20631 was here first. Since each bug points to the other, any discussion of bug 20631 will be informed by the discussion here. The upshot of our discussion today was to establish that no one seems to have any objections to the solution as outlined in [1], which proposes xs:integer, xs:decimal, xs:double, xs:float as the order of members (noting that it replicates the priorities used in casting numeric literals, and noting also that xs:integer is redundant for use of xs:numeric as a sequence type, and xs:float is redundant when it comes to casting behavior). So -- no worries, the xs:numeric type is coming, as soon as we get through the coordination issues with the custodians of the XSD spec and namespace. [1] https://lists.w3.org/Archives/Member/w3c-xsl-query/2014May/0053.html (member-only link) -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 27 May 2014 15:46:18 UTC