Re: XMLn’t in XML Calabash 3.0.16

On 10/6/25 2:43 AM, Norm Tovey-Walsh wrote:

> David Cramer<david@thingbag.net> writes:
>> 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.
> What would you like the processor to do about unresolvable entities in attribute values?
>
I think the only option is a PI that encodes the location of the 
unresolved entity:

    <imagedata fileref="../../&unresolvedEntity;/duck.png"/>

Could become something like:

    <imagedata fileref="../..//duck.png">
          <?xmlnt name="unresolvedEntity" location="/full/xpath/to/imagedata/@fileref/string()" before="../../" after="/duck.png"/>
    </imagedata>

The use case is to provide the schematron developer with everything they 
need to construct useful error messages downstream for the person 
debugging the failed pipeline run.

It's tempting to pick a string to wrap the entity name with, 
@@@unresolvedEntity@@@, but then its a matter of time before you have a 
positive and a confused author.

Regards,

David