Standards

Network standards are published by the Developer Portal of the Velocity Interoperability Network and numbered in the VIN series. Each standard is issued at a stated version; a system that claims conformance must state the version to which it conforms. Five standards are in force. Two of them, the Interoperability Baseline and the Message Envelope, apply to every system connected to the Network; the remaining three apply only to systems that perform the functions they describe.

The standards were issued together on 6 September 2026 at Version 1.0. Comments on any standard are invited until 4 December 2026 and will be considered at the first review of the standard concerned, in March or June 2027. The rules governing versions, corrections and the notice given before a change are set out under Versioning.

VIN-1 Interoperability Baseline

The minimum set of protocols, encodings and conduct that every system connected to the Network must support.

Version 1.0, 6 September 2026

VIN-2 Identity Federation

How member organisations assert and verify the identity of persons and systems across organisational boundaries.

Version 1.0, 6 September 2026

VIN-3 Incident Reporting Format

The structure and required fields of an incident report submitted to a Network authority.

Version 1.0, 6 September 2026

VIN-4 Registry Data Model

The common model for records held in Network registries, including identifiers, ownership and status.

Version 1.0, 6 September 2026

VIN-5 Message Envelope

The envelope in which all messages between member systems are carried, including addressing, sequencing and signature.

Version 1.0, 6 September 2026

Versions in force. The table below is the authoritative statement of the current version of each standard. It is updated on the day a new version or a correction is issued.

Interfaces that follow each standard. An interface in the API Catalogue follows exactly one standard, and its documentation states which requirements of that standard it exercises. The Interoperability Baseline is not followed by any single interface because it governs the conduct of every connected system rather than an exchange of data.

How a standard is structured. Every standard in the VIN series is set out in the same six parts, so that a developer who has read one knows where to find the requirements in another.

Scope

Which systems the standard applies to and which functions it governs. A system that performs none of the functions in scope need not implement the standard, with the exception of VIN-1 and VIN-5, which apply to every connected system.

Terms

The terms the standard uses, each with the meaning given in the Glossary of this site unless the standard defines it more narrowly.

Requirements

Numbered statements of what a conforming system must, should or may do. Only statements using must are tested by a declaration of conformance; should and may record recommended and permitted practice.

Conformance clause

The requirements a system must meet to declare conformance, and any options among which a declaration must choose.

Interface annex

Where an interface in the API Catalogue follows the standard, an annex names the interface and states which requirements it exercises.

Change record

Every version and correction of the standard, with its date and a summary of what changed.

Interfaces that implement these standards are listed in the API Catalogue and described under APIs. The procedure for declaring conformance is set out under Conformance, and the terms the standards use are defined in the Glossary. Comments on a standard may be sent to contact@developer.gov.vin.