Re: XMLn’t in XML Calabash 3.0.16

A Saturday morning well-spent and I like the name XMLnt!

The only other out-of-the-box tool that I know of that attempts this is 
Oxygen's Refactoring Tool (and also their XSLTOperation which you 
typically use in the context of an Action). They have to handle things 
like attribute order, population of default attributes, etc too. IIRC, 
they are forced to punt on CDATA escaping.

Another common build pipline use case to consider would be a validation 
mode where you resolve the entities that you can resolve but leave 
markup breadcrumbs (PIs?) for un-resolvable entities so that it's 
possible to provide useful warnings to users via a downstream 
schematron. The goal here would be to avoid failing hard at the first 
whiff of trouble. Pipeline users are much happier if you can tell them 
/all/ the things they need to fix or at least as many as you can 
reasonably detect rather than failing hard with an ugly stack trace at 
the first one and making them debug and rerun the pipeline over and 
over. Schematron also lends itself to very clear, detailed error 
messages so the pipeline user knows exactly how to resolve the issue. In 
this validation use case, the tricky things about white space 
normalization, attribute order, CDATA, etc are irrelevant.

Regards,

David

On 9/7/25 10:50 AM, Norm Tovey-Walsh wrote:
> Hello,
>
> If anyone has been curious about the XMLn’t parser[1][2] that came about following our discussion at the last XProc user group meeting,
> it’s in XML Calabash 3.0.16 released earlier today.
>
>                                          Be seeing you,
>                                            norm
>
> [1]https://so.nwalsh.com/2025/08/31-xmlnt
> [2]https://docs.xmlcalabash.com/userguide/current/xmlnt.html
>
> --
> Norm Tovey-Walsh<ndw@nwalsh.com>
> https://norm.tovey-walsh.com/
>
>> My dog is worried about the economy because Alpo is up to 99 cents a
>> can. That's almost $7.00 in dog money.--Joe Weinstein