Thanks Sheila

The problem is the xpath in the templatesb& as Michael mentioned,
preprocessing makes more sense, especially when other tweaks change with the
new versionb&

Cheers,
L E O

> On 12 May 2026, at 10:27, Sheila Thomson coder@xxxxxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> You could match on element local-name instead of the full prefixed name,
eg.
>
> <template match="*:my-element" />
>
> or, if you need to check the namespace as well:
> <template match="*[namespace-uri() =
('urn:iso:std:iso:20022:tech:xsd:camt.054.001.04',
'urn:iso:std:iso:20022:tech:xsd:camt.054.001.08')][local-name() =
'my-element']" />
>
> Sheila
>
>
> On 12 May 2026 01:16:11 BST, "Leo Studer leo.studer@xxxxxxxxxxx"
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>> Hello
>>
>> The bank renewed the camt54 standard.
>>
>> In my stylesheet I need to access old and new bank statements
simultaneously.
>>
>> With
xpath-default-namespace="urn:iso:std:iso:20022:tech:xsd:camt.054.001.04b my
stylesheet works for the old documents and
>> with
xpath-default-namespace="urn:iso:std:iso:20022:tech:xsd:camt.054.001.08b it
does the job for the new documents.
>>
>> Is there an easy way to use either of the two namespaces so that my
stylesheet works for old and new bank statements?
>>
>> Thanks for caring!
>>
>> Yours, L E O
>>
>>
>>
>>
>>
>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
>> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/3368146> (by
email <>)
>
> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/945646> (by
email <>)