Hi all,
    Due to an unknowing issue with the previous mail that I've sent as
mentioned within mail trail, the URL of codebase repos branch got
specified as https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0_mvn.
(with an erroneous period suffix character). The correct URL is
https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0_mvn (this
code repos branch also has a test suite with corresponding README
document. The test suite can be run to verify integrity of the
implementation wrt W3C XSL 3.0 specifications).

If I need to provide any clarification about this work, please let me
know and I shall try my best to answer questions wrt this.

I'm also copying this mail to Joseph Kesselman (Xalan PMC member) &
Gary Gregory (Xalan PMC chair), who have also been working on this
implementation.

With best wishes.

On Sun, Feb 2, 2025 at 11:05 AM Mukul Gandhi <muk...@apache.org> wrote:

>  Apache Xalan team wrote much of XSL 3 spec's implementation (I
> wrote lot of Java code for this enhancing upon lot of Xalan code
> that's within jdk's XML api implementations). Here's url of codebase
> repos branch for this,
> https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0_mvn.
>
> Is it kindly possible for someone on this list, to look at this code
> repos branch and study feasibility of including these Xalan
> implementation changes to future jdk release. It may also be helpful
> to have these code changes to be part of a possible jdk 1.8 compliant
> service pack. It is requested please someone to have git clone of this
> code repos branch since there are chances for having code on this
> repos branch to change.
>
> I wrote this request mail, initially to Sharat Chander who works with
> Oracle (Senior Director, Product Management & Developer Engagement).
> He advised me to post this request to, this mail list to try having
> this request fulfilled.
>
> Hoping that this list shall oblige with this request over the next few
> weeks, or months.
>
> Many thanks.



-- 
Regards,
Mukul Gandhi

Reply via email to