Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/TR 25100 — Intelligent Transport Systems: Systems Architecture — Harmonization of ITS Data Concepts
Practical Guidance for Semantic, Structural, and Syntactic Data Concept Harmonisation Across Intelligent Transport Systems
1. Introduction to Harmonization of ITS Data Concepts
ISO/TR 25100:2012, developed by ISO/TC 204 (Intelligent transport systems), provides user guidance for the harmonisation of data concepts where there are similarities in definitions, semantics, and structure across different ITS systems and standards. As intelligent transport systems have proliferated — encompassing traffic management, traveller information, electronic payment, freight logistics, public transport, and emergency response — the proliferation of independently defined data concepts has created significant interoperability barriers.
The fundamental problem is that different systems often represent the same real-world concept (e.g., “departure time”, “vehicle location”, “speed limit”) in different ways. These differences may be semantic (same term, different meaning), structural (same information, different data model), or syntactic (same data, different format). Without harmonisation, each pair of communicating systems requires custom interface development — an approach that scales poorly as the number of systems grows.
The document notes a key insight: harmonisation is not strictly essential for interoperability, which can be achieved through sufficient investment in point-to-point interfaces. However, this approach leads to duplication and nugatory work, and the total effort required increases with the square of the number of communicating systems.
2. Harmonisation Process and Methodological Approaches
ISO/TR 25100 defines a structured harmonisation process and evaluates four distinct approaches that have been applied in ITS and related domains.
| Approach | Origin | Core Method | Strengths | Limitations |
|---|---|---|---|---|
| ISO 14817 Harmonisation | ITS data registry | Centralized data concept registration; change control committee | Authoritative; well-defined process | Requires central governance body |
| ISO/IEC 20943 Approach | Metadata registries | Metadata-based concept mapping and equivalence | Rigorous semantic analysis | Complex; requires metadata expertise |
| UN/CEFACT TBG17 Core Components | Trade and business | Core component technical specification; business information entities | Cross-domain applicability | Heavyweight process |
| UK Highways Agency Core Components | ITS metadata registry | Core component analysis of existing data concepts | Practical; based on real data | ITS-specific scope |
2.1 The Harmonisation Process Steps
The document defines an eight-step harmonisation process: (1) identify candidate data concepts for harmonisation, (2) analyse the semantics of each concept, (3) identify similarities and differences, (4) assess the impact of differences on interoperability, (5) develop proposed harmonised definitions, (6) review with stakeholders, (7) publish harmonised concepts, and (8) maintain and update. The process is iterative — new concepts or implementation experience may trigger revision of previously harmonised definitions.
Harmonisation is particularly difficult in mature domains where there are already established implementations and standards but no single controlling authority to enforce the use of one particular standard. The document acknowledges that even partial harmonisation — where definitions are understood to grow closer without becoming identical — can provide significant value.
3. Engineering Design Insights: Practical Application
For system architects and data modellers working on ITS projects, ISO/TR 25100 offers several important insights:
3.1 Semantic, Structural, and Syntactic Harmonisation
The document identifies three levels at which harmonisation can be applied. Semantic harmonisation addresses differences in meaning — the classic example being travel service departure time expressed as local time with daylight savings in one system and UTC in another. Structural harmonisation addresses differences in data models — the same address information expressed as a flat structure in one system and a normalized relational model in another. Syntactic harmonisation addresses differences in format — XML vs. JSON vs. ASN.1 representations of the same data. Each level requires different analytical tools and stakeholder engagement.
3.2 The Role of Metadata Registries
ISO 14817 defines a data registry framework for ITS data concepts. A well-maintained registry provides a single point of reference for standardised data concepts, reducing duplication and enabling reuse. The document recommends that projects contribute their data concepts to the registry as part of the development process, building a shared resource over time. The UK Highways Agency case study in Annex A demonstrates how core component analysis of existing data concepts in the registry can reveal harmonisation opportunities.
3.3 Practical Trade-offs in Harmonisation
ISO/TR 25100 honestly addresses the practical challenges. Harmonisation requires investment of time and resources with benefits that are realized over the long term as interfaces become reusable. Projects under budget or schedule pressure may find it difficult to justify harmonisation activities. The document suggests pragmatic strategies: focus harmonisation efforts on high-value, frequently used concepts; adopt existing harmonised definitions where available; and contribute local definitions to the registry even if immediate harmonisation is not possible.
The most valuable practical contribution of ISO/TR 25100 is its harmonisation process and the worked example of the UK Highways Agency ITS Metadata Registry. For ITS architects, following this process — even informally — reduces the long-term cost of system integration and enables the data interoperability that is essential for the vision of seamlessly connected intelligent transport systems.
4. Frequently Asked Questions
Q1: How does data concept harmonisation differ from data standardization?
Standardization aims for a single definition that all parties must use. Harmonisation is a broader process that may result in standardization but can also produce mappings or translations that allow different definitions to coexist while maintaining interoperability.
Standardization aims for a single definition that all parties must use. Harmonisation is a broader process that may result in standardization but can also produce mappings or translations that allow different definitions to coexist while maintaining interoperability.
Q2: Is harmonisation relevant for modern web API-based ITS systems?
Yes — even more so. REST APIs, GraphQL, and event-driven architectures exchange data concepts, and without harmonisation, the proliferation of APIs recreates the same interoperability problems at a different level of abstraction.
Yes — even more so. REST APIs, GraphQL, and event-driven architectures exchange data concepts, and without harmonisation, the proliferation of APIs recreates the same interoperability problems at a different level of abstraction.
Q3: Who should be responsible for harmonisation within an ITS project?
The document recommends a data architect or information manager role with responsibility for data concept governance, supported by stakeholder representatives who understand the domain semantics.
The document recommends a data architect or information manager role with responsibility for data concept governance, supported by stakeholder representatives who understand the domain semantics.
Q4: How does this relate to ITS ontologies and semantic web technologies?
ISO/TR 25100 predates widespread adoption of ontologies in ITS but the harmonisation process is compatible with ontology-based approaches. Ontologies can provide the formal semantic framework that supports the harmonisation analysis described in the document.
ISO/TR 25100 predates widespread adoption of ontologies in ITS but the harmonisation process is compatible with ontology-based approaches. Ontologies can provide the formal semantic framework that supports the harmonisation analysis described in the document.
📥 Standard Documents Download
No download files available yet