ISO/IEC TS 7367-2:2026

Personal identification — mdoc schemas — Part 2: Mobile vehicle certificate

This document provides the logical data structure of a mobile Vehicle Certificate (mVC) in conformity with ISO/IEC TS 23220-2 that serves as a confirmation of vehicle register data and confirmation of conformity with issuance requirements. Other documents related to vehicle administration, such as a document that proves ownership of a vehicle and is designed to be used for ownership transfer, are out of scope of this document.

Identification personnelle — Schémas mdoc — Partie 2: Certificat mobile pour les véhicules

General Information

• Status: Published
• Publication Date: 12-May-2026
• ICS: 35.240.15 - Identification cards. Chip cards. Biometrics
• Technical Committee: ISO/IEC JTC 1/SC 17 - Cards and security devices for personal identification
• Drafting Committee: ISO/IEC JTC 1/SC 17/WG 10 - Motor vehicle driver licence and related documents
• Current Stage: 6060 - International Standard published
• Start Date: 13-May-2026
• Due Date: 07-Oct-2028
• Completion Date: 13-May-2026

Overview

ISO/IEC TS 7367-2:2026 is an international technical specification that defines the logical data structure for the mobile Vehicle Certificate (mVC) within the broader ISO/IEC mdoc schemas series. Managed by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC), this standard establishes a unified approach for issuing, storing, and verifying vehicle certification documents in digital, mobile formats. The mVC is designed to confirm both a vehicle's registration data, as recorded by an issuing authority, and conformity with all relevant issuance requirements such as taxes, inspections, and insurance coverage. The specification is in alignment with ISO/IEC TS 23220-2, ensuring interoperability and conformance within digital identity and vehicle administration ecosystems.

Key Topics

• Logical Data Structure: Defines mandatory, optional, and conditional data elements for mVCs, including information on vehicle registration, users, owners, technical specifications, and issuing authority.
• Data Model & Namespace: Uses unique docTypes and namespaces to ensure unambiguous identification of mVC data elements.
• Interoperability & Compliance: mVCs follow established international protocols for encoding and verification, leveraging standards such as ISO 3166 (country codes), ISO 3779 (VIN), and RFC standards for data encoding and timestamps.
• Authorization & Legal Recognition: mVCs confirm the holder’s right to operate a vehicle and compliance with legal and regulatory requirements.
• Selective Disclosure: Supports the secure sharing of relevant information (such as user or owner details) with authorities or verifiers as needed.
• Roles & Responsibilities: Clarifies the distinction between the vehicle’s user (registered holder), owner (title holder), presenter (person showing the certificate), and the issuing authority.

Applications

The mobile Vehicle Certificate (mVC) standard is highly applicable in digital transformation initiatives for vehicle registration and administration. Its key practical uses include:

• Roadside Verification: Enables law enforcement and regulatory authorities to quickly confirm vehicle registration and compliance status through mobile or digital readers.
• Regulatory Compliance: Facilitates automated checking of taxes, insurance, and inspection conformity, streamlining both enforcement and re-registration processes.
• International Operations: Supports the digital presentation and cross-border acceptance of vehicle certificates, enhancing efficiency for vehicles operating in multiple jurisdictions.
• Environmental Controls: Assists with access control for environmental zones, restricting entry to vehicles that meet specific criteria.
• Vehicle Life-Cycle Management: Provides a trusted digital record for tracking the status and updates of vehicle registration over time, aiding authorities in authentic data management.
• Digital Identity Integration: The mVC standard complements mobile identity solutions and eID-Wallets, allowing convenient carrying and presentation of proof-of-registration on smartphones and devices.

Related Standards

• ISO/IEC TS 23220-2: Data objects and encoding rules for generic eID systems; foundational to mVC data structuring and validation.
• ISO 3166-1, ISO 3166-2: Country and subdivision codes for accurate, standardized geographic identifiers.
• ISO 3779: Structure and content for Vehicle Identification Numbers (VIN), crucial for unique vehicle identification.
• ISO/IEC TS 7367-series: Broader specifications for mobile documents (mdocs) and personal identification schemas.
• RFC 3339 & RFC 8943: Standards for date, time, and binary object representation, ensuring consistency and reliability in timestamps.
• UN Convention on Road Traffic (1968): Provides the international legal framework for vehicle certification and road use compliance.

---

ISO/IEC TS 7367-2:2026 streamlines and secures the digital management of vehicle registration data worldwide, ensuring vehicles’ digital certificates are trustworthy, interoperable, and future-ready for digital public services and cross-border mobility. By adopting this standard, authorities, organizations, and regulatory bodies can improve compliance, operational efficiency, and user convenience in vehicle administration.

Standards Content (Sample)

Technical
Specification
ISO/IEC TS 7367-2
First edition
Personal identification — mdoc
2026-05
schemas —
Part 2:
Mobile vehicle certificate
Identification personnelle — Schémas mdoc —
Partie 2: Certificat mobile pour les véhicules
Reference number
© ISO/IEC 2026
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2026 – All rights reserved
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviations . 3
5 General principles . 3
6 mVC data model . 4
6.1 mVC document type and namespace .4
6.2 mVC data elements .4
6.2.1 Overview .4
6.2.2 Basic data elements of namespace “org.iso.7367.2.1” .5
6.2.3 User and owner data elements of namespace “org.iso.7367.2.1” .7
6.2.4 Vehicle information data elements of namespace “org.iso.7367.2.1” .11
6.2.5 Domestic data elements . 20
6.2.6 Country codes . 20
Annex A (informative) Examples of use cases .21
Annex B (informative) Generic vehicle registration life-cycle .25
Annex C (normative) Certificate and CRL profiles .27
Bibliography .30

© ISO/IEC 2026 – All rights reserved
iii
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical activity.
ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations,
governmental and non-governmental, in liaison with ISO and IEC, also take part in the work.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/
IEC Directives, Part 2 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www.iso.org/iso/foreword.html.
In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 17, Cards and security devices for personal identification.
A list of all parts in the ISO/IEC 7367 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.

© ISO/IEC 2026 – All rights reserved
iv
Introduction
This document is part of the ISO/IEC 7367 series which specifies mdoc schemas. An mdoc can be held
on a mobile device and can be verified by a verifier using a reader device with mechanisms specified in
ISO/IEC 18013-5, ISO/IEC TS 18013-7 and ISO/IEC TS 23220-4.
This document specifies the data structure of a mobile Vehicle Certificate.
An mVC serves two core functions:
a) Confirmation of vehicle register data
It serves as confirmation of information recorded in the issuing authority’s vehicle register for a specific
vehicle. This can include details about the vehicle’s user or holder, the owner or titleholder, and unique
identifiers such as configuration and technical specifications.
b) Confirmation of conformity with issuance requirements
It confirms that the vehicle meets any conditions set by the issuing authority for the issuance of an mVC.
Typical requirements can include:
1) payment of vehicle-related taxes;
2) fulfilment of annual roadworthiness inspections;
3) proof of valid insurance coverage.
In addition to its role as a confirmation document, an mVC can support enforcement of vehicle-related
regulations, particularly in roadside environments, by providing data relevant to the authorization to
operate a vehicle. Examples include:
— restricting road access to vehicles with specific attributes;
— verifying the identity of the authorized vehicle user.

© ISO/IEC 2026 – All rights reserved
v
Technical Specification ISO/IEC TS 7367-2:2026(en)
Personal identification — mdoc schemas —
Part 2:
Mobile vehicle certificate
1 Scope
This document provides the logical data structure of a mobile Vehicle Certificate (mVC) in conformity with
ISO/IEC TS 23220-2 that serves as a confirmation of vehicle register data and confirmation of conformity
with issuance requirements.
Other documents related to vehicle administration, such as a document that proves ownership of a vehicle
and is designed to be used for ownership transfer, are out of scope of this document.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country code
ISO 3166-2, Codes for the representation of names of countries and their subdivisions — Part 2: Country
subdivision code
ISO 3779, Road vehicles — Vehicle identification number (VIN) — Content and structure
ISO/IEC TS 23220-2, Cards and security devices for personal identification — Building blocks for identity
management via mobile devices — Part 2: Data objects and encoding rules for generic eID systems
RFC 3339, Date and Time on the Internet: Timestamps
RFC 8943, Concise Binary Object Representation (CBOR) Tags for Date
UNITED NATIONS. Convention on Road Traffic. Consolidated version including amendments entered into
force on 28 March 2006. Vienna, 8 November 1968. United Nations Treaty Series, vol. 1091, no. 15810.
[online]. Available at: https:// unece .org/ fileadmin/ DAM/ trans/ conventn/ Conv _road _traffic _EN .pdf
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/

© ISO/IEC 2026 – All rights reserved
3.1
mdoc
mobile document
set of attributes and credentials issued by one or more issuers into an mdoc app and managed by an mdoc
app, in accordance with ISO/IEC 23220-1
Note 1 to entry: A mobile document is considered a digital document. An mdoc app managing more than one mobile
documents is also considered an eID-Wallet.
Note 2 to entry: In ISO/IEC 18013-5, mdoc represents mdoc app or mobile eID.
EXAMPLE Mobile documents include eID documents and licences or certificates that give the holder permission.
[SOURCE: ISO/IEC 23220-1:2023, 3.22, modified — preferred term changed to mdoc, definition changed to
include accordance with source document, Note 2 to entry " document" changed to "eID".]
3.2
issuing country
country which issued the mobile Vehicle Certificate (3.4) or within which the issuing authority (3.3) is located
[SOURCE: ISO/IEC 18013-1:2018, 3.12, modified — "DL" replaced with "mobile Vehicle Certificate", "licensing
authority" replaced by "issuing authority", “according to Annex F” removed.]
3.3
issuing authority
name of the authorized organization that issues mobile Vehicle Certificate (3.4)
3.4
mobile Vehicle Certificate
mobile document which confirms the information recorded in the vehicle register of the issuing authority
in respect of a vehicle (3.5) and which confirms the conformity with the requirements for issuance of the
document
Note 1 to entry: The mobile Vehicle Certificates is an mdoc (3.1) with document type and namespace specified in
6.1 and data elements specified in 6.2. An mVC can be verified with mdoc readers according to ISO/IEC TS 23220-4
and mDL readers according to ISO/IEC 18013-5 and ISO/IEC TS 18013-7, where such readers are provided with the
definition of an mVC
Note 2 to entry: The certificate includes information about the vehicle and the user (3.6) or the owner (3.7), or both, of
the vehicle.
Note 3 to entry: The conformity requirements for issuance of the mVC can include (periodical) requirements that can
be applicable to the vehicle, e.g. annual registration.
Note 4 to entry: The certificate, known as the registration certificate in the UNITED NATIONS. Convention on Road
Traffic 1968, is also known as vehicle licence, vehicle registration certificate, or in the EU as Part I of the registration
certificate.
3.5
vehicle
wheeled or tracked device designed or adapted mainly to be used on land, motorised or to be towed by a
motorised device on wheels
EXAMPLE Motor vehicles, motor cycles, trailer or semi-trailer are examples of vehicles.

© ISO/IEC 2026 – All rights reserved
3.6
user
natural or legal person who has been granted the right of use and benefit of the vehicle by the owner of
the vehicle and who is recorded as user of the vehicle (3.5) in the system of the authority issuing the mobile
Vehicle Certificate (3.4)
Note 1 to entry: The user is responsible and liable for the vehicle e.g. in terms of fines, insurance, taxes or technical
state of the vehicle. Being a user of a vehicle does not imply ownership of the vehicle. A natural person can be authorized
by the user to use the vehicle by sharing the mobile Vehicle Certificate with such person. The user can also be referred
to as the registered holder of the vehicle.
3.7
owner
natural or legal person that has the right to sell or dispose of the vehicle (3.5) and who is recorded as the
owner of the vehicle (3.5) in the system of the authority issuing the mobile Vehicle Certificate (3.4) according
to the rules of the issuing authority
Note 1 to entry: The owner can also be referred to as the title holder or lien holder of the vehicle.
3.8
presenter
natural person who is presenting the mobile Vehicle Certificate (3.4) to other persons, authorities or entities
Note 1 to entry: The presenter doesn’t have to be the same person as the user or owner of the vehicle in the vehicle
register.
4 Symbols and abbreviations
For the purposes of this document, the following abbreviations apply
CBOR concise binary object representation
CDDL concise data definition language
IA issuing authority
mdoc mobile document
mVC mobile Vehicle Certificate
MSO Mobile Security Object
5 General principles
This document focuses on the authorization to operate the vehicle. Usually (depending on national
legislation) the document which conveys the authorization to operate should be kept in the vehicle while
the vehicle is being driven. The mVC is a confirmation of information recorded by the issuing authority and
a confirmation of the conformity with the requirements for issuance of the mVC. These requirements can
include (periodical) requirements that can be applicable to the vehicle, e.g. annual registration.
The certificate can contain information about:
— the registration;
— the user(s), also known as the holder of the vehicle;
— the owner(s), also known as the title holder of the vehicle;
— unique identification, configuration and technical capacity of the vehicle;
— annual legal and/or technical conformity of the vehicle for use on a public road.

© ISO/IEC 2026 – All rights reserved
mVC’s are used for various purposes as given in Annex A, such as:
— to verify that the vehicle is registered so it can be used in public areas;
— to verify that the presenter has permission to drive the specific vehicle or the vehicle-combination (e.g.
car and trailer) according to the presenter’s driving licence;
— to verify that the presenter is allowed to enter an environmental zone with the vehicle;
— authentic information for (re-)registration in a second country or interstate transfers;
— to determine who is the recorded liable person of the vehicle; or
— presenting the certificate can be seen as a confirmation that the presenter is allowed to use the vehicle
from the user/owner.
The definition of data elements is based on the UN Convention on Road Traffic and an example of a generic
vehicle registration life-cycle as given in Annex B. Both require a number of items on the vehicle certificate.
The definition of detailed technical data of the vehicle is based on further documents, such as electronic
[9]
certificates of conformity (CoC) of the EU .
6 mVC data model
6.1 mVC document type and namespace
docType and namespace are used to encapsulate the document type and the space in which the data elements
are defined according to ISO/IEC TS 23220-2. Certificate and CRL profiles shall be used as defined in Annex C.
The docType for an mVC document shall be “org.iso.7367.2.1.mVC”. The number “1” in the document type
might be increased in future versions of this document.
The namespace for mVC data elements defined in 6.2 shall be “org.iso.7367.2.1”. The “2” refers to the part
within the ISO/IEC 7367 series. The number “1” in the namespace can be increased in future versions of this
document. Within this namespace, only data elements defined in 6.2.2, 6.2.3 and 6.2.4 are used.
To accommodate domestic data, an issuing authority can additionally define its own namespace as described
in 6.2.5 and 6.2.6.
NOTE 1 To prevent collisions, the namespace field follows the following general format: [Reverse Domain].[Domain
Specific Extension].
6.2 mVC data elements
6.2.1 Overview
The data elements described in 6.2 belong to the namespace defined in 6.1.
— The "Identifier" column is used for DataElementIdentifier in the mdoc request in accordance with
ISO/IEC TS 23220-4.
— The "Presence" column indicates whether the presence of the element on an mVC is mandatory (M),
optional (O) or conditional (C). If an element is conditional the respective condition is given.
— The “Encoding format” column indicates how the data elements shall be encoded. “tstr”, “uint”, “bstr”,
“bool” and “tdate” are CDDL representation types as defined in RFC 8610. “full-date” shall be implemented
according to the additional information tag 1004 for full-date elements as defined in RFC 8943.
— The following requirements shall apply to dates in mVC data elements unless otherwise indicated and
when applicable: Dates shall not use fraction of seconds. No local offset from UTC shall be used, as
indicated by setting the time-offset defined in RFC 3339 to “Z”.

© ISO/IEC 2026 – All rights reserved
— The data elements provided in 6.2.2, 6.2.3 and 6.2.4 are included in the device response in accordance
with ISO/IEC TS 23220-4.
6.2.2 Basic data elements of namespace “org.iso.7367.2.1”
The mVC basic data elements shall be as defined in Table 1 and belong to the namespace given in 6.1. The mVC
shall include sufficient fields to allow unique identification of the vehicle. In some regions, the mandatory
data elements given in Table 1 and Table 7 can be insufficient to support a roadside process (including
when network connectivity is not available) to confirm the match between a vehicle and an mVC. It is the
responsibility of an appropriate authoritative body to identify any optional or conditional data elements
in either Table 1 or in Table 7, or both, that must be made mandatory in that region for this purpose, and to
publish this.
Table 1 — org.iso.7367.2.1 data elements
Encoding for-
Identifier Meaning Definition Presence
mat
The date of initial issuing of an mVC, or reissuing
an mVC because of change of data on the certif-
Date of issuing certif-
issue_date M full-date
icate (e.g. ownership or technical vehicle data).
icate
SOURCE: ISO/IEC TS 23220-2
Date given by the issuing authority, when the
mVC expires.
expiry_date Expiry date O full-date
example: UN element H
SOURCE: ISO/IEC TS 23220-2
Name of the issuing authority of the mVC.
issuing_au-
The issuing authority also refers to the com-
thority_uni- Issuing authority M tstr
petent authority.
code
SOURCE: ISO/IEC TS 23220-2
Name of the issuing authority of the mVC in
issuing_au-
a
latin1 characters.
Issuing authority M tstr
thority_latin1
SOURCE: ISO/IEC TS 23220-2
Alpha-2 country code, as defined in ISO 3166-1,
issuing_coun-
of the issuing country.
Issuing country M tstr
try
SOURCE: ISO/IEC TS 23220-2
Subdivision code, as defined in ISO 3166-2 of
the subdivision which issued the mVC or within
which the issuing authority is located. The first
issuing_subdi-
Issuing subdivision O tstr
part of the code shall be the same as the value
vision
for issuing_country.
SOURCE: ISO/IEC TS 23220-2
The number assigned or calculated by the
document_
issuing authority of the issued mVC.
Document number O tstr
number
SOURCE: ISO/IEC TS 23220-2
The distinguishing sign of the issuing country
used on (plates of) vehicles in international
traffic (see article 45 of UN Convention on Road
Traffic, 1968 and Annex 4 of UN Convention on
Road Traffic, 1949).
un_distin- UN distinguishing
M tstr
If no applicable distinguishing sign is available
guishing_sign sign
in the UN Convention on Road Traffic, an IA can
use an empty identifier or another identifier by
which it is internationally recognized. In this
case the IA should ensure there is no collision
with other IA’s
© ISO/IEC 2026 – All rights reserved
TTabablele 1 1 ((ccoonnttiinnueuedd))
Encoding for-
Identifier Meaning Definition Presence
mat
Number issued by the authority, usual-
ly composed in the manner indicated in
Annex 2 to UN Convention on Road Traffic,
registration_
1968, also named as the vehicle’s plate num-
Registration Number M tstr
number
ber.
example: Element A (see article 35 of
UN Convention on Road Traffic).
Type of registration number when using the
registration_ Registration Number same registration number for different class-
O tstr
number_type Type es/types of vehicles (e.g. registered farming
vehicle, motorised scooter, heavy vehicles).
Unique administrative number under which
register_num-
Register Number a vehicle is recorded in the system of the O tstr
ber
issuer.
Date and optionally time when an authorized
body records the vehicle's user(s) or own-
date_of_regis-
er(s) (date of change ownership)
Date of Registration M tdate or full-date
tration
NOTE The Issuing Authority can act as
authorized body.
Year of manufacturing of the vehicle.
year_of_manu-
Year of manufacturing O uint
facturing
EXAMPLE: UN element B
Date and optionally time of the administra-
tive authorization for a vehicle first to enter
date_of_first_ Date of first registra-
into service wherever in the world.
O tdate or full-date
registration tion
EXAMPLE: Element B (see article 35 of
UN Convention on Road Traffic).
The number assigned or calculated by the issu-
document_ ing authority of the issued technical inspection
Document number of
number_ report related to the approval and expiry date
technical inspection O tstr
techn_insp_re- of the technical inspection as given in data
report
port elements approval_date_technical_inspection
and expiry_date_technical_inspection.
approval_date_
Date of approval tech- Date and optionally time of the most recent
technical_in- O tdate or full-date
nical inspection registered successful technical inspection.
spection
expiry_date_ Date of expiration of
Date and optionally time by which a vehicle
technical_in- the approval for the O tdate or full-date
must undergo its (next) technical inspection.
spection technical inspection
The serial number of the chassis allocated to
chassis_num- Chassis number infor-
the vehicle by the maker and/or registering M See 6.2.4.2
ber_info mation
authority.
One or more users of the vehicle as recorded
by the issuing authority.
Recorded user(s) of EXAMPLE: Element C (see article 35 of
users C See 6.2.3.2
the vehicle UN Convention on Road Traffic)
The mVC shall always include at least one
user or one vehicle owner
One or more owners of the vehicle as record-
ed by the issuing authority.
Recorded owner(s) of
owners C See 6.2.3.3
the vehicle
The mVC shall always include at least one
user or one vehicle owner.
basic_vehi- Basic vehicle informa-
The basic information of the vehicle. M See 6.2.4.3
cle_info tion
mass_info Mass information The mass information of a vehicle. O See 6.2.4.4

© ISO/IEC 2026 – All rights reserved
TTabablele 1 1 ((ccoonnttiinnueuedd))
Encoding for-
Identifier Meaning Definition Presence
mat
The towing vehicle’s maximum allowable
towed mass for both unbraked and braked
towed_trail- Towed trailer mass
O See 6.2.4.5
trailers.
er_mass_info information
Only present if applicable.
engine_info Engine information The information of the engine of a vehicle. O See 6.2.4.6
The information of the number of seating
seating_info Seating information O See 6.2.4.7
and standing places in a vehicle
dimensions_ Dimensions informa- The information of the dimensions of a
O See 6.2.4.8
info tion vehicle.
Key
Presence:
M mandatory
O optional
C conditional
a
Latin1 is defined in ISO/IEC 8859-1 as Latin alphabet No. 1
6.2.3 User and owner data elements of namespace “org.iso.7367.2.1”
6.2.3.1 Introduction
A single data element is defined for recorded users, and a single data element is defined for recorded owners.
This allows an mVC reader to request, and the mVC holder to respond with (assuming their presence in the
request), either or both of these elements. The data element for users allows for multiple users, and the data
element for owners allows for multiple owners. All users are included in the users data element when shared,
and all owners are included in the owners data element when shared. Where multiple users or owners exist,
the release of individual users is not supported.
The mVC shall include at least one user or owner.
6.2.3.2 User information
The user information contains information describing the name and address of the recorded user(s) of the
vehicle. There can be more than one user. The data elements in the user information shall be as defined in
Table 2.
The presence of the data element naturalperson in the structure RecordedEntity indicates a natural person.
The data elements for a natural person shall be as defined in Table 3 and Table 5.
The presence of the data element organization in the structure RecordedEntity indicates an organization
or body of persons. The data elements for an organization shall be as defined in Table 4.
The user structure shall be encoded as CBOR for device retrieval and shall be formatted as following CDDL
structure.
Users = [+RecordedEntity]     ; Example: UN element C

RecordedEntity = {
? natural_person: NaturalPerson,                ; according to Table 2
? organization: Organization                 ; according to Table 2
}
NaturalPerson = {
"full_address" : Address,                    ; according to Table 3
"family_name" : tstr,                     ; according to Table 3

© ISO/IEC 2026 – All rights reserved
? "family_name_latin1" : tstr,                ; according to Table 3
"given_name" : tstr,                     ; according to Table 3
? "given_name_latin1" : tstr,                 ; according to Table 3
? "supplemental_person_data" : {+ tstr => tstr}        ; according to Table 3
}
Organization = {
"full_address" : Address
"organization_name" : tstr,                  ; according to Table 4
? "organization_name_latin1" : tstr,             ; according to Table 4
? "supplemental_organization_data" : {+ tstr => tstr}        ; according to Table 4
}
Address = {
"address" : tstr,                       ; according to Table 5
? "address_latin1" : tstr,                  ; according to Table 5
"city" : tstr,                        ; according to Table 5
? "city_latin1" : tstr,                    ; according to Table 5
? "state" : tstr,                       ; according to Table 5
? "state_latin1" : tstr,                   ; according to Table 5
? "postal_code" : tstr,                    ; according to Table 5
"country" : tstr,                       ; according to Table 5
? "supplemental_location_data" : {+ tstr => tstr}       ; according to Table 5
}
Table 2 — RecordedEntity key details
Encoding
Identifier Description Presence
format
Personal and address data of the natural person recorded as user
or owner of the vehicle.
See
Optional in case of an organization or body of persons is record-
naturalPerson C
Table 3
ed as user or owner of the vehicle; the element then contains the
family name of the representative or proxy of the organization or
body of persons.
Personal and address data of the organization recorded as user or
See
organization owner of the vehicle. Absent in case of the recorded user or owner C
Table 4
is a natural person.
Key
Presence:
M mandatory
O optional
C conditional
© ISO/IEC 2026 – All rights reserved
Table 3 — NaturalPerson key details
Encoding
Identifier Description Presence
format
See
Full address of the person, the organization or body of persons
full_address M
recorded as user or owner of the vehicle.
Table 5
Last name, surname, or primary identifier, of the user or owner
mandatory in case of a natural person, optional in case of an
organization or body of persons; the element then contains the
family_name M tstr
family name of the representative or proxy of the organization or
body of persons.
SOURCE: ISO/IEC TS 23220-2
Last name, surname, or primary identifier, of the user or owner.
In case of an organization or body of persons; the family name of
the representative or proxy of the organization or body of per-
family_name_latin1 O tstr
a
sons. Latin1 characters.
SOURCE: ISO/IEC TS 23220-2
First name(s), other name(s), or secondary identifier, of
the user or owner.
Mandatory in case of a natural person, optional in case of an organi-
given_name M tstr
zation or body of persons; the element then contains the given name
of the representative or proxy of the organization or body of persons.
SOURCE: ISO/IEC TS 23220-2
First name(s), other name(s), or secondary identifier, of the user
or owner. In case of an organization or body of persons; the given
name of the representative or proxy of the organization or body
given_name_latin1 O tstr
a
of persons. Latin1 characters.
SOURCE: ISO/IEC TS 23220-2
supplemental_per- Any other relevant information of the person. Only tstr is allowed,
O
son_data for another encoding format use a domestic namespace.
Key
Presence:
M mandatory
O optional
C conditional
a
Latin1 is defined in ISO/IEC 8859-1 as Latin alphabet No. 1
NOTE Full address is not defined in current edition of ISO/IEC TS 23220-2.

© ISO/IEC 2026 – All rights reserved
Table 4 — Organization key details
Encoding
Identifier Description Presence
format
See
Full address of the person, the organization or body of persons
full_address M
recorded as user or owner of the vehicle.
Table 5
The name of the entity like an organization or body of persons.
organization_name M tstr
SOURCE: ISO/IEC TS 23220-2
The name of the entity like an organization or body of persons.
organization_name_
a
Latin1 characters.
O tstr
latin1
SOURCE: ISO/IEC TS 23220-2
supplemental_organi- Any other relevant information of the organization. Only tstr is
O
zation_data allowed, for another encoding format use a domestic namespace.
Key
Presence:
M mandatory
O optional
C conditional
a
Latin1 is defined in ISO/IEC 8859-1 as Latin alphabet No. 1
Table 5 — Address key details
Encoding
Identifier Description Presence
format
Address of the organization or body of persons recorded as user or
owner of the vehicle (street/house number, municipality etc.).
address M tstr
SOURCE: ISO/IEC TS 23220-2
Address of the organization or body of persons recorded as user or
owner of the vehicle (street/house number, municipality etc.).
address_latin1 O tstr
a
Latin1 characters
SOURCE: ISO/IEC TS 23220-2
The place of the organization or body of persons recorded as user or
owner of the vehicle.
city M tstr
SOURCE: ISO/IEC TS 23220-2
The place of the organization or body of persons recorded as user or
owner of the vehicle.
city_latin1 O tstr
a
Latin1 characters.
SOURCE: ISO/IEC TS 23220-2
The state of the organization or body of persons recorded as user or
owner of the vehicle.
state O tstr
SOURCE: ISO/IEC TS 23220-2
The state of the organization or body of persons recorded as user or
owner of the vehicle.
state_latin1 O tstr
a
Latin1 characters
SOURCE: ISO/IEC TS 23220-2
The postal code of the organization or body of persons recorded as
user or owner of the vehicle.
postal_code O tstr
SOURCE: ISO/IEC TS 23220-2
© ISO/IEC 2026 – All rights reserved
TTabablele 5 5 ((ccoonnttiinnueuedd))
Encoding
Identifier Description Presence
format
The country of the organization or body of persons recorded as user
or owner of the vehicle as a two letter country code (alpha-2 code)
country M tstr
defined in ISO 3166-1.
SOURCE: ISO/IEC TS 23220-2
Any other relevant information because of the address. Any other
relevant information of the person. Only tstr is allowed, for another
supplemental_lo-
O
encoding format use a domestic namespace.
cation_data
SOURCE: ISO/IEC TS 23220-2
Key
Presence:
M mandatory
O optional
C conditional
a
Latin1 is defined in ISO/IEC 8859-1 as Latin alphabet No. 1
6.2.3.3 Owner information
The owner information contains information describing the name and address of the recorded owner(s)
of the vehicle. There can be more than one owner. The structure and the definition of the elements of the
RecordedEntity element can be found in paragraph 6.2.3.2 User information.
The Owner structure shall be encoded as CBOR for device retrieval and shall be formatted as follows:

Owners = [+RecordedEntity] ; Example: UN element C, defined in 6.2.3.2

6.2.4 Vehicle information data elements of namespace “org.iso.7367.2.1”
6.2.4.1 Introduction
The vehicle info elements give the possibility for selective disclosure of basic vehicle info and extended
vehicle info. The basic vehicle data element is mandatory. The mass_info, towed_trailer_mass_info, the
engine_info and the seating_info data elements are optional.
6.2.4.2 Chassisnumber information
The chassisnumber information contains information of the serial number of the chassis allocated by the
manufacturer or the registering authority, or both. The data elements in the chassisnumber information
shall be as defined in Table 6.
The ChassisNumberInfo structure shall be encoded as CBOR for device retrieval and shall be formatted as
following CDDL structure:
ChassisNumberInfo = {
? "vehicle_identification_number" : tstr,   ; according to Table 6
? "vehicle_register_number" : tstr      ; according to Table 6
}
© ISO/IEC 2026 – All rights reserved
Table 6 — chassisnumber information key details
Encoding
Identifier Description Presence
format
The serial number of the chassis or as the maker’s production
or serial number. The Vehicle Identification Number is defined
by the vehicle manufacturer. The data element is mandatory if
vehicle_identification_
C tstr
the vehicle_register_number is not present.
number
EXAMPLE: element E (see article 35 of UNITED NATIONS. Con-
vention on Road Traffic)
A unique domestic identifier conformant to ISO 3779 allocated
to the vehicle by the registering authority upon system intro-
duction (due to vehicles with for example a redundant chassis
number or a chassis number which is not conformant with ISO
vehicle_register_number C tstr
3779)
The data element is mandatory if the vehicle_identification_
number is not present.
Key
Presence:
M mandatory
O optional
C conditional
6.2.4.3 Basic vehicle information
The basic vehicle information contains information describing the basic data elements of a vehicle. The data
elements in the basic vehicle information shall be as defined in Table 7.
The BasicVehicleInfo structure shall be encoded as CBOR for device retrieval and shall be formatted as
following CDDL structure:
BasicVehicleInfo = {
? "vehicle_category_code" : tstr,      ; according to Table 7
? "vehicle_category_national" : tstr,    ; according to Table 7
? "approval_number" : tstr,         ; according to Table 7
? "type" : tstr,               ; according to Table 7
? "variant" : tstr,             ; according to Table 7
? "version" : tstr,             ; according to Table 7
"make" : tstr,               ; according to Table 7
? "commercial_name" : tstr,         ; according to Table 7
? "colours" : [+ colour],
? "automation_level" : uint,         ; according to Table 7
? "status_vehicle" : tstr          ; according to Table 7
}
colour = uint                ; according to Table 13

© ISO/IEC 2026 – All rights reserved
Table 7 — Basic vehicle information key details
Encoding
Identifier Description Presence
format
Vehicle category code as defined in the Consolidated UNECE
vehicle_category_code O tstr
Resolution on the Construction of Vehicles R.E.3, Revision 6 .
National vehicle category.
vehicle_category_na-
O tstr
tional
Vehicle category when vehicle category code is not available.
The number of the approval of the last stage of the vehicle
approval_number O tstr
mostly during homologation.
Brand of the vehicle.
A value set to “-” indicates that there is no brand available.
make M tstr
EXAMPLE: Element D (see article 35 of UN Convention on Road
Traffic).
type The type of the vehicle as presented by the manufacturer. O tstr
The variant of the type, only present in combination with the
variant O tstr
approval number. Only present in combination with type.
The version of the type and variant, only present in combina-
version O tstr
tion with the variant.
commercial_name Commercial name of the vehicle. O tstr
colours Primary colour(s) as identifier(s) of the vehicle, see 6.2.4.9. O
Level of automation of the vehicle referring to industry-stand-
ard scale from zero to five developed by the Society of Automo-
automation_level O uint
tive Engineers (SAE).
The value shall be one of the following: 0, 1, 2, 3, 4, 5.
Status of the vehicle, e.g. stolen, written off vehicle (WOVR), O tstr
status_vehicle
impounded.
Key
Presence:
M mandatory
O optional
C conditional
6.2.4.4 Mass information
The mass information contains information describing the mass data elements of a vehicle in kilograms. The
data elements in the mass information shall be as defined in Table 8. The structure is absent when none of
the data elements is applicable.
The mass info structure shall be encoded as CBOR for device retrieval and shall be formatted as following
CDDL structure:
MassInfo = {
? "techn_perm_max_laden_mass" : uint,       ; according to Table 8
? "vehicle_max_mass" : uint,            ; according to Table 8
? "mass_in_running_order" : uint,          ; according to Table 8
? "mass_in_running_order_variable_min" : uint,   ; according to Table 8
? "mass_in_running_order_variable_max" : uint,   ; according to Table 8
}
© ISO/IEC 2026 – All rights reserved
Table 8 — Mass information key details
Encoding
Identifier Description Presence
format
techn_perm_max_laden_mass Technical permissible maximum laden mass in kg. O uint
The legally maximum permissible laden mass of the
vehicle in service in kg.
vehicle_max_mass O uint
EXAMPLE: element F (see article 35 of UN Convention on
Road Traffic)
The mass of the vehicle in service in kg.
mass_in_running_order O uint
EXAMPLE: element G (see article 35 of UN Convention on
Road Traffic)
The variable minimum mass of the vehicle in service in
kg.
mass_in_running_order_varia-
O uint
ble_min
EXAMPLE: element G (see article 35 of UN Convention on
Road Traffic)
The variable maximum mass of the vehicle in service in
kg.
mass_in_running_order_varia-
O uint
ble_max
EXAMPLE: element G (see article 35 of UN Convention on
Road Traffic)
Key
Presence:
M mandatory
O optional
C conditional
a
The mdoc reader can convert to the local unit of measurement.
6.2.4.5 Towed trailer mass information
The towed trailer mass information contains information about the towing vehicle’s maximum allowable
towed mass for both unbraked and braked trailers to be coupled in kilograms. The data elements in the
trailer mass information shall be as defined in Table 9.
The structure is absent when none of the data elements is applicable
The towed trailer mass information structure shall be encoded as CBOR for device retrieval and shall be
formatted as following CDDL structure:

TowedTrailerMasses = [+ TowedTrailerData]

TowedTrailerData = {
? "tech_perm_max_tow_mass" : uint,               ; according to Table 9
? "technically_permissible_maximum_combination_mass" : uint,   ; according to Table 9
? "braked_type_trail_code" : uint,                ; according to Table 9
? "type_trail_code" : uint,                   ; according to Table 9
}
© ISO/IEC 2026 – All rights reserved
Table 9 — Towed trailer mass information key details
Encoding
Identifier Description Presence
format
The technically permissible maximum towable mass
of a trailer to be coupled in kg.
tech_perm_max_tow_mass C uint
mandatory in case of technically_permissible_maxi-
mum_combination_mass is absent.
The maximum permissible laden mass of the whole
vehicle combination in kg.
technically_permissible_maxi-
C uint
mum_combination_mass
Mandatory in case of tech_perm_max_tow_mass is
absent.
Type of braking of the trailer code added with the
national description (e.g. braked and unbraked).
Values:
BRK = Braked
CSB = Continuous or semi-continuous braked
INB = Inertia braked
braked_type_trail_code O tstr
IPB = Independently braked
PNH = Hydraulic pneumatic braked
UNB = Unbraked
HDB = Hydraulic braked
PNB =
...