Hi Joseph, On Mon, Jun 10, 2024 at 2:51 AM Joseph Kesselman <kesh...@alum.mit.edu> wrote:
> I would still like to fold the 3.0 prototypes into the mainline branch at > some point, while keeping their prototype nature clear. While I still think > making them an extension package is the cleanest solution architecturally, we > *could* consider adding them as built in but in a separate namespace; that > wouldn't be as clean a code separation but would at least require that users > be aware that they are using something 2.0 doesn't support. I'd prefer an > extension-like Xalan-specific namespace since we aren't providing the rest of > 3.0, but if my arm is twisted hard enough I might be willing to see them in > the W3C's XSLT 3.0 namespace. One useful activity that I see as useful to be done, on Xalan-J dev repos branch xalan-j_xslt3.0 before we make the 1st Xalan-J XSL 3 subset release, is following: We test and verify that, Xalan-J's extension element and, extension function mechanism hasn't broken and works exactly like before. Either someone other than me, may try to do this on dev repos branch xalan-j_xslt3.0, or I'll do this before I shall conclude my XSLT 3 implementation work on Xalan_j dev repos branch xalan-j_xslt3.0. [1] About your suggestion, to change existing code on Xalan-J dev repos branch xalan-j_xslt3.0, to have all of XSLT 3.0's existing implementation to be in a non-standard namespace. This suggestion appears to me kind of ok, because when we'll be ready to release Xalan-J's fully compliant (most likely with XSLT 3 basic conformance) XSLT 3.0 processor, we'll change that non-standard namespace to W3C's XSLT 3.0 namespace. But also, IMHO (personal opinion, and sorry, about saying like this) [1] appears to me as a non-essential effort, which I feel shall also appear as wasted effort later on. For now, continuing development on Xalan-J's dev repos branch xalan-j_xslt3.0, for XSLT 3.0 standard elements in the W3C's XSLT 3.0 namespace, gives me personally clarity and momentum to continuing working on these tasks. I also think that, if you, or Gary wish to do anything concrete (like, modifying 'code', 'build process' etc) on Xalan-J dev repos branch xalan-j_xslt3.0, you can do those things anytime, and I shall adjust my dev activity accordingly. You both are Xalan-J PMC members and committers :) -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
