BSI PD ISO/TR 25100:2012:2013 Edition
$167.15
Intelligent transport systems. Systems architecture. Harmonization of ITS data concepts
| Published By | Publication Date | Number of Pages |
| BSI | 2013 | 44 |
This Technical Report provides guidance on the harmonisation of data concepts that are being managed by data registry and data dictionaries such as those described in ISO 14817:2002.
This Technical Report describes processes for harmonisation of such data concepts to arrive at preferred definitions for use in formal standards, specifications, technical reports and information models. It is based on consideration of a harmonisation process used by international groups involved in the ITS sector and in the wider sector of transport and logistics information and control systems.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 9 | 1 Scope 2 Terms, definitions and abbreviated terms 2.1 Terms and definitions |
| 10 | 2.2 Abbreviated terms |
| 12 | 3 Background issues 3.1 Proprietary data concepts 3.2 Semantic differences 3.3 Structural differences |
| 13 | 3.4 Difficulty of application of existing data concepts 3.5 Report of investigation 4 Harmonisation – General discussion 4.1 Introduction to harmonisation 4.2 Illustration of the need for harmonisation |
| 14 | 4.3 Challenges in harmonisation |
| 15 | 4.4 Harmonisation processes 4.4.1 Harmonisation contrasted with standardization |
| 16 | 4.4.2 Harmonisation by recognising underlying concepts |
| 18 | 4.4.3 Harmonisation and metadata registries 4.5 Steps in the harmonisation process 4.5.1 Derive entity boundaries – including names and semantics 4.5.2 Derive relationships – including role names and semantics |
| 19 | 4.5.3 Derive attributes – including names, semantics and datatypes 4.6 Other work related to harmonisation 4.6.1 Extract, Transform and Load (ETL) 4.6.2 MOF QVT (Meta-Object Facility Queries Views and Transformations) 5 Current approaches to harmonisation in ITS international standards 5.1 Four approaches 5.1.1 ISO 14817 approach 5.1.2 ISO/IEC 20943 approach 5.1.3 UN/CEFACT TBG17 approach 5.1.4 Highways Agency approach |
| 20 | 5.2 ISO 14817 harmonisation 5.2.1 Steps 5.2.2 Success of practical application of the process |
| 21 | 5.3 ISO/IEC 20943 approach 5.3.1 Part 1:Data elements 5.3.2 Part 3:Value domains |
| 22 | 5.3.3 Part 5:Semantic metadata mapping procedure 5.4 TBG17 Business process & core components 5.4.1 Fundamental idea of core components |
| 23 | 5.4.2 Harmonisation team submission guidelines and procedures |
| 24 | 5.4.3 Harmonisation rules 5.4.4 Success of practical application of the process 5.5 Highways Agency (UK) – Core Components Analysis of the ITS Metadata Registry 5.5.1 Basis |
| 25 | 5.5.2 Derivation of core components 5.5.3 Contrast with UN/CEFACT process |
| 27 | 5.5.4 Rules guiding the analysis |
| 28 | 5.5.5 Portraying mappings between entities |
| 29 | 5.5.6 Precise mappings |
| 31 | 5.5.7 Success of practical application of the process |
| 32 | 6 Harmonisation approach for designers of data specifications 6.1 Where there are relevant core components in a metadata registry or library |
| 33 | 6.2 Where there is no relevant registry using core components 7 Harmonisation as a means to improve efficiency |
| 34 | 8 Conclusions and recommendations |
