Chain agreements: feedback, correction, chunking, transport, releases
Release policy and version management: annual cycle, three active releases and afdDefinitionVersion
SIVI publishes a pre-release at the end of June and a final release at the end of September every year. Three annual releases are active at the same time. Every message carries in commonFunctional the afdDefinitionVersion of the schema it was built with (001.04 for Release 2026, 001.05 for Release 2027), so the receiver picks the right schema.
Steps
- JuneSIVIPre-release with release notes on GitHub; chains assess impact.
- SeptemberSIVIFinal release; manual PDF on sivi.org.
- MigrationChain partnersAgree per link when to move to the new afdDefinitionVersion; support two versions temporarily.
Rules and consistency checks
- Change requests run via GitHub issues in the format prescribed by the wiki (sample JSON, UML, consistency checks).
- Changes are only made through the formal process; derived versions require approval from SIVI or the Pensioenfederatie.
Source: Handleiding paragraaf 2.8 en 2.9.2; GitHub README