Publish 2025-1-RC5 #269

What

Cut and publish release candidate 2025-1-RC5, reflecting the terminology
and bibliography alignment merged in #267 (ISO/IEC FDIS 20151-1, ISO/IEC
38500:2024, ISO/IEC 7498-1:1994).

Steps

• Merge feat(terminology): align dataspace definitions with ISO/IEC FDIS 20151-1 #267
• Merge the release-prep PR (release/2025-1-rc5 → main)
• Tag the chore: publish 2025-1-RC5 commit as 2025-1-RC5 and push the tag
• Re-run the Auto-Publish workflow so it picks up the new tag
• Verify https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1-RC5/ renders correctly

⚠️ Merge method for the release-prep PR

This PR must be merged with "Rebase and merge", not "Squash and merge".

The release-prep branch carries two commits on purpose: one that flips
specStatus to "base" and sets publishDate (this is the commit the git
tag needs to point at), and a second that reverts specStatus back to
"unofficial". Squashing collapses both into a single final-state commit and
silently drops the "base"-status snapshot that the tag requires.

This isn't hypothetical — it already happened once for 2025-1-RC4: PR #206
was squash-merged, which ate the intermediate commit, had to be reverted
(commit fee40e5), and was redone as two individually preserved commits
(7c8f678, 6b3df2a) before the tag would build correctly.