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
