- From: Michael Kay <mike@saxonica.com>
- Date: Fri, 10 Nov 2023 21:20:50 +0000
- To: Norm Tovey-Walsh <norm@saxonica.com>
- Cc: Christian Grün <cg@basex.org>, "public-xslt-40@w3.org" <public-xslt-40@w3.org>, Dimitre Novatchev <dnovatchev@gmail.com>
I'm all in favour if we can find an incremental way forward. I think that issue #652 is part of this; we need to find a way for people to write function libraries that work across XSLT and XQuery without having to write all the code twice. And I think part of that is to deliver as much functionality of XSLT and XQuery as possible in the form of functions, so that the functionality is available in the common subset, XPath. Hence, for example, issue #573 node construction functions. The proposal for E"xxx" and L"xxx", providing a common format for string literals across XPath and XQuery, was also part of that thrust. Concerning load-xquery-module, I don't think that meets the need; we want something that injects function definitions into the static context. Michael Kay Saxonica
Received on Friday, 10 November 2023 21:21:09 UTC