FprCEN ISO/TS 24315-4
(Main)Intelligent transport systems - Management of electronic traffic regulations (METR) - Part 4: System-level requirements (SysR) (ISO/DTS 24315-4:2026)
- Abstract
The management of electronic traffic regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network. This document defines the requirements for each of the component systems that make up the METR system of systems (SoS), including the METR regulation system, METR distribution system, METR consumer system, and METR discrepancy handling system
- Status
- Not Published
- Publication Date
- 17-Feb-2027
- Technical Committee
- CEN/TC 278 - Road transport and traffic telematics
- Drafting Committee
- CEN/TC 278/WG 17 - Ad hoc group U-ITS
- Current Stage
- 5020 - Submission to Vote - Formal Approval
- Start Date
- 27-Aug-2026
- Due Date
- 27-Apr-2027
- Completion Date
- 27-Aug-2026
FprCEN ISO/TS 24315-4 is a CEN/ISO technical specification for intelligent transport systems. It sets system-level requirements for management of electronic traffic regulations (METR), defining how the METR regulation system, METR distribution system, METR consumer system and METR discrepancy handling system work together to move authoritative, machine-interpretable road rules. It is aimed at authorities, system developers and operators who need a common requirements base for METR services.
What does FprCEN ISO/TS 24315-4 specify?
FprCEN ISO/TS 24315-4 specifies the requirements for the METR system of systems, with a focus on the four component systems named in the scope: METR regulation system (MRS), METR distribution system (MDS), METR consumer system (MCS) and METR discrepancy handling system (MDHS).
The document is organized around a system overview, information flow requirements, functional object requirements, external dependencies and an annex with deployment scenarios. Clause 5 explains the METR framework, traceability and how requirements are presented. Clause 6 sets out the information flows, Clause 7 sets out the functional requirements for each part of the system, and Clause 8 identifies external actors and responsibilities.
| Annex | What it covers |
|---|---|
| A | Deployment scenarios and MRS types, including a centre-based regulation system for pre-announced rules, a centre-based regulation system for emergent rules, and a localized regulation system |
What are the key requirements of FprCEN ISO/TS 24315-4?
FprCEN ISO/TS 24315-4 is built around defined information flows and subsystem behaviors. In practice, that means implementers have to design interfaces, security, verification and distribution behavior as a connected whole, not as isolated messages or apps.
Information flows are specified one by one
Clause 5.5 explains that the document presents requirements once per information flow, using the flow’s purpose, content, source, destination and any constraints. Clause 6 then applies that pattern to flows such as consolidated discrepancy reports, discrepancy report details, discrepancy suppression information, METR information, METR information for consumers, signed METR information, TCD discrepancy and TCD status.
This matters because a METR implementation can be checked flow by flow. Engineers can map each interface to a source, destination and security expectation, and quality teams can trace whether the right data reaches the right system.
Verification and discrepancy handling are central
Clause 7.1 and Clause 7.2 require collection awareness, update frequency, filtering, verification checks, logging of inconsistencies and notifications. The MRS also has requirements for independent verification, discrepancy management, approval and signing, packaging and provisioning, withholding unapproved information, rule provenance and TCD synchronization.
In practice, this means METR data is not just published once and forgotten. It has to be checked, logged, approved and kept aligned with the field state so that road users and automated systems receive rules that match what is actually in place.
Security, privacy and controlled use are built into the system
Clause 7.1.4 covers access control, auditing, limited use of data, identification and authentication, incident reporting, personally identifiable information, data minimization, confidentiality and system monitoring. Clause 6 repeats security as a named part of each information flow.
For implementers, this means security is not an add-on. The system has to control who can read, sign, distribute, verify and report METR information, and it has to keep records suitable for audits and incident handling.
The document expects interoperability over time and across regions
Clause 7.1.5 asks for open specification, backwards compatibility, forward compatibility and language neutral behavior. The introduction also says the METR framework supports regional adaptation and can work with non-METR protocols and data formats where they can carry the required information.
This matters because METR deployments may span different jurisdictions, existing roadside infrastructure and multiple transport data ecosystems. Systems need to exchange information without breaking older implementations or locking users into one local format.
The MDS focuses on delivery, repackaging and timely distribution
Clause 7.3 adds requirements for METR emergent information distribution, including CV RSE emergent information distribution, MDV emergent information distribution, broadcast management, status reporting, repackaging and distribution, location and characteristic constraints, priority delivery and efficient updates.
In practice, distribution systems must deliver changing rules fast enough for roadside units, connected vehicles and mobile users, while still respecting where the rule applies and which recipients should receive it.
The MCS must receive, verify and store usable rule information
Clause 7.4 covers METR reception, verification, availability, latency, preferred communications, radio frequency regulations, status reporting, terms of service and local storage of rules. It also includes discrepancy reporting and detection by METR information adaptation.
That means consumer systems are expected to do more than display data. They need to verify what they receive, handle delayed or unavailable links, keep local copies where needed and support user-facing behavior based on the verified rule set.
MDHS groups and consolidates discrepancy information
Clause 7.5 defines discrepancy report management, grouping, consolidated discrepancy report management, preparation of consolidated reports, notification of responsible systems, forwarding of details requests and suppression handling.
This matters for authorities and operators because multiple reports about the same road sign, TCD or rule can arrive from different sources. MDHS helps turn those reports into one managed view so repairs, updates and notifications can be coordinated.
What terms does FprCEN ISO/TS 24315-4 define?
- management of electronic traffic regulations (METR) - the METR framework for providing machine-interpretable road rules.
- system of systems (SoS) - the set of METR component systems operating together as one service chain.
- METR regulation system (MRS) - the part that manages rule creation, verification, approval, packaging and provisioning.
- METR distribution system (MDS) - the part that repackages and distributes METR information to recipients.
- METR consumer system (MCS) - the part that receives, verifies and uses METR information.
- METR discrepancy handling system (MDHS) - the part that manages discrepancy reports and consolidated discrepancy handling.
- first-tier MDHS - an MDHS that provides discrepancy information to another MDHS.
- second-tier MDHS - an MDHS that receives discrepancy information from another MDHS.
Who uses FprCEN ISO/TS 24315-4?
FprCEN ISO/TS 24315-4 is used by road authorities, transport system architects, software developers and operators that are building or running METR services. It is also relevant to organizations that manage rule creation, rule signing, verification, distribution and discrepancy handling.
Typical users include:
- METR operator and METR auditor
- rule maker, rule translation agent, rule signing agent and rule verification agent
- discrepancy handling system operators
- maintenance and construction management centre
- providers of supporting data, map data and roadside or vehicle systems
- organizations working in road transport and IT applications in transport
The document is especially useful where road rules must be distributed to connected vehicles, roadside equipment, user devices or other transport applications that depend on current and traceable rule information.
Which standards are used with FprCEN ISO/TS 24315-4?
| Standard | What it contributes |
|---|---|
| ISO/TS 14812 | ITS vocabulary used for transport-system terms |
| ISO/TS 24315-1 | METR vocabulary |
| ISO/IEC/IEEE 24765 | Systems and software engineering vocabulary |
| CEN ISO/TS 24315-3:2025 | METR system of systems requirements and architecture |
| NIST 800-53, Rev 5 | Security and privacy controls for information systems and organizations |
The overview also points readers to ISO 24315-2 for the METR operational concept and to ISO/TS 24315-3 for the structure of the METR system of systems.
What does the FprCEN ISO/TS 24315-4 document contain?
The document includes a METR system overview, a framework adaptation discussion and a graphical physical view of the METR subsystems. It then gives a catalog of information flows with purpose, content, source, destination and security for each flow. Clause 7 adds common system-level requirements plus separate requirement sets for MRS, MDS, MCS and MDHS. Clause 8 describes contextual functional objects and actors such as rule makers, users, auditors, vehicles, supporting data providers and maintenance and construction management centres. Annex A provides deployment scenarios and MRS types for different regulatory setups.
Relations
- Effective Date
- 12-Feb-2026
Get Certified
Connect with accredited certification bodies for this standard
BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
Great Wall Tianjin Quality Assurance Center
Established 1993, first batch to receive national accreditation with IAF recognition.
Hong Kong Quality Assurance Agency (HKQAA)
Hong Kong's leading certification body.
Sponsored listings
Frequently Asked Questions
FprCEN ISO/TS 24315-4 is a draft published by the European Committee for Standardization (CEN). Its full title is "Intelligent transport systems - Management of electronic traffic regulations (METR) - Part 4: System-level requirements (SysR) (ISO/DTS 24315-4:2026)". This standard covers: The management of electronic traffic regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network. This document defines the requirements for each of the component systems that make up the METR system of systems (SoS), including the METR regulation system, METR distribution system, METR consumer system, and METR discrepancy handling system
The management of electronic traffic regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network. This document defines the requirements for each of the component systems that make up the METR system of systems (SoS), including the METR regulation system, METR distribution system, METR consumer system, and METR discrepancy handling system
FprCEN ISO/TS 24315-4 is classified under the following ICS (International Classification for Standards) categories: 03.220.20 - Road transport; 35.240.60 - IT applications in transport. The ICS classification helps identify the subject area and facilitates finding related standards.
FprCEN ISO/TS 24315-4 has the following relationships with other standards: It is inter standard links to ISO/DTS 24315-4. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
FprCEN ISO/TS 24315-4 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2026
Inteligentni transportni sistemi - Vodenje elektronskih prometnih predpisov
(METR) - 4. del: Sistemsko-nivojske zahteve (SysR) (ISO/DTS 24315-4:2026)
Intelligent transport systems - Management of electronic traffic regulations (METR) - Part
4: System-level requirements (SysR) (ISO/DTS 24315-4:2026)
Intelligente Verkehrssysteme - Management von elektronischen Verkehrsregularien
(METR) - Teil 4: Anforderungen an die Systemebene (SysR) (ISO/DTS 24315-4:2026)
Systèmes de transport intelligents - Gestion des règles de circulation sous forme
électronique - Partie 4: Exigences au niveau système (ISO/DTS 24315-4:2026)
Ta slovenski standard je istoveten z: FprCEN ISO/TS 24315-4
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
FINAL DRAFT
Technical
Specification
ISO/DTS 24315-4
ISO/TC 204
Intelligent transport systems —
Secretariat: ANSI
Management of electronic traffic
Voting begins on:
regulations (METR) —
2026-08-26
Part 4:
Voting terminates on:
2026-11-18
System-level requirements (SysR)
Systèmes de transport intelligents — Gestion des règles de
circulation sous forme électronique —
Partie 4: Exigences au niveau système
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/CEN PARALLEL PROCESSING LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
ISO/DTS 24315-4:2026(en) © ISO 2026
FINAL DRAFT
ISO/DTS 24315-4:2026(en)
Technical
Specification
ISO/DTS 24315-4
ISO/TC 204
Intelligent transport systems —
Secretariat: ANSI
Management of electronic traffic
Voting begins on:
regulations (METR) —
Part 4:
Voting terminates on:
System-level requirements (SysR)
Systèmes de transport intelligents — Gestion des règles de
circulation sous forme électronique —
Partie 4: Exigences au niveau système
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© ISO 2026
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/CEN PARALLEL PROCESSING
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland Reference number
ISO/DTS 24315-4:2026(en) © ISO 2026
ii
ISO/DTS 24315-4:2026(en)
Contents Page
Foreword .vii
Introduction .viii
0.1 System overview .viii
0.1.1 General .viii
0.1.2 Purpose .viii
0.1.3 Flow of information .viii
0.1.4 Graphical overview . ix
0.1.5 Rule distribution .x
0.2 Framework adaptation . . xi
0.3 Document overview .xii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms. 2
5 Overview . 3
5.1 General .3
5.2 Assumptions and dependencies .3
5.2.1 Customizing requirements .3
5.2.2 Internet-based communications .4
5.2.3 Vehicle communications .4
5.2.4 Geo-positioning rules .4
5.2.5 Leverage existing standards.4
5.2.6 Efficient data exchange.4
5.2.7 Additional requirements .4
5.3 Traceability conventions.4
5.4 External responsibilities .4
5.5 Presentation of requirements .4
5.6 Physical view .5
5.6.1 General .5
5.6.2 Physical view diagrams .6
6 Information flow requirements.13
6.1 Information flow: consolidated discrepancy report . 13
6.1.1 Purpose of consolidated discrepancy report . 13
6.1.2 Content of consolidated discrepancy report . 13
6.1.3 Source of consolidated discrepancy report . 13
6.1.4 Destination of consolidated discrepancy report .14
6.1.5 Security for consolidated discrepancy report .14
6.1.6 Instances of consolidated discrepancy report .14
6.2 Information flow: discrepancy report details .14
6.2.1 Purpose of discrepancy report details .14
6.2.2 Content of discrepancy report details .14
6.2.3 Source of discrepancy report details . 15
6.2.4 Destination of discrepancy report details . 15
6.2.5 Security for discrepancy report details. 15
6.3 Information flow: discrepancy suppression information . 15
6.3.1 Purpose of discrepancy suppression information . 15
6.3.2 Content of discrepancy suppression information .16
6.3.3 Source of discrepancy suppression information .16
6.3.4 Destination of discrepancy suppression information .16
6.3.5 Security for discrepancy suppression information.16
6.4 Information flow: local METR information for consumers .16
6.4.1 Purpose of local METR information for consumers .16
6.4.2 Content of local METR information for consumers .16
iii
ISO/DTS 24315-4:2026(en)
6.4.3 Source of local METR information for consumers.17
6.4.4 Destination of local METR information for consumers .17
6.4.5 Security for local METR information for consumers .17
6.5 Information flow: METR application information .17
6.5.1 Purpose of METR application information .17
6.5.2 Content of METR application information .17
6.5.3 Source of METR application information .17
6.5.4 Destination of METR application information .17
6.5.5 Security for METR application information .18
6.6 Information flow: METR application status .18
6.6.1 Purpose of METR application status .18
6.6.2 Content of METR application status .18
6.6.3 Source of METR application status .18
6.6.4 Destination of METR application status .18
6.6.5 Security for METR application status . .18
6.7 Information flow: METR coordination .19
6.7.1 Purpose of METR coordination .19
6.7.2 Content of METR coordination .19
6.7.3 Source of METR coordination .19
6.7.4 Destination of METR coordination .19
6.7.5 Security for METR coordination .19
6.8 Information flow: METR device status . 20
6.8.1 Purpose of METR device status . 20
6.8.2 Content of METR device status . 20
6.8.3 Source of METR device status . 20
6.8.4 Destination of METR device status . 20
6.8.5 Security for METR device status . 20
6.9 Information flow: METR discrepancy report . . 20
6.9.1 Purpose of METR discrepancy report . 20
6.9.2 Content of METR discrepancy report . 20
6.9.3 Source of METR discrepancy report .21
6.9.4 Destination of METR discrepancy report .21
6.9.5 Security for METR discrepancy report .21
6.10 Information flow: METR emergent rule input .21
6.10.1 Purpose of METR emergent rule input .21
6.10.2 Content of METR emergent rule input.21
6.10.3 Source of METR emergent rule input . 22
6.10.4 Destination of METR emergent rule input. 22
6.10.5 Security for METR emergent rule input . 22
6.11 Information flow: METR feedback . 22
6.11.1 Purpose of METR feedback . 22
6.11.2 Content of METR feedback . . . 22
6.11.3 Source of METR feedback . 22
6.11.4 Destination of METR feedback . 22
6.11.5 Security for METR feedback . 23
6.12 Information flow: METR information . 23
6.12.1 Purpose of METR information . 23
6.12.2 Content of METR information . 23
6.12.3 Source of METR information . 23
6.12.4 Destination of METR information . 23
6.12.5 Security for METR information . 23
6.13 Information flow: METR information for consumers .24
6.13.1 Purpose of METR information for consumers .24
6.13.2 Content of METR information for consumers.24
6.13.3 Source of METR information for consumers .24
6.13.4 Destination of METR information for consumers .24
6.13.5 Security for METR information for consumers .24
6.14 Information flow: METR information signature request .24
6.14.1 Purpose of METR information signature request .24
iv
ISO/DTS 24315-4:2026(en)
6.14.2 Contents of METR information signature request .24
6.14.3 Source of METR information signature request .24
6.14.4 Destination of METR information signature request . 25
6.14.5 Security for METR information signature request . 25
6.15 Information flow: METR input . 25
6.15.1 Purpose of METR input . 25
6.15.2 Content of METR input . 25
6.15.3 Source of METR input . 25
6.15.4 Destination of METR input . 25
6.15.5 Security for METR input . 25
6.16 Information flow: METR management information . 25
6.16.1 Purpose of METR management information . 25
6.16.2 Content of METR management information . 26
6.16.3 Source of METR management information . . 26
6.16.4 Destination of METR management information . 26
6.16.5 Security for METR management information . 26
6.17 Information flow: signed METR information . 26
6.17.1 Purpose of signed METR information . 26
6.17.2 Content of signed METR information . 26
6.17.3 Source of signed METR information . 26
6.17.4 Destination of signed METR information . 26
6.17.5 Security for signed METR information .27
6.18 Information flow: system-generated discrepancy report .27
6.18.1 Purpose of system-generated discrepancy report.27
6.18.2 Content of system-generated discrepancy report .27
6.18.3 Source of system-generated discrepancy report .27
6.18.4 Destination of system-generated discrepancy report .27
6.18.5 Security for system-generated discrepancy report .27
6.19 Information flow: TCD discrepancy . 28
6.19.1 Purpose of TCD discrepancy . 28
6.19.2 Content of TCD discrepancy . 28
6.19.3 Source of TCD discrepancy. 28
6.19.4 Destination of TCD discrepancy . 28
6.19.5 Security for TCD discrepancy . 28
6.20 Information flow: TCD discrepancy status . 28
6.20.1 Purpose of TCD discrepancy status . 28
6.20.2 Content of TCD discrepancy status . 28
6.20.3 Source of TCD discrepancy status . 29
6.20.4 Destination of TCD discrepancy status . 29
6.20.5 Security for TCD discrepancy status . 29
6.21 Information flow: TCD status . 29
6.21.1 Purpose of TCD status . 29
6.21.2 Content of TCD status . 29
6.21.3 Source of TCD status . 30
6.21.4 Destination of TCD status . 30
6.21.5 Security for TCD status . 30
6.22 Information flow: unverified METR information . 30
6.22.1 Purpose of unverified METR information . 30
6.22.2 Content of unverified METR information . 30
6.22.3 Source of unverified METR information . 30
6.22.4 Destination of unverified METR information . 30
6.22.5 Security for unverified METR information. 30
6.23 Information flow: verified METR information .31
6.23.1 Purpose of verified METR information .31
6.23.2 Content of verified METR information .31
6.23.3 Source of verified METR information .31
6.23.4 Destination of verified METR information .31
6.23.5 Security for verified METR information .31
v
ISO/DTS 24315-4:2026(en)
7 Functional object requirements .31
7.1 Common system-level METR requirements .31
7.1.1 METR Collection & Verification . .31
7.1.2 METR information verification .32
7.1.3 Coordination METR activities . 33
7.1.4 ITS-S unit requirements . 33
7.1.5 General requirements . 34
7.2 Additional MRS requirements . 34
7.2.1 Independent METR verification . 34
7.2.2 METR discovered rule management . 35
7.2.3 METR discrepancy management . 35
7.2.4 METR information approval .37
7.2.5 METR packaging and provisioning .37
7.2.6 METR translation . 39
7.3 Additional MDS requirements .41
7.3.1 METR emergent information distribution .41
7.3.2 METR repackaging and distribution .42
7.3.3 Radio frequency regulations .43
7.3.4 ITS management support .43
7.4 Additional MCS requirements .43
7.4.1 ITS management support .43
7.4.2 METR discrepancy reporting .43
7.4.3 METR reception . . . 44
7.4.4 METR verification .45
7.4.5 Other MCS requirements . .45
7.5 Additional MDHS requirements . 46
7.5.1 ITS management support . 46
7.5.2 METR discrepancy handling . 46
7.5.3 Consolidate discrepancy reports . 46
8 External dependencies . 47
8.1 Contextual functional objects .47
8.1.1 Data collection and provisioning .47
8.1.2 METR information adaptation .47
8.1.3 User device functions . 48
8.2 Actors . 48
8.2.1 Discrepancy handling system operators . 48
8.2.2 Maintenance and construction management centre . 49
8.2.3 Map providers . 49
8.2.4 METR auditor . 49
8.2.5 METR operator . 49
8.2.6 METR user . 50
8.2.7 Non-METR distribution centre . 50
8.2.8 Rule maker . 50
8.2.9 Rule implementation agent . 50
8.2.10 Rule signing agent . 50
8.2.11 Rule translation agent .51
8.2.12 Rule verification agent .52
8.2.13 Supporting data providers .52
8.2.14 Vehicles . 53
Annex A (informative) Deployment scenarios .54
Bibliography .57
vi
ISO/DTS 24315-4:2026(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
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 ISO 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).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes 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 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. ISO shall not be held responsible
...