Philip Helger

I changed it locally in my project in commit https://github.com/phax/ph-schematron/commit/7dbc1d4385c72ba1025c09d47dd4c3d01af23d92 and experiencing no problem using Saxon HE 9.7 or 9.8 (except that 9.8.0_1 and 9.8.0_2 were not usable but because...

Pragmatic approach: we basically need a different versioning scheme here. Use semantic version numbers (like 1.2.3), label the current version "1.0.0" (or whatever) and start with the next major release,...

I think the problem is, that nobody is actively maintaining this repository. Last change: 6 month ago...

@vincentml I'm more the Java guy (see https://github.com/phax/ph-schematron) and not the XSLT/Schematron guy. But if there is anything I can help (like batch execution or the like), drop me a...

Yes, it is still relevant :)

@mathieucarbou that feature was previously working and it should hopefully be a simple regression. Do you think you can tackle this one???

Which doesn't work for MIME messages when you have a flexible Content-Type as in `Content-Type: multipart/related; boundary="----=_Part_0_1057468716.1585071599240"; type="application/soap+xml"; charset=UTF-8`, as the model template requires a fixed Content-Type

Thanks @Stefan4112 - good suggestion. Let me see what I can do :)

Initial parts are contained in 2.7.5 release

Currently you need to use the implementation of BouncyCastle - it's not yet published in a release of xmlsec 3.x to the best of my knowledge. Link: https://github.com/apache/santuario-xml-security-java/pull/293