Ideally, *if* you can structure these as clean extensions with only minimal/safe changes to Xalan core, we should be able to then pull them into the main branch with minimal, if any, conflicts, documenting them clearly as experimental with explanations of their known differences from the 3.0 Recommendation and a section explaining the rebinding-the-namespace trick for migrating these to/from a real 3.0 implementation.
You could then continue work as pull requests against the main branch, rather than having to maintain your own except as a transient development space. See Xalan's docs for how to write plug-in extensions, of course. I can open a task for that. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________ From: Mukul Gandhi <gandhi.mu...@gmail.com> Sent: Monday, March 18, 2024 2:32:38 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: xsl 4.0 draft specs, and xalan implementation Hi Joseph, > On Fri, Mar 15, 2024 at 9:19 PM Joseph Kesselman <kesh...@alum.mit.edu> wrote: > > Mukul: I haven't looked at the 3.0 prototypes in any detail yet. Would it > > be possible to restructure them as an extension set? Would you be willing > > to do so? If you want to make these available for folks to start playing > > with, I think that would be the best path forward for them, and for early > > 4.0 experimentation too. Is it possible, that you may please create XalanJ jira issue describing how you wish to have XalanJ's current XSLT 3.0 and XPath 3.1 implementations modified for these modification descriptions that you've mentioned? That shall be nice. I've following question as well, please. Do you wish to have these XalanJ implementation code modified in-place on the dev branch xalan-j_xslt3.0, or any other way you wish to have these implementation changes implemented? Please feel free to assign me to these mentioned tasks, if you'd like and I shall be happy to make those XalanJ implementation changes. Many thanks. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
