I think there is now a consensus that changing the namespace with a new
version of a standard is a bad idea, because it causes such inconvenience; but
that doesn't help you.

As has been mentioned, XPath 2.0 offers `*:local` to match a specific local
name in any namespace, and XPath 4.0 introduces the option to allow unprefixed
element names to match in any namespace by default. There's no option to match
a list of namespaces, though I've often thought it would be a good idea.

There's another option which hasn't been mentioned, which is to preprocess the
source documents to standardise the namespace. That also enables you to handle
other variations in the vocabulary. Basically, use a processing pipeline in
which the first step is to normalize the vocabulary, so that subsequent steps
don't have to deal with variations.

Michael Kay
Saxonica

> On 12 May 2026, at 01:16, 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/293509> (by
email <>)