- From: <bugzilla@jessica.w3.org>
- Date: Thu, 05 Mar 2015 18:45:30 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27613 Michael Kay <mike@saxonica.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |LATER --- Comment #6 from Michael Kay <mike@saxonica.com> --- In response to this comment, the XSL WG attempted to identify where there were differences between our current facilities and those described in TR35, and reviewed the opportunities for further alignment. See the following member-only links: https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015Feb/0002.html https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015Mar/0010.html For many of the missing features, the WG felt that XPath functions such as format-number() and format-integer() will usually used within the context of a Turing-complete programming language such as XSLT or XQuery, or at any rate a language offering conditional expressions, such as XPath. Facilities such as using different grouping positions based on the magnitude of the number could therefore be readily achieved using the facilities of the host language, and it would be a mistake to duplicate this functionality within the micro-language used for defining numeric pictures. (Indeed, given a free hand, we would probably drop some existing features such as support for percent and per-mille if we were starting today.) We did identify some features that are often requested by users, for example padding, which we would be favourably inclined to add to the spec if we were at a different stage of development; but since all these features have relatively straightforward workarounds by writing user-defined functions to achieve the task, we did not feel that these features were sufficiently urgent to justify delaying the progression of XSLT 3.0 to CR, or XPath 3.1 to PR. At the current stage of development we need to be brutal in rejecting "good ideas" that are not essential to completion. I am therefore closing this on the WG's behalf as "LATER", meaning that if we ever get the charter and resources to produce another version of XSLT or XPath, the comment will be taken into account as a candidate for inclusion in the requirements for that version. We thank the I18N group for drawing our attention to the opportunities in this area, and we are hopeful that you will accept our decision of the disposition. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 5 March 2015 18:45:32 UTC