Versioning
Every standard in the VIN series, and every interface in the API Catalogue, carries a version number of the form major.minor. The version number tells a developer whether a change matters to an existing system: a change to the second number adds to a standard without invalidating conforming systems, while a change to the first number alters a requirement and starts the clock on the withdrawal of the earlier version.
The Developer Portal of the Velocity Interoperability Network issues each version on a stated date, records it in the register below and announces it on this site. No standard or interface is changed silently. Where a change affects an existing requirement, the period of notice set out in the table of kinds of change is given before the new version takes effect, and the earlier version remains valid for a defined period afterwards so that member organisations can plan their work.
A declaration of conformance always names a version. It remains valid at that version until the version lapses, whether or not a later version has been issued. The procedure for declaring conformance, and for renewing a declaration after adopting a new version, is set out under Conformance.
Kinds of change. Four kinds of change are recognised. Each has a fixed effect on the version number and a fixed period of notice.
| Kind of change | Effect on version | Meaning | Notice given |
|---|---|---|---|
| Correction | None | Wording is clarified or an error corrected without changing any requirement. Recorded in the change record of the standard. | None |
| Minor revision | Second number raised, e.g. 1.0 to 1.1 | A requirement is added that a conforming system may ignore, or an optional element is introduced. Systems conforming to the earlier version continue to conform. | Three months before issue |
| Major revision | First number raised, e.g. 1.1 to 2.0 | A requirement is changed or removed so that a system conforming to the earlier version may no longer conform. The earlier version remains valid for twelve months after issue. | Six months before issue |
| Withdrawal | Version marked Withdrawn | The standard ceases to apply and no declaration may be made against it. Existing declarations lapse twelve months after withdrawal. | Twelve months before withdrawal |
Register of issued versions. The register lists every version of every standard and interface issued since the Developer Portal was established, and will be added to with each issue. Interface versions below 1.0 denote an Interim interface.
| Standard or interface | Version | Issued | Status | Valid until |
|---|---|---|---|---|
| VIN-1 Interoperability Baseline | 1.0 | 6 September 2026 | Current | Current version |
| VIN-2 Identity Federation | 1.0 | 6 September 2026 | Current | Current version |
| VIN-3 Incident Reporting Format | 1.0 | 6 September 2026 | Current | Current version |
| VIN-4 Registry Data Model | 1.0 | 6 September 2026 | Current | Current version |
| VIN-5 Message Envelope | 1.0 | 6 September 2026 | Current | Current version |
| Registry lookup (API-01) | 0.9 | 6 September 2026 | Interim | Until confirmed at 1.0; follows VIN-4 Registry Data Model |
| Identity assertion (API-02) | 0.9 | 6 September 2026 | Interim | Until confirmed at 1.0; follows VIN-2 Identity Federation |
| Incident submission (API-03) | 0.8 | 6 September 2026 | Interim | Until confirmed at 1.0; follows VIN-3 Incident Reporting Format |
| Notice feed (API-04) | 0.7 | 6 September 2026 | Interim | Until confirmed at 1.0; follows VIN-5 Message Envelope |
Review schedule. Each standard is reviewed on a fixed cycle. The first reviews fall in March and June 2027; thereafter each standard is reviewed annually in the same month. A review may result in no change, in a correction or in a new version.
6 September 2026
Version 1.0 of VIN-1 to VIN-5 issued
All five standards are issued together at Version 1.0. The four available interfaces are listed as Interim at versions between 0.7 and 0.9.
6 September to 4 December 2026
Comment period on Version 1.0
Member organisations may send comments on any standard by email. Comments received in this period are considered at the first review of the standard concerned.
March 2027
First review of VIN-1, VIN-2 and VIN-5
The Interoperability Baseline, Identity Federation and Message Envelope are reviewed in the light of comments and of six months' operation. Any minor revision is announced at the close of the review.
June 2027
First review of VIN-3 and VIN-4
The Incident Reporting Format and Registry Data Model are reviewed. The review considers, among other things, whether the Interim interfaces that follow them are ready to be confirmed.
Forthcoming
Confirmation of interfaces at Version 1.0
Each Interim interface is confirmed at Version 1.0 once its documentation is complete, it has been stable for three months and two member systems have declared conformance to the standard it follows.
Comments on the versioning policy or on any standard may be sent to contact@developer.gov.vin. The current version of every standard is shown on the Standards page and of every interface in the API Catalogue.