This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
XSLT defines a set of addtional functions to the standard XPath functions. While some of them are XSLT specific, like current() and key(). Many are quite generic and useful under the XPath/XQuery context, like generate-id(), format-number(), format-dateTime(), etc. Is there any intension to merge some of these functions into the core libraries? Or is there any reason they are left out?
There's never been any desire to add functionality to XPath or XQuery simply because it was already present in XSLT (whether in XSLT 1.0 or 2.0): each language has its own set of requirements, and while there has been a lot of effort to achieve commonality in areas where the languages have overlapping requirements, the aim for both XPath and XQuery has been to keep the language as small as possible consistent with meeting its stated requirements. Many of the XSLT-specific functions are concerned with providing presentation and rendition capability, which is not seen as a core requirement for XQuery (it's not explicit in the published requirements, at any rate: I agree that many people would like to use the language for that purpose and will find the absence of format-number and format-date frustrating.). We'll soon be starting a process of gathering requirements for XQuery version 2.0 and that will be the right time for this kind of comment. It's too late to affect version 1.0. Michael Kay (personal response)
Henry, thank you for your comment. It really is not a "bug" or comment on XSLT so I am closing it against XSLT; however, if you wish to pursue this you may resubmit the comment against the F&O spec, although I fully concur with the answer provided by Mike Kay. If for some reason you wish to push back please reopen the bug indicating your rationale why you think this should be processed as an XSLT 2.0 comment. Thanks again for your comment. Sharon