DraftDraft for review, not yet a published standard. Registry vehicle/1.0-draft of 2026-10-24, marker vehicle/1.0. How changes are made.

vehicle.specificationId

VINvoice specification · VINvoice-Spezifikation

Marker row. Identifies the vehicle data specification and the major.minor version that the vehicle rows of this line follow, and so makes the line a vehicle line. Analogous to EN 16931 BT-24 (Specification identifier) at line level; it is not a BT-24 value and never appears in BT-24.

Key
vehicle.specificationId
Row name (BT-160)
VINvoice-Spezifikation [vehicle.specificationId]
VINvoice specification [vehicle.specificationId]

The bare key vehicle.specificationId is also accepted.

Tier
Core
Status
draft
Representation term
Id
Value format
^vehicle/[1-9][0-9]*[.](0|[1-9][0-9]*)$, e.g. vehicle/1.0 (no patch number, never a URL)
Grammar
^vehicle/[1-9][0-9]*[.](0|[1-9][0-9]*)$
Unit
none
Code list
none (version token)
Required when
MUST appear exactly once on every vehicle line and SHOULD be the first row; MUST NOT appear on any other line
Statutory feature
No
Repeatable
No, at most one row per line
Anchors
  • EN 16931-1 BT-24 'Specification identifier' (UBL cbc:CustomizationID, CII GuidelineSpecifiedDocumentContextParameter/ID), as an analogy only
  • KoSIT CIUS XRechnung CVD v0.9 BT-160 'cva' as precedent for a machine token in BT-160
Carrier and binding
BG-32: BT-160 'VINvoice-Spezifikation [vehicle.specificationId]', BT-161 'vehicle/1.0'
Values in the test corpus
  • vehicle/1.0
Crosswalk (informative)

EN 16931 BT-24 Specification identifier (analogy only)

informative; names and IRIs of third-party works, CC BY 4.0, sources stated; VDA 4938: reprint with source

Source and changes
registry/keys/specificationId.yaml · Propose a change