Re: xpath 3.1 implementation activity
"Joseph Kesselman via dev" <[email protected]> Sun, 24 May 2026 18:04:15 +0000
| Newsgroups | gmane.text.xml.xalan.devel |
|---|---|
| Message-ID | <MN2PR12MB42210C933349163711C22B4F9E0D2@MN2PR12MB4221.namprd12.prod.outlook.com> |
--_000_MN2PR12MB42210C933349163711C22B4F9E0D2MN2PR12MB4221namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The old test driver uses a mix of ways to invoke tests, since some of it te= sts the language (with input samples and expected output) and some of it te= sts our APIs. It also has hooks intended to allow running it against other = processors. When we started work on it we were one of the first groups to w= rite an XSLT regression test suite; I think we had one before the recommend= ation committee did. I haven't looked at what they've done for 3.1; I don't know how hard it wou= ld be to drop that into our framework. NOTE: Our current framework relies on being driven by Ant, and has a lot of= ad-hoc code, including using Tidy as a basic HTML parser for serializer-se= nsitive tests which should be compared semantically rather than byte for by= te. It does the job but as part of keeping it portable to other processors = (including those written in other languages) it is moderately ugly. Writing= a new test driver might be worth considering, but we would need to establi= sh whether and how testing other implementations is still required. It woul= dn't be a huge task, probably less than my Maven effort, but doing it right= is nontrivial. If you are going to consider a new test driver, you might w= ant to spend some time resolving that, and at least understanding what conc= erns went into xalan-test so you don't repeat some of the mistakes we made = along the way. If we *can* make a portable test suite Someone Else's Problem, pointing the= m to an unmaintained copy of the old xalan-test, that might let us simplify= things substantially. -- Joe (Typo'ed on my phone.) Car Talk has been advised that the staff opticians, C. F. Eyecare, are now = under new management. It's Ike and Zeke Leary, now; Lorraine is gone. ________________________________ From: Mukul Gandhi <[email protected]> Sent: Sunday, May 24, 2026 11:29:54 AM To: [email protected] <[email protected]> Subject: xpath 3.1 implementation activity Hello Xalan-J team, Little bit of information, related to Xalan-J xslt3.0 development acti= vity. I'm trying to write few XPath 3.1 test cases, from W3C XPath 3.1 test suite into Xalan-J xslt3.0 development branch. I think ideally, we should have an XSL test driver for these test cases, similar to what we have for XSL test cases that we already have within Xalan-J xslt3.0 development branch. W3C XPath 3.1 test suite's schema is little bit different than, W3C XSLT 3.0 test suite's schema. Due to this, I'm currently writing few of these XSL test cases manually within Xalan-J xslt3.0 repos test area. I'm trying to find Xalan-J XPath 3.1 implementation bugs and unimplemented XPath 3.1 features, that I could possibly solve by this activity. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --_000_MN2PR12MB42210C933349163711C22B4F9E0D2MN2PR12MB4221namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > </head> <body> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> The old test driver uses a mix of ways to invoke tests, since some of it te= sts the language (with input samples and expected output) and some of it te= sts our APIs. It also has hooks intended to allow running it against other = processors. When we started work on it we were one of the first groups to write an XSLT regression test sui= te; I think we had one before the recommendation committee did.</div> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> <br> </div> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> I haven't looked at what they've done for 3.1; I don't know how hard it wou= ld be to drop that into our framework.</div> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> <br> </div> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> NOTE: Our current framework relies on being driven by Ant, and has a lot of= ad-hoc code, including using Tidy as a basic HTML parser for serializer-se= nsitive tests which should be compared semantically rather than byte for by= te. It does the job but as part of keeping it portable to other processors (including those written in oth= er languages) it is moderately ugly. Writing a new test driver might be wor= th considering, but we would need to establish whether and how testing othe= r implementations is still required. It wouldn't be a huge task, probably less than my Maven effort, but doing = it right is nontrivial. If you are going to consider a new test driver, you= might want to spend some time resolving that, and at least understanding w= hat concerns went into xalan-test so you don't repeat some of the mistakes we made along the way.</div> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> <br> </div> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> If we *can* make a portable test suite Someone Else's Problem, pointing the= m to an unmaintained copy of the old xalan-test, that might let us simplify= things substantially.</div> <div id=3D"ms-outlook-mobile-body-separator-line" data-applydefaultfontstyl= es=3D"true" dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, = -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;"> <div style=3D"font-family: Aptos, Aptos_MSFontService, -apple-system, Robot= o, Arial, Helvetica, sans-serif; font-size: 12pt;"> <br> </div> </div> <div id=3D"ms-outlook-mobile-signature" dir=3D"auto" style=3D"font-family: = Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-s= erif; font-size: 12pt; color: rgb(33, 33, 33);"> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> <br> </div> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> --</div> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> Joe (Typo'ed on my phone.)</div> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> <br> </div> <div dir=3D"auto" style=3D"font-family: Aptos, Aptos_MSFontService, -apple-= system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(3= 3, 33, 33);"> Car Talk has been advised that the staff opticians, C. F. Eyecare, are now = under new management. It's Ike and Zeke Leary, now; Lorraine is gone.</div> </div> <hr style=3D"display:inline-block;width:98%" tabindex=3D"-1"> <div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st= yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Mukul Gandhi <gand= [email protected]><br> <b>Sent:</b> Sunday, May 24, 2026 11:29:54 AM<br> <b>To:</b> [email protected] <[email protected]><br> <b>Subject:</b> xpath 3.1 implementation activity</font> <div> </div> </div> <div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;= "> <div class=3D"PlainText">Hello Xalan-J team,<br> Little bit of information, related to Xalan-J xslt= 3.0 development activity.<br> <br> I'm trying to write few XPath 3.1 test cases, from W3C XPath 3.1 test<br> suite into Xalan-J xslt3.0 development branch.<br> <br> I think ideally, we should have an XSL test driver for these test<br> cases, similar to what we have for XSL test cases that we already have<br> within Xalan-J xslt3.0 development branch.<br> <br> W3C XPath 3.1 test suite's schema is little bit different than, W3C<br> XSLT 3.0 test suite's schema. Due to this, I'm currently writing few<br> of these XSL test cases manually within Xalan-J xslt3.0 repos test<br> area. I'm trying to find Xalan-J XPath 3.1 implementation bugs and<br> unimplemented XPath 3.1 features, that I could possibly solve by this<br> activity.<br> <br> <br> -- <br> Regards,<br> Mukul Gandhi<br> <br> ---------------------------------------------------------------------<br> To unsubscribe, e-mail: [email protected]<br> For additional commands, e-mail: [email protected]<br> <br> </div> </span></font></div> </body> </html> --_000_MN2PR12MB42210C933349163711C22B4F9E0D2MN2PR12MB4221namp_--