Oh, and since the question has been raised somewhere: I stumbled again upon this:

So, apparently, the namespace prefix is not merely the PAGE schema's choice, but actually had to enforce it.

I am not sure, if everything will still work out of the box, if we drop this, though. (IMHO it should stay, anyway.)

Oh, and since the question has been raised somewhere: I stumbled again upon this:

core/Makefile

Lines 234 to 238 in 255ddbd

	# hack to ensure output has pc: prefix
	@#sed -i "s/namespaceprefix_=''/namespaceprefix_='pc:'/" $(GDS_PAGE)
	sed -i 's/_nsprefix_ = None/_nsprefix_ = "pc"/' $(GDS_PAGE)
	# hack to ensure child nodes also have pc: prefix...
	sed -i 's/.*_nsprefix_ = child_.prefix$$//' $(GDS_PAGE)

So, apparently, the namespace prefix is not merely the PAGE schema's choice, but actually had to enforce it.

I am not sure, if everything will still work out of the box, if we drop this, though. (IMHO it should stay, anyway.)

I think we did introduce this not because we explicitly wanted a pc: prefix, but because generateDS did generate XML which used the pc: prefix for the elements but did not define it, i.e. that was a bug in generateDS.

It's also sensible IMHO because in the docs, we always use pc: for PAGE and mets: for METS. I also just personally prefer it that way, but that's not a strong argument ;)

In any case, thanks for the update, I'll test it and let's discuss the ramifications. I do like the features, I fear the repercussions of keeping PAGE-XML in different versions interoperable...

Just for reference: the version of page.xsd I used here is exactly the one from current PRImA master – just without carriage return EOL (because that would have made for a very big diff).

As you have pointed out on other channels, it seems there was already a decision made by PRImA to release a 2024 namespace – just not public on their Github. In that changelog they unfortunately attribute

• MapRegion can now be used recursively (nested in other regions)

to the 2024 version, not the 2019 version, which indicates they are not willing to let this be covered as a mere bugfixing postrelease (as in the other patch release for 2019). IMHO this is not a good decision (if it is deliberate at all)