Sounds good. I really do need to take a look at what you've been working on. When IBM implemented 3.0 we started with the API and data model work needed to migrate Xalan to the XSLT3 data model rather than from the "what could be back-ported to 2.0" angle, so I don't have a good handle on the latter. Now that I've had a year to think about it, the latter is not an unreasonable incremental step, if we think people will really use that combination.
In addition to new utilities and schema data types, 3.0 changes some semantics, specifically in removing the distinction between node sets and temporary trees (which has always been a bit frustrating). It isn't clear whether we could get away with that one and still claim 2.0 conformance; negative tests which detect the difference would fail. Have you been avoiding that (eg building automatic conversion into your new functions), or are you working to the 2.0 definitions? (My own highest architectural priority would be getting us into cursors rather than DTM iterators, which would give us a path toward 3.0 semantics and make running over data other than DTM much simpler... but I'm biased; the cursor cutover was my baby, all those years ago. And it's not a small change.) -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! ________________________________ From: Mukul Gandhi <[email protected]> Sent: Tuesday, September 12, 2023 9:13:02 AM To: [email protected] <[email protected]> Subject: Re: xalanj new release proposal Hi Joseph, On Tue, Sep 12, 2023 at 5:58 PM Joseph Kesselman <[email protected]> wrote: > > I'd like to take a better look at what we've got before opining on that. That's fine. Please take your time to work on XalanJ issues, that you're interested to work on. > I presume you've been committing conformance tests for the new functions > along with their implementations? I'm writing below, about the XalanJ implementation that we've added to dev repos branch xalan-j_xslt3.0. The JUnit java class https://github.com/apache/xalan-java/blob/xalan-j_xslt3.0/tests/org/apache/xalan/xslt3/AllXsl3Tests.java, is an entry point to invoke the whole of XSLT 3.0 + XPath 3.1 combined tests that we've written so far. [1] The folder https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0/tests/org/apache/xalan/xpath3, has all the XPath 3.1 related tests that we've written so far (which contains, tests for XPath 3.1 functions, operators, and expressions). [2] And folder, https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0/tests/org/apache/xalan/xslt3, has all the tests for XSLT 3.0 related implementation that we've added to XalanJ. [3] The JUnit test suite at [1] is a sum of tests at location [2] and [3]. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
