1、 Reference number ISO/TR 25100:2012(E) ISO 2012TECHNICAL REPORT ISO/TR 25100 Second edition 2012-09-15 Intelligent transport systems Systems architecture Harmonization of ITS data concepts Systmes intelligents de transport Architecture des systmes Harmonisation des concepts de donnes SIT ISO/TR 2510
2、0:2012(E) COPYRIGHT PROTECTED DOCUMENT ISO 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the
3、 address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2012 All rights reservedISO/TR 25100:2012(E) ISO 2012 All ri
4、ghts reserved iiiContents Page Foreword iv Introduction . v 1 Scope 1 2 Terms, definitions and abbreviated terms 1 2.1 Terms and definitions . 1 2.2 Abbreviated terms . 2 3 Background issues . 4 3.1 Proprietary data concepts 4 3.2 Semantic differences 4 3.3 Structural differences . 4 3.4 Difficulty
5、of application of existing data concepts 5 3.5 Report of investigation . 5 4 Harmonisation General discussion 5 4.1 Introduction to harmonisation . 5 4.2 Illustration of the need for harmonisation 5 4.3 Challenges in harmonisation . 6 4.4 Harmonisation processes 7 4.5 Steps in the harmonisation proc
6、ess . 10 4.6 Other work related to harmonisation 11 5 Current approaches to harmonisation in ITS international standards 11 5.1 Four approaches . 11 5.2 ISO 14817 harmonisation . 12 5.3 ISO/IEC 20943 approach . 13 5.4 TBG17 Business process this basic idea is common to most description languages and
7、 metamodels including UML, XML and entity-relationship notations. 2.1.3 entity data concept that may have attributes and relationships to other entities NOTE This Technical Report follows common usage of the term “entity” where the words “entity kind” or “entity class” would be more accurate. 2.1.4
8、harmonisation of data concepts process of reconciling differences in semantics, structure and syntax of similar data concepts NOTE Harmonisation may include the establishment of a single pervasive definition for each data concept (i.e. standardization), but can also encompass flexible approaches in
9、which definitions can be understood to grow closer without becoming identical. ISO/TR 25100:2012(E) 2 ISO 2012 All rights reserved2.1.5 ontology rigorous conceptual schema representing the subject domain 2.1.6 relationship property of a data concept that defines its relation to another data concept
10、2.1.7 standardization of data concepts process of establishing a single standard definition for data concepts 2.1.8 taxonomy classification scheme for a subject domain 2.2 Abbreviated terms 2.2.1 ACC aggregate core component 2.2.2 ASCC association core component 2.2.3 ASN.1 abstract syntax notation
11、one 2.2.4 BCC basic core component 2.2.5 BIE business information entity 2.2.6 BRS business requirement specification 2.2.7 CC core component 2.2.8 CCC change control committee ISO 14817 (2002) 2.2.9 CCTS Core Components Technical Specification 2.2.10 CV controlled vocabulary ISO/TR 25100:2012(E) IS
12、O 2012 All rights reserved 32.2.11 DEN Dictionary Entry Name 2.2.12 ETL Extract, Transform and Load 2.2.13 IEC International Electrotechnical Commission 2.2.14 ISO International Organization for Standardization 2.2.15 ITS intelligent transport systems 2.2.16 MOF meta-object facility 2.2.17 QVT queries views and transformations 2.2.18 RSM requirements specification mapping 2.2.19 TBG17 Trade and Business Processes Group working group 17, UN/CEFACT 2.2.20 TC technical committee 2.2.21 TICS transport information
