1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationDD CEN/TS 16157-1:2011Intelligent transport systems DATEX II data exchangespecifications for trafficmanagement and informationPart 1: Context and frameworkDD CEN/TS 16157-1:2011
2、DRAFT FOR DEVELOPMENTNational forewordThis Draft for Development is the UK implementation of CEN/TS16157-1:2011. DD ENV 13106:2000 and DD ENV 13777:2000 werewithdrawn in 2007 as ENV 13106:2000 and ENV 13777:2000 expiredwithout producing an EN standard.DATEX II is founded on a single UML model which
3、is madeavailable in a useable format to all through the website, http:/www.datex2.eu/.This publication is not to be regarded as a British Standard.It is being issued in the Draft for Development series of publicationsand is of a provisional nature. It should be applied on thisprovisional basis, so t
4、hat information and experience of its practicalapplication can be obtained.Comments arising from the use of this Draft for Developmentare requested so that UK experience can be reported to theinternational organization responsible for its conversion toan international standard. A review of this publ
5、ication willbe initiated not later than 3 years after its publication by theinternational organization so that a decision can be taken on itsstatus. Notification of the start of the review period will be made inan announcement in the appropriate issue of Update Standards.According to the replies rec
6、eived by the end of the review period,the responsible BSI Committee will decide whether to support theconversion into an international Standard, to extend the life of theTechnical Specification or to withdraw it. Comments should be sentto the Secretary of the responsible BSI Technical Committee at B
7、ritishStandards House, 389 Chiswick High Road, London W4 4AL.The UK participation in its preparation was entrusted to TechnicalCommittee EPL/278, Road transport informatics.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purp
8、ort to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. BSI 2011ISBN 978 0 580 72442 8ICS 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This Draft for Development was published under the authority ofthe St
9、andards Policy and Strategy Committee on 31 October 2011.Amendments issued since publicationDate Text affectedDD CEN/TS 16157-1:2011TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 16157-1 October 2011 ICS 35.240.60 Supersedes ENV 13106:2000, ENV 13777:2000English Versi
10、on Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 1: Context and framework Systmes de transport intelligents - Spcifications DATEX II dchange de donnes pour la gestion du trafic et linformation routire - Partie 1: Contexte et cadre
11、 gnralIntelligente Transportsysteme - DATEX II Datenaustausch Spezifikationen fr Verkehrsmanagement und Informationen - Teil 1: Kontext und Rahmenstruktur This Technical Specification (CEN/TS) was approved by CEN on 10 April 2011 for provisional application. The period of validity of this CEN/TS is
12、limited initially to three years. After two years the members of CEN will be requested to submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard. CEN members are required to announce the existence of this CEN/TS in the same way as for an EN a
13、nd to make the CEN/TS available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached. CEN members are the national st
14、andards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland an
15、d United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels 2011 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TS 16
16、157-1:2011: EDD CEN/TS 16157-1:2011CEN TS 16157-1:2011 2 Contents Page Introduction .51 Scope 62 Conformance 63 Normative references 74 Terms and definitions .74.1 Terms and definitions adapted from ISO/IEC 19501:2005 .74.2 Other terms and definitions 85 Symbols and abbreviated terms . 106 General c
17、onventions and requirements . 106.1 Metamodelling . 106.2 Naming conventions 126.3 Notational conventions 137 Platform independent model rules 137.1 General . 137.2 Numbered list of requirements 138 Predefined model elements . 158.1 General . 158.2 Top Level model packages and classes 158.3 Basic da
18、tatypes. 179 Extension Rules 179.1 General . 179.2 Numbered list of requirements 18Annex A (informative) History and Background of DATEX II 19A.1 Introduction . 19A.2 Separation of payload content and exchange . 19A.3 Modelling approach: abstract specification and platform mappings . 20Annex B (info
19、rmative) UML graphical notation 22Annex C (informative) DATEX II Metamodel . 25C.1 Introduction . 25C.2 Meta-Metamodel how to describe a metamodel? . 26C.3 The DATEX II metamodel . 26Annex D (normative) XML Schema Definition Mapping . 31D.1 General . 31D.2 Platform specific model rules for XML with
20、XML schema definition 31D.2.1 General . 31D.2.2 Numbered list of requirements 31D.3 Mapping the PSM to XML Schema Definition 32D.3.1 Mapping of “D2Datatype“ 32D.3.2 Mapping of “D2Enumeration“ and “D2Literal“ 33D.3.3 Mapping of “D2Component“ 33D.3.4 Mapping of “D2Identifiable“ classes. 36D.3.5 XML el
21、ements 37D.3.6 Extension mapping . 37D.3.7 Overall document structure and namespaces . 38Annex E (normative) General structure element 39DD CEN/TS 16157-1:2011CEN/TS 16157-1:2011 (E) 3 E.1 Package “D2LogicalModel“ 39E.2 Package “PayloadPublication“ 40E.3 Package “General“ 42E.4 Package “DataTypes“ .
22、 42E.5 Package “Generic“ 43Bibliography 46DD CEN/TS 16157-1:2011CEN/TS 16157-1:2011 (E) 4 Foreword This document (CEN/TS 16157-1:2011) has been prepared by Technical Committee CEN/TC 278 “Road transport and traffic telematics”, the secretariat of which is held by NEN. Attention is drawn to the possi
23、bility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identifying any or all such patent rights. This document supersedes ENV 13106:2000, ENV 13777:2000. As a user of the standard, attention is drawn to the resourc
24、es of www.datex2.eu. This web site contains related software tools and software resources that aid the implementation of CEN/TS 16157 DATEX II. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to announce this Technical Spec
25、ification: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the U
26、nited Kingdom. DD CEN/TS 16157-1:2011CEN/TS 16157-1:2011 (E) 5 Introduction This Technical Specification defines a common set of data exchange specifications to support the vision of a seamless interoperable exchange of traffic and travel information across boundaries, including national, urban, int
27、erurban, road administrations, infrastructure providers and service providers. Standardisation in this context is a vital constituent to ensure interoperability, reduction of risk, reduction of the cost base, promotion of open marketplaces and many social, economic and community benefits to be gaine
28、d from more informed travellers, network managers and transport operators. Delivering European Transport Policy in line with the White Paper issued by the European Commission requires co-ordination of traffic management and development of seamless pan European services. With the aim to support susta
29、inable mobility in Europe, the European Commission has been supporting the development of information exchange mainly between the actors of the road traffic management domain for a number of years. In the road sector, DATEX II has been long in fruition, with the European Commission being fundamental
30、 to its development through an initial contract and subsequent co-funding through the Euro-Regional projects. With this standardisation of DATEX II there is a real basis for common exchange between the actors of the traffic and travel information sector. This Technical Specification includes the fra
31、mework and context for exchanges, the modelling approach, data content, data structure and relationships, communications specification. This Technical Specification supports a methodology that is extensible. The European Committee for Standardisation (CEN) draws attention to the fact that it is clai
32、med that compliance with this document may involve the use of a patent concerning procedures, methods and/or formats given in this document. CEN takes no position concerning the evidence, validity and scope of patent rights. This document (i.e. CEN/TS 16157-1) is targeted towards all stakeholders th
33、at want to understand the modelling methodology applied throughout the DATEX II specifications. While this is potentially a wide range of readers, the document addresses specifically those users that intend to extend the DATEX II data model and therefore need to understand and comply with the modell
34、ing principles, the use of the “Unified Modeling Language” (UML) and other conventions for DATEX II modelling. The subject matter may be difficult to address without some basic background about the historical evolution and main design decisions taken. Users unfamiliar with this background may find a
35、 brief summary in Annex A. Users not (yet) familiar with the UML find a brief introduction in the informative Annex B. Further to the UML modelling, this Technical Specification also defines the mapping of this model to the “eXtensible Markup Language” (XML), used for formatting data in DATEX II dat
36、a exchanges. XML is the most widely used method nowadays of formatting data for business-to-business data exchange (i.e. centre-to-centre) over the Internet. DD CEN/TS 16157-1:2011CEN/TS 16157-1:2011 (E) 6 1 Scope This Technical Specification (CEN/TS 16157-1) specifies and defines component facets r
37、equired to support the exchange and shared use of data and information in the field of traffic and travel. The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships, communications specification. This Technical Specif
38、ication is applicable to: traffic and travel information which is of relevance to road networks (non urban and urban); public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service). This Technical Specification establishes specifica
39、tions for data exchange between any two instances of the following actors: Traffic Information Centres (TICs); Traffic Control Centres (TCCs); Service Providers (SPs). Use of this Technical Specification may be applicable for use by other actors. This Technical Specification covers, at least, the fo
40、llowing types of informational content: road traffic event information planned and unplanned occurrences both on the road network and in the surrounding environment; operator initiated actions; road traffic measurement data, status data, and travel time data; travel information relevant to road user
41、s, including weather and environmental information; road traffic management information and information and advice relating to use of the road network. This part of CEN/TS 16157 specifies the DATEX II framework of all parts of this Technical Specification, the context of use and the modelling approa
42、ch taken and used throughout these Technical Specifications. This approach is described using formal methods and provides the mandatory reference framework for all other parts. 2 Conformance This document provides requirements for UML models (as of ISO/IEC 19501:2005) that claim conformance with the
43、 DATEX II Technical Specifications. UML models claiming this conformance shall comply with the provisions of the normative clauses and annex of this part. Conformance with metadata constructs is subject to multiplicity requirements stated explicitly in the model or is implicitly defined in provision
44、s of this Technical Specification. Metadata constructs with minimum multiplicity of 1 or more shall be present in any data claiming conformance. Metadata constructs with minimum multiplicity of 0 may be present or may be missing without violating conformance. DD CEN/TS 16157-1:2011CEN/TS 16157-1:201
45、1 (E) 7 3 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 639-2:1998, Co
46、des for the representation of names of languages Part 2: Alpha-3 code ISO 3166-1:2006, Codes for the representation of names of countries and their subdivisions Part 1: Country codes ISO/IEC 14977:1996, Information technology Syntactic metalanguage Extended BNF ISO/IEC 19501:2005, Information techno
47、logy Open Distributed Processing Unified Modeling Language (UML) Version 1.4.2 ISO/IEC 19503:2005, Information technology XML Metadata Interchange (XMI) 4 Terms and definitions For the purposes of this document, the following terms and definitions apply. 4.1 Terms and definitions adapted from ISO/IE
48、C 19501:2005 NOTE Definitions have been adapted to meet the particular use of UML within this specification. 4.1.1 association semantic relationship between classes 4.1.2 association end endpoint of an association, which connects the association to a class 4.1.3 aggregation association where the tar
49、get class is an aggregate; therefore the source class is a part. This characteristic is expressed in UML with an attribute named “aggregation” on the target side Association End being set to “aggregate” 4.1.4 attribute named slot within a class that describes a range of values that instances of the class may hold 4.1.5 class description of a set of objects that share the same attributes, relationships, and semantics 4.1.6 composi
