so

SInclude 5.5.0

Volume 9, Issue 14; 08 Aug 2025

I’ve migrated and updated my “Saxon XInclude” processor.

In preparing my Balisage talk, I discovered that the SInclude “search” fragment identifier scheme didn’t parse RFC 5147 integrity constraints correctly. I fixed that.

In the course of doing that, I had a huge fight with the Maven Central publication process that turned out, naturally, to be me being careless. (I accidentally created the token secret with a trailing new line that sent the curl post into fits).

Anyway, having fought for two days, I decided to fight for another few hours and migrate the repository to Codeberg. That was interesting: I need to write myself some better notes. I regret that I failed to preserve all of the history. Mea culpa.

I’ve published the release on Codeberg and pushed it to Maven.

And I moved the documentation as well, but it’s still generated as part of the build so it stays mostly up-to-date.

#XML

Please provide your name and email address. Your email address will not be displayed and I won’t spam you, I promise. Your name and a link to your web address, if you provide one, will be displayed.

Your name:

Your email:

Homepage:

Do you comprehend the words on this page? (Please demonstrate that you aren't a mindless, screen-scraping robot.)

What is nine plus six?   (e.g. six plus two is 8)

Enter your comment in the box below. You may style your comment with the CommonMark flavor of Markdown.

All comments are moderated. I don’t promise to preserve all of your formatting and I reserve the right to remove comments for any reason.