Release Notes & Erratas
The authoritative record of changes made after publication. The register is split in two — one side tracks changes to the operational systems participants integrate with, the other tracks corrections to published documentation.
What has changed since publication
Release Notes describe what was deployed to the platform. Erratas describe what was corrected in the published documentation. Use them together to understand where the ecosystem stands.
Release Notes
Changes deployed to the operational systems participants integrate with — the API Hub platform, the Trust Framework, and any supporting infrastructure. Each entry describes what was deployed, when it became effective, and the impact on TPPs and LFIs.
Erratas
Corrections to published documentation — the TPP Standards, LFI Integration Guide, and OpenAPI specifications. Each entry records what was corrected, why the change was required, and the effective date.
How these registers are governed
Both registers are bound by the policies that control how published content evolves and how versions are promoted.
Changes to Published Documentation
How published content may change after release — what requires an Errata, what does not, and how corrections are communicated.
Version Management
How versions are numbered, when errata releases are cut, and how the relationship between Standards, API Hub, and Ozone Connect versions is maintained.