<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 3/1/25 10:19 PM, Mukul Gandhi wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:CABuuzNOYJtV9b+x4AAi4Yg8JpFmhbdz52ONO=fgpz5Q4RVgJzA@mail.gmail.com">
      
      <div dir="auto">Hi Joe,
        <div dir="auto">    Thanks for nice thoughts.<br>
          <br>
          <div class="gmail_quote" dir="auto">
            <div dir="ltr" class="gmail_attr">On Fri, 28 Feb, 2025,
              00:06 Joe Wang, <<a href="mailto:huizhe.wang@oracle.com" rel="noreferrer noreferrer noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">huizhe.wang@oracle.com</a>>
              wrote: </div>
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
              What's your assessment on the readiness for a formal
              release (or how <br>
              much additional work is needed)? What are the conformance
              test results?<br>
            </blockquote>
          </div>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">The link here, <a href="https://urldefense.com/v3/__https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0_mvn__;!!ACWV5N9M2RV99hQ!OqtC527gdej0VCBFTK7nmgy16OxpR-nNdOtLNNCE6OgHGcXoGC66GPEDSBTdcPEAk5gO-8fG5s86DRxOAw$" target="_blank" rel="noreferrer" moz-do-not-send="true">https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0_mvn</a>
          has a pdf link at bottom of that page which is Xalan-J XSL 3
          implementation's latest development status. This link also has
          documentation about how to run Xalan-J's XSL 3 conformance
          test suite, which currently has 900+ odd tests supported by
          Xalan-J covering wide areas of XSLT 3.0 and XPath 3.1 language
          features.</div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>Great work. Are the tests counted differently? The W3C test suite
      for XSLT 3.0 is said to "contain over 11,000 test cases". What
      would be the pass rate if measured against the W3C test suite?</p>
    <p><br>
      -Joe<br>
    </p>
    <blockquote type="cite" cite="mid:CABuuzNOYJtV9b+x4AAi4Yg8JpFmhbdz52ONO=fgpz5Q4RVgJzA@mail.gmail.com">
      <div dir="auto">
        <div dir="auto">
          <div dir="auto"><br>
          </div>
          <div class="gmail_quote" dir="auto">
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <br>
              Also, do you have data showing how the Xalan-J's XSL 3
              implementation is <br>
              used in user applications? What are the feedback (or bug
              reports) from <br>
              developers?<br>
            </blockquote>
          </div>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">I know of few people, particularly <a href="https://urldefense.com/v3/__https://x.com/XSLT_knowmad?t=ZKJE2bkeVyceZTxTmy1sPg&s=09__;!!ACWV5N9M2RV99hQ!OqtC527gdej0VCBFTK7nmgy16OxpR-nNdOtLNNCE6OgHGcXoGC66GPEDSBTdcPEAk5gO-8fG5s_0qbsB_Q$" moz-do-not-send="true">https://x.com/XSLT_knowmad?t=ZKJE2bkeVyceZTxTmy1sPg&s=09</a>
          and probably others who've been using Xalan-J's XSL 3
          implementation. Gary Gregory (Apache Xalan's PMC chair) has
          also rigorously tested Xalan-J's XSL 3 implementation and
          reported it to be ok and useful.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Many thanks.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Regards,</div>
        <div dir="auto">Mukul</div>
        <div dir="auto">
          <div dir="auto"><br>
          </div>
          <div class="gmail_quote" dir="auto">
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <br>
              On 2/26/25 7:59 AM, Mukul Gandhi wrote:<br>
              > Hi Alan,<br>
              >      I've just seen this mail from you. Apologies for
              a delayed response.<br>
              ><br>
              > My mail box has had few issues due to the volume of
              mails that I get<br>
              > from mailing lists.<br>
              ><br>
              > On Sun, Feb 2, 2025 at 9:38 PM Alan Bateman <<a href="mailto:alan.bateman@oracle.com" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">alan.bateman@oracle.com</a>>
              wrote:<br>
              ><br>
              >> The stats for that branch suggest 5,845 changed
              files with 234,372 additions and 84,058 deletions. I can't
              easily tell how much of this would need to come into the
              jdk repo but this looks like a major update. If only 10%
              of this is applicable to the JDK then it still needs seems
              like a major update that would require a huge investment
              to audit and integrate this code. How much XML is in new
              applications developed in 2025? Only asking because it's
              an area that is surely much lower priority compared to all
              the other major investments right now. Maybe there are
              useful security or performance changes that would be
              useful to cherry pick instead? Finally, does this Xalan
              update work with the SPIs so that someone really looking
              for XSL 3 can just deploy it on the class path and module
              path?<br>
              > Ofcourse, anyone could use Xalan-J's XSL 3
              implementation with JDK by<br>
              > placing Xalan jars on class path & module path.<br>
              ><br>
              > Since Xalan-J's XSLT 1.0 & XPath 1.0
              implementations are already<br>
              > available within JDK, I thought its natural if JDK
              could pick<br>
              > Xalan-J's XSL 3 implementation and include that
              within JDK. I can<br>
              > imagine that this may surely be time consuming for
              someone from JDK<br>
              > team to integrate with JDK. XSLT 1.0's use I think is
              very less these<br>
              > days particularly for new XML projects, due to vast
              improvements in<br>
              > language features offered by XSLT 3.0 and XPath 3.1.<br>
              ><br>
              > IMHO, I wrote all the XSL 3 implementation code (and
              solved various<br>
              > XSL 3 implementation bugs reported by community on
              Xalan-J's dev<br>
              > forum) within Xalan-J's XSL 3 dev respos branch,
              enhancing upon<br>
              > Xalan-J's XSLT 1.0 implementation. From my point of
              view, I'll be<br>
              > happy if JDK could include Xalan-J's XSL 3
              implementation.<br>
              ><br>
              > I even wrote following two online articles on <a href="https://urldefense.com/v3/__http://xml.com__;!!ACWV5N9M2RV99hQ!OqtC527gdej0VCBFTK7nmgy16OxpR-nNdOtLNNCE6OgHGcXoGC66GPEDSBTdcPEAk5gO-8fG5s-ku_DmTQ$" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank" moz-do-not-send="true">xml.com</a> about
              few of XSL<br>
              > 3 language features, and how they're implemented
              within Xalan-J,<br>
              > <a href="https://urldefense.com/v3/__https://www.xml.com/articles/2024/07/22/string-analysis-with-analyze-string/__;!!ACWV5N9M2RV99hQ!OqtC527gdej0VCBFTK7nmgy16OxpR-nNdOtLNNCE6OgHGcXoGC66GPEDSBTdcPEAk5gO-8fG5s-o4MDiYw$" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank" moz-do-not-send="true">https://www.xml.com/articles/2024/07/22/string-analysis-with-analyze-string/</a><br>
              > <a href="https://urldefense.com/v3/__https://www.xml.com/articles/2023/12/05/xml-path-language-xpath-higher-order-functions/__;!!ACWV5N9M2RV99hQ!OqtC527gdej0VCBFTK7nmgy16OxpR-nNdOtLNNCE6OgHGcXoGC66GPEDSBTdcPEAk5gO-8fG5s_1qR7Epg$" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank" moz-do-not-send="true">https://www.xml.com/articles/2023/12/05/xml-path-language-xpath-higher-order-functions/</a><br>
              ><br>
              ><br>
              > Many thanks.<br>
              ><br>
              ><br>
              <br>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
  </body>
</html>