Ideally, I would like to see us become a full 3.0 processor, and since XQuery is effectively just an alternative syntax for XSLT3, that would ideally be part of the package.
As I've said, we did a 3.0 implementation inside IBM, though it was a major rewrite in other ways as well. I'm still annoyed that got not only captured but lost inside Websphere. I don't think we have the resources to get there any time soon. We may never do so. But if I can get the backlog cleared out, it's one of the things I want to attempt. I think cutting over to XCI would be my first step in building the infrastructure for that. And possibly recreating the type-aware version of DTM, though in these days of larger memory it isn't clear DTM is a net win. -- /_ 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 <muk...@apache.org> Sent: Wednesday, October 11, 2023 10:41:57 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: Xalan retirement Hi Joseph, On Wed, Oct 11, 2023 at 6:46 AM Joseph Kesselman <kesh...@alum.mit.edu> wrote: > I expect there _will_ be future releases of Xalan-J, though even with my > return it's painful short-staffed. At this time true XSLT/XPath 3.0 and > XQuery support don't seem likely to happen any time soon I think, XalanJ has never worked on development and release of an XQuery processor earlier. i.e, XalanJ currently has zero implementation of XQuery. But XalanJ has existing XSLT 1.0 and XPath 1.0 implementations, and development XSLT 3.0 and XPath 3.1 codebases on dev repos branch xalan-j_xslt3.0. Do you mean, XalanJ should support XQuery implementation as well going forward? If yes, that's great as an idea and XalanJ's future product roadmap. But I think, implementing an XQuery processor within XalanJ is not a trivial task, and shall require significant effort and time. Also, I believe, an XPath 3.1 processor can be shared between XSLT 3.0 and XQuery (3.1 is latest version of XQuery) processors. IMHO, XalanJ can release XSLT 3.0 and XPath 3.1 processors, independently of releasing an XQuery processor. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
