SIST EN 16157-1:2019
(Main)Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 1: Context and Framework
Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 1: Context and Framework
This European Standard specifies and defines component facets required 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 the modelling approach, data content, data structure and relationships.
This European Standard 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);
- Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This European Standard establishes specifications 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 European Standard may be applicable for use by other actors.
This European Standard covers, at least, the following types of informational content:
- Road traffic event information - planned and unplanned occurrences both on the road network and in the surrounding environment;
- Information about operator initiated actions - including both advisory and mandatory measures;
- Road traffic measurement data, status data, and travel time data;
- Travel information relevant to road users, including weather and environmental information;
- Road traffic management information and information and advice relating to use of the road network.
This part of prEN 16157 specifies the DATEX II framework of all parts of this European Standard, the context of use and the modelling approach taken and used throughout these European Standard. This approach is described using formal methods and provides the mandatory reference framework for all other parts.
Intelligente Verkehrssysteme - Datex II Datenaustauschspezifikation für Verkehrsmanagement und Verkehrsinformation - Teil 1: Kontext und Rahmenwerk
Systèmes de transport intelligents - Spécifications DATEX II d'échange de données pour la gestion du trafic et l'information routière - Partie 1: Contexte et cadre général
Ce présent document spécifie et définit des aspects des composants requis pour permettre l’échange et le partage de données et d’informations dans le domaine de l’information de trafic et de parcours routiers.
Ces aspects constitutifs comprennent l’architecture et le contexte des échanges, la modélisation, le contenu des données, la structure des données et les relations entre elles.
Ce présent document est applicable :
— aux informations de trafic et de parcours routiers qui relèvent directement de l’utilisation du réseau routier (non urbain et urbain) ;
— aux informations sur les transports publics qui relèvent directement de l’utilisation du réseau routier (par exemple liaison routière via ferroutage ou bateau) ;
— aux informations de trafic ou de parcours routiers dans le cas de systèmes de transport intelligents coopératifs (C-ITS).
Ce présent document établit des spécifications d’échange de données entre deux instances quelconques des acteurs suivants :
— Centres d’informations routières ;
— Centres de gestion du trafic ;
— Prestataires de services.
Ce présent document peut également être utilisée par d’autres acteurs.
Ce présent document couvre, au minimum, les types suivants de contenu d’information :
— informations sur des événements concernant le trafic routier, planifiés ou non et pouvant survenir sur le réseau routier comme sur le milieu environnant ;
— informations sur les actions initiées par un opérateur – incluant à la fois des mesures conseillées et obligatoires ;
— données de trafic routier, données d’état et données de temps de parcours ;
— informations pour les usagers de la route, comprenant les informations météorologiques et environnementales ;
— informations sur la gestion du trafic routier et informations et conseils relatifs à l’utilisation du réseau routier.
Cette partie de la norme EN 16157 spécifie l’architecture Datex II de toutes les parties de cette Norme européenne, le contexte d’utilisation et la modélisation retenue et utilisée dans l’ensemble de la présente Norme européenne. Cette approche est décrite en utilisant des méthodes formelles et fournit le cadre de référence obligatoire pour toutes les autres parties.
Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri upravljanju prometa in informiranju - 1. del: Kontekst in okvir
Ta evropski standard določa vidike v zvezi s komponentami, potrebnimi za omogočanje izmenjave in skupne uporabe prometnih ter potovalnih podatkov in informacij.
Vidiki v zvezi s komponentami vključujejo kontekst in okvir za pristop z modeliranjem, vsebino podatkov, strukturo podatkov ter razmerja.
Ta evropski standard se uporablja za:
– prometne in potovalne informacije o prometu in potovanju, ki so pomembne za cestna omrežja (na podeželju in v mestih);
– informacije o javnem prevozu, ki so neposredno pomembne za uporabo cestnega omrežja (npr. cestna povezava prek železniške ali trajektne storitve);
– prometne in potovalne informacije v primeru kooperativnih inteligentnih transportnih sistemov (C-ITS).
Ta evropski standard določa specifikacije za izmenjavo podatkov med katerima koli akterjema na naslednjem seznamu:
– prometni informacijski centri (TIC);
– prometni nadzorni centri (TCC);
– ponudniki storitev (SP).
Ta evropski standard lahko uporabljajo tudi drugi akterji.
Ta evropski standard zajema najmanj naslednje vrste informacijskih vsebin:
– informacije o dogajanju v cestnem prometu – načrtovani ali nenačrtovani dogodki v cestnem omrežju in njegovi okolici;
– informacije o dejanjih, ki jih izvedejo izvajalci; – vključno s svetovalnimi in obveznimi ukrepi;
– podatki o merjenju cestnega prometa, podatki o stanju in času potovanja;
– potovalni podatki, ki so pomembni za uporabnike cest, vključno z informacijami o vremenu in okolju;
– informacije o upravljanju cestnega prometa in nasveti za uporabo cestnega omrežja.
Ta del standarda prEN 16157 določa okvir DATEX II vseh delov tega evropskega standarda, kontekst uporabe in pristop z modeliranjem, ki se uporablja v teh evropskih standardih. Ta pristop je opisan z uporabo uradnih metod in zagotavlja obvezen referenčni okvir za vse druge dele.
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri upravljanju prometa in informiranju - 1. del: Kontekst in okvirIntelligente Verkehrssysteme - Datex II Datenaustauschspezifikation für Verkehrsmanagement und Verkehrsinformation - Teil 1: Kontext und RahmenwerkSystèmes de transport intelligents - Spécifications DATEX II d'échange de données pour la gestion du trafic et l'information routière - Partie 1: Contexte et cadre généralIntelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 1: Context and Framework35.240.60Uporabniške rešitve IT v prometuIT applications in transportICS:Ta slovenski standard je istoveten z:EN 16157-1:2018SIST EN 16157-1:2019en,fr,de01-februar-2019SIST EN 16157-1:2019SLOVENSKI
STANDARDSIST-TS CEN/TS 16157-1:20111DGRPHãþD
SIST EN 16157-1:2019
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 16157-1
December
t r s z English Version
Intelligent transport systems æ DATEX II data exchange specifications for traffic management and information æ Part
sã Context and framework Systèmes de transport intelligents æ Spécifications DATEX II d 5échange de données pour la gestion du trafic et l 5information routière æ Partie
sã Contexte et cadre général
Intelligente Verkehrssysteme æ Datex II Datenaustauschspezifikation für Verkehrsmanagement und Verkehrsinformation æ Teil
sã Kontext und Rahmenwerk This European Standard was approved by CEN on
u September
t r s zä
egulations which stipulate the conditions for giving this European Standard the status of a national standard without any alterationä Upætoædate lists and bibliographical references concerning such national standards may be obtained on application to the CENæCENELEC Management Centre or to any CEN memberä
translation under the responsibility of a CEN member into its own language and notified to the CENæCENELEC Management Centre has the same status as the official versionsä
CEN members are the national standards bodies of Austriaá Belgiumá Bulgariaá Croatiaá Cyprusá Czech Republicá Denmarká Estoniaá Finlandá Former Yugoslav Republic of Macedoniaá Franceá Germanyá Greeceá Hungaryá Icelandá Irelandá Italyá Latviaá Lithuaniaá Luxembourgá Maltaá Netherlandsá Norwayá Polandá Portugalá Romaniaá Serbiaá Slovakiaá Sloveniaá Spainá Swedená Switzerlandá Turkey and United Kingdomä
EUROPEAN COMMITTEE FOR STANDARDIZATION COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre:
Rue de la Science 23,
B-1040 Brussels
9
t r s z CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Membersä Refä Noä EN
s x s w yæ sã t r s z ESIST EN 16157-1:2019
EN 16157-1:2018 (E) 2 Contents
Page European foreword . 4 Introduction . 5 1 Scope . 6 2 Normative references . 6 3 Terms and definitions . 7 4 Symbols and abbreviations . 10 5 Conformance . 10 6 General conventions and requirements . 10 6.1 Metamodelling . 10 6.2 DATEX II stereotype properties . 11 6.3 Naming conventions . 12 7 Platform independent model rules . 13 7.1 General . 13 7.2 Requirements on associations . 14 7.3 Requirements on attributes . 15 7.4 Requirements on classes . 16 7.5 Requirements on datatypes . 17 7.6 Requirements on enumerations . 18 7.7 Requirements on generalizations . 18 7.8 Requirements on literals . 19 7.9 Requirements on packages . 20 8 Extension rules. 20 8.1 General . 20 8.2 Numbered list of requirements. 21 Annex A (normative)
XML Schema Definition Mapping . 23 A.1 General . 23 A.2 Platform specific model rules for XML with XML schema definition. 23 A.2.1 General . 23 A.2.2 Requirements for mapping to XML schema definitions . 23 A.3 Mapping the PSM to XML schema definition . 24 A.3.1 General . 24 A.3.2 Mapping of “D2Datatype” and “ExternalType” . 24 A.3.3 Mapping of “D2Enumeration” and “D2Literal” . 25 A.3.4 Mapping of “D2Class” . 27 A.3.4.1 Mapping of “D2Class” classes that do not have a superclass . 27 A.3.4.2 Mapping of “D2Class” classes with a superclass . 29 A.3.5 Mapping of “D2Identifiable” and “D2VersionedIdentifiable” classes . 30 SIST EN 16157-1:2019
EN 16157-1:2018 (E) 3 A.3.6 XML elements . 31 A.3.7 Extension mapping . 31 A.3.8 Overall document structure and namespaces . 33 Bibliography . 34
SIST EN 16157-1:2019
EN 16157-1:2018 (E) 4 European foreword This document (EN 16157-1:2018) has been prepared by Technical Committee CEN/TC 278 “Intelligent transport systems”, the secretariat of which is held by NEN. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by June 2019, and conflicting national standards shall be withdrawn at the latest by June 2019. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN shall not be held responsible for identifying any or all such patent rights. Together with EN 16157-7, this document supersedes CEN/TS 16157-1:2011. The major differences introduced in this part are the following: — Correction of unclear phrases; — Methodology now based on UML 2; — Metamodel now based on explicit UML profile; — Pre-defined model elements removed (these are now covered by Part 7, see below). EN 16157-1 is the first part of a multi-part standard under the general title Intelligent transport systems — DATEX II data exchange specifications for traffic management and information. According to the CEN-CENELEC Internal Regulations, the national standards organisations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. SIST EN 16157-1:2019
EN 16157-1:2018 (E) 5 Introduction This European Standard defines a common set of data modelling specifications to support the vision of a seamless interoperable exchange of traffic and travel information across boundaries, including national, urban, interurban, road administrations, infrastructure providers and service providers. Standardization 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 gained 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 sustainable 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 to its development through an initial contract and subsequent co-funding through the Euro-Regional projects. With this standardization of DATEX II there is a real basis for common exchange between the actors of the traffic and travel information sector. This European Standard includes the framework and context for exchanges, the modelling approach, data content and data structure and relationships. This European Standard supports a methodology that is extensible. This part of EN 16157 is targeted towards all stakeholders that 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 modelling principles, the use of the Unified Modelling Language (UML) and other conventions for DATEX II modelling. Further to the UML modelling, this document also defines the mapping of this model to the eXtensible Markup Language (XML), used for formatting data in DATEX II data exchanges. XML, being the most widely used method nowadays of formatting data for business-to-business data exchange (i.e. centre-to-centre) over the Internet, is one of the possible solutions for mapping the UML modelling into formatted data. Other method like UPER based on ASN.1 defined by ISO/IEC 8825-2 can also be considered. SIST EN 16157-1:2019
EN 16157-1:2018 (E) 6 1 Scope This document specifies and defines components required to support the exchange and shared use of data and information in the field of traffic and travel. The components include the framework and context for the modelling approach, data content, data structure and relationships. This document 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), — traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS). This document establishes specifications 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 document can be applicable for use by other actors. This document covers, at least, the following types of informational content: — road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment, — information about operator-initiated actions – including both advisory and mandatory measures, — road traffic measurement data, status data, and travel time data, — travel information relevant to road users, including weather and environmental information, — road traffic management information and information and advice relating to use of the road network. This part of EN 16157 specifies the DATEX II framework of all parts of this European Standard, the context of use and the modelling approach taken and used throughout this European Standard. This approach is described using formal methods and provides the mandatory reference framework for all other parts. 2 Normative references The following documents are referred to in the text in such a way that some or all of their content constitutes requirements 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/IEC 14977:1996, Information technology — Syntactic metalanguage — Extended BNF ISO/IEC 19505-1:2012, Information technology — Object Management Group Unified Modeling Language (OMG UML) — Part 1: Infrastructure SIST EN 16157-1:2019
EN 16157-1:2018 (E) 7 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. ISO and IEC maintain terminological databases for use in standardization at the following addresses:
IEC Electropedia: available at http://www.electropedia.org/
ISO Online browsing platform: available at http://www.iso.org/obp
3.1 Terms and definitions adapted from ISO/IEC 19505-1:2012: NOTE Definitions have been adapted to meet the particular use of UML within this specification. 3.1.1 Association semantic relationship between classes 3.1.2 Attribute named slot within a class that describes a range of values that instances of the class may hold 3.1.3 Class description of a set of objects that share the same attributes, relationships, and semantics 3.1.4 Composition association between two classes, where one class is a composite and the other is a part Note 1 to entry: This characteristic is expressed in UML with an attribute named “isComposite” on the part end of the Association being set to “true”. 3.1.5 Dependency implementation or functioning of one or more elements that requires the presence of one or more other elements 3.1.6 Enumeration data type whose range is a list of predefined values, called enumeration literals 3.1.7 Enumeration literal element of the value space of an enumeration data type
3.1.8 Generalization taxonomic relationship between a more general element and a more specific element SIST EN 16157-1:2019
EN 16157-1:2018 (E) 8 3.1.9 Multiplicity range of integers specifying the allowable cardinalities for an instantiation of an element Note 1 to entry: The upper bound of the range cannot be below the lower bound. The lower bound shall be a nonnegative integer. The upper bound shall be a nonnegative integer or the special value unlimited, which indicates there is no upper bound on the range. 3.1.10 Package grouping of model elements 3.1.11 UML profile mechanism that allows metaclasses from existing metamodels to be extended to adapt them for different purposes Note 1 to entry: The term profile within the term UML profile has a different meaning than the term profile defined in 3.2.15. 3.1.12 Stereotype concept provides a way of branding (classifying) model elements so that they behave in some respects as if they were instances of new virtual metamodel constructs 3.2 Other terms and definitions: 3.2.1 binary (association) association that connects exactly two classes 3.2.2 extension set of data model elements not in the Level A model and following the Level B extension rules of DATEX II 3.2.3 Globally Unique Identifier – GUID Identifier that is unique in space and time, i.e. no other object will ever have the same identifier at any other place and at any time 3.2.4 Lower Camel Case – LCC description of the practice of concatenating compound phrases without whitespace in between where phrases are delimited by upper case letters and the initial letter is lower case EXAMPLE Lower Camel Case describes the case where the initial letter is lower case, e.g. as in lowerCamelCase. 3.2.5 Model Element generic term for any construct of metadata used within a model to specify a particular aspect or element of this model SIST EN 16157-1:2019
EN 16157-1:2018 (E) 9 3.2.6 Platform Independent Model – PIM model of aspects of an information system (e.g. the data model) that is independent of any technical platform used to implement the model Note 1 to entry: Concrete implementations can be derived from the platform independent model by platform specific models or mappings. 3.2.7 Platform Specific Model – PSM model of aspects of an information system (e.g. the data model) that is linked to a specific technological platform (e.g. a specific programming language or data transfer syntax) 3.2.8 Publication traffic-related information or associated management information created at a specific point in time that can be exchanged via a DATEX II interface Note 1 to entry: The “PayloadPublication” class is the top-level root class for DATEX II Level A. 3.2.9 Upper Camel Case – UCC description of the practice of concatenating compound phrases without whitespace in between where phrases are delimited by upper case letters and the initial letter is upper case EXAMPLE Upper Camel Case describes the case where the initial letter is upper case, e.g. as in UpperCamelCase. 3.2.10 Unique Resource Identifier / Locator – URI / URL character string of well-defined structure used to uniquely identify a resource Note 1 to entry: If that string is actually pointing at a resource accessible via the Internet, it is called a Unique Resource Locator. 3.2.11 eXtensible Markup Language – XML set of rules for encoding electronic documents defined by the World Wide Web Consortium W3C Note 1 to entry: Although developed for documents, it is today widely used for data exchange in general, usually in conjunction with an XML Schema Definition. 3.2.12 XML Metadata Interchange – XMI XML based specification for the interoperable exchange of metadata Note 1 to entry: It is today most commonly used to exchange UML models between UML tools. XMI is specified in ISO/IEC 19508. 3.2.13 XML Schema Definition – XSD formal description of the allowed content of an XML document that claims compliance to the schema Note 1 to entry: XML Schema Definitions allow for formal validation of syntactical compliance of instance documents. SIST EN 16157-1:2019
EN 16157-1:2018 (E) 10 3.2.14 Extension enlarged model incorporating new elements 3.2.15 Profile selection of possible, optional elements 3.2.16 Superclass generalization class containing elements a class shares with other classes 3.2.17 Namespace identifier that specifies a set of unique names 3.2.18 Facet defining aspect of a value space 4 Symbols and abbreviations GUID – Globally Unique identifier LCC – Lower Camel Case PIM – Platform Independent Model UCC – Upper Camel Case UML – Unified Modelling Language W3C – World Wide Web Consortium 5 Conformance This document provides requirements for UML models (as of ISO/IEC 19505-1:2012) that claim conformance with the DATEX II 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 provisions of this European Standard. 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. 6 General conventions and requirements 6.1 Metamodelling The DATEX II data modelling methodology uses the Unified Modelling Language (UML), version 2 as specified in ISO/IEC 19505-1:2012. More accurately the release 2.4.1 of UML 2 is used. UML provides a vast set of modelling elements that are not all used for DATEX II data modelling. In fact, DATEX II uses a fairly small UML profile, based on the following metaclasses from the Core::Basic and Core::Constructs packages specified in ISO/IEC 19505-1:2012: — Association (stereotypes: D2Relation); SIST EN 16157-1:2019
EN 16157-1:2018 (E) 11 — Attribute (stereotypes: D2Attribute, D2Literal); — Class (stereotypes: D2Class, D2Identifiable, D2VersionedIdentifiable, D2ModelRoot, ExternalClass); — DataType (stereotypes: D2Datatype, ExternalType); — Enumeration (stereotype: D2Enumeration); — Generalization (some of them having the stereotype: D2LevelBExtension); — Package (stereotypes: D2Package, D2Namespace, ExternalNamespace). DATEX II specifies metadata for the metaclasses in a UML profile with stereotypes which are assigned to the metaclasses, as listed above. Simple types that may be assigned to attributes are defined as datatypes or enumerations. Complex types (data structures) are defined as classes, with potential substructures connected via a composition. Generalization between classes is allowed, but multiple inheritance is prohibited, i.e. each class shall have either zero or one superclass. Classes, datatypes and enumerations may be structured in namespace packages, which define a namespace for their contained classes, datatypes, enumerations and sub-packages. They may also be structured simply in packages, which have no further semantics in DATEX II, they simply serve to structure DATEX II models and make them more accessible. Namespaces, classes and datatypes also have an option to refer to an external namespace, class or datatype. The stereotypes defined for this purpose contain only the metadata required to refer to the external entity. The specification of such external model elements is entirely out of the scope of this European Standard. Further to that, additional properties have been defined in the normative Annex A to govern the platform specific mapping to XML schema definitions. Other property sets may be added to generate an alternative platform specific model. Models that claim to comply with this specification may use these UML elements but shall comply with all provisions regarding the use of these elements. For readers not familiar with using UML or its graphical notations there is plenty of introductory material available to learn about UML in general and we would like to refer the reader to these resources for further study (e.g. to [1] or [2]). It should be noted that this European Standard uses only the default graphical representation of all UML elements used. Note that no provisions are made regarding the existence and use of other UML elements. Thus, compliant models may use these other elements, but they have no defined semantics in the framework of DATEX II. The stereotypes of the DATEX II UML profile related to the platform independent model have defined properties which are used in subsequent clauses to specify metamodel aspects. The allocation of which properties are used by which stereotypes is depicted in the diagrams in Clause 7. Further to that, additional properties have been defined to govern the platform specific mapping to XML schema definitions (ref. Annex A). Note that the following list of properties constitutes the list of properties governed by this European Standard. Other properties may exist but are not governed by this European Standard and have no semantics in the DATEX II specifications. 6.2 DATEX II stereotype properties 6.2.1 Properties for the Platform Independent Model are: definition: a clear, comprehensible and unambiguous definition of the modelled concept SIST EN 16157-1:2019
EN 16157-1:2018 (E) 12 description: a general textual reference and explanation of an external specification that is included in a DATEX II model by using either classes with stereotype “ExternalNamespace”, “ExternalType” and/or “ExternalClass”. extensionName: the name of an extension if the model is extended extensionVersion: the version of an extension if the model is extended modelBaseVersion: the number of the major component of a version number, e.g. “n” in case of version number “n.m” namespaceUri: a Universal Resource Identifier that uniquely identifed an external namespace order: allows determining the order in which multiple metaclasses shall occur in a serialized structure of a container profileName: the name of a profile if the model is a profile profileVersion: the version of a profile if the model is a profile regulatoryContext: a description of any relevant regulatory context that governs the creation or the structure of a metaclass, if applicable version: the full version number of the associated metaclass 6.2.2 Properties for the Platform Specific Model are: facets: the value of this property shall be a valid content for the restriction element of an XML schema simple type definition of a type restriction of the XML schema type that a DATEX II metaclass is mapped to prefix: a prefix used to represent a namespace in an XML Schema mapping rootElement: the indication to generate a top-level element in the schema with the class as type, using the property value as element name schemaAttribute: if this property is set to “yes”, an attribute with simple type (datatype or enumeration) from the platform independent model will be mapped to an XML attribute, if the property is empty or has any other value, it will be mapped to an XML element schemaLocation: A URL that points to an external XML schema that will be imported into the DATEX II schema schemaName: if this property is non-empty, its value will be used in the mapping of the metaclass instead of the metaclass' own “name” attribute or any name following any of the naming conventions provided in subsequent clauses of this European Standard schemaType: this property is used to name a XML Schema simple type that a DATEX II datatype is mapped to (ref. A.2.2.3) schemaTypeInclude: a reference to an externally specified XML schema type to be used as a mapping for this metaclass (ref. A.2.2.5) targetClass: for attributes referring to other classes (i.e. classes with stereotype “D2Identifiable” or “D2VersionedIdentifiable”), this attributes depicts the name of the other class and is used to create a typed reference. 6.3 Naming conventions 6.3.1 All names used in DATEX II UML models shall comply with the following rule set. SIST EN 16157-1:2019
EN 16157-1:2018 (E) 13 6.3.2 The following UML constructs used in this document may have a name that is used by the DATEX II metamodel: Attribute, Class, DataType, Enumeration, Package, Property. This name is specified via a “name” meta-attribute from that metaclass. If such a name meta-attribute is provided, it shall begin with a letter, followed by none or more letters or digits. A name is case sensitive. In formal terms, a DATEX II name shall comply with the following definition using Extended Backus Naur Form as of ISO/IEC 14977:1996. name ::=
letter ,
{ letter
| digit } letter ::=
“A” | “B” | “C” | “D” | “E” | “F” | “G” | “H” | “I” | “J” | “K” | “L” | “M” | “N” | “O” | “P” | “Q” | “R” | “S” | “T” | “U” | “V” | “W”
...
SLOVENSKI STANDARD
oSIST prEN 16157-1:2017
01-september-2017
Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri
upravljanju prometa in informiranju - 1. del: Skladnost in okvir
Intelligent transport systems - DATEX II data exchange specifications for traffic
management and information - Part 1: Context and Framework
Intelligente Verkehrssysteme - Datex II Datenaustauschspezifikation für
Verkehrsmanagement und Verkehrsinformation - Teil 1: Kontext und Rahmenwerk
Systèmes de transport intelligents - Spécifications DATEX II d'échange de données pour
la gestion du trafic et l'information routière - Partie 1: Contexte et cadre général
Ta slovenski standard je istoveten z: prEN 16157-1
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
oSIST prEN 16157-1:2017 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN 16157-1:2017
---------------------- Page: 2 ----------------------
oSIST prEN 16157-1:2017
DRAFT
EUROPEAN STANDARD
prEN 16157-1
NORME EUROPÉENNE
EUROPÄISCHE NORM
June 2017
ICS 35.240.60 Will supersede CEN/TS 16157-1:2011
English Version
Intelligent transport systems - DATEX II data exchange
specifications for traffic management and information -
Part 1: Context and Framework
Systèmes de transport intelligents - Spécifications Intelligente Verkehrssysteme - Datex II
DATEX II d'échange de données pour la gestion du Datenaustauschspezifikation für Verkehrsmanagement
trafic et l'information routière - Partie 1: Contexte et und Verkehrsinformation - Teil 1: Kontext und
cadre général Rahmenwerk
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 278.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations
which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and United Kingdom.
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 supporting documentation.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2017 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 16157-1:2017 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 6
3 Terms and definitions . 7
4 Symbols and abbreviations . 10
5 Conformance . 10
6 General conventions and requirements . 10
6.1 Metamodelling . 10
6.2 DATEX II stereotype properties . 11
6.3 Naming conventions . 12
7 Platform independent model rules . 13
7.1 General . 13
7.2 Requirements on associations . 13
7.3 Requirements on attributes . 15
7.4 Requirements on classes . 16
7.5 Requirements on DataTypes . 17
7.6 Requirements on enumerations . 19
7.7 Requirements on generalizations . 19
7.8 Requirements on literals . 20
7.9 Requirements on packages . 21
8 Extension rules. 22
8.1 General . 22
8.2 Numbered list of requirements. 23
Annex A (normative) XML Schema Definition Mapping . 25
A.1 General . 25
A.2 Platform specific model rules for XML with XML schema definition. 25
A.2.1 General . 25
A.2.2 Requirements for mapping to XML schema definitions . 25
A.3 Mapping the PSM to XML schema definition . 26
A.3.1 General . 26
A.3.2 Mapping of "D2Datatype" and "ExternalType" . 26
A.3.3 Mapping of "D2Enumeration" and "D2Literal" . 27
A.3.4 Mapping of "D2Class" . 29
A.3.4.1 Mapping of "D2Class" classes that do not have a superclass . 29
A.3.4.2 Mapping of "D2Class" classes with a superclass . 32
A.3.5 Mapping of "D2Identifiable" and “D2VersionedIdentifiable” classes . 32
2
---------------------- Page: 4 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
A.3.6 XML elements . 33
A.3.7 Extension mapping . 34
A.3.8 Overall document structure and namespaces . 35
Bibliography . 37
3
---------------------- Page: 5 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
European foreword
This document (prEN 16157-1:2017) has been prepared by Technical Committee CEN/TC 278
“Intelligent transport systems”, the secretariat of which is held by NEN.
This document is currently submitted to the CEN Enquiry.
This document, together with prEN 16157-7, will supersede CEN/TS 16157-1:2011.
The major differences introduced in this part are the following:
— Correction of unclear phrases
— Methodology now based on UML 2
— Metamodel now based on explicit UML Profile
— Pre-defined model elements removed (there are now covered by Part 7, see below).
prEN 16157-1 is the first part under the general title “Intelligent transport systems — DATEX II data
exchange specifications for traffic management and information”, the other parts being:
— Part 2: Location referencing
— Part 3: Situation publication
— Part 7: Common data elements
Other parts will be developed in the future.
4
---------------------- Page: 6 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
Introduction
This European Standard defines a common set of data modelling specifications to support the vision of
a seamless interoperable exchange of traffic and travel information across boundaries, including
national, urban, interurban, 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 gained 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 sustainable 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 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 European Standard includes the framework and context for exchanges, the modelling approach,
data content and data structure and relationships.
This European Standard supports a methodology that is extensible.
The European Committee for Standardisation (CEN) draws attention to the fact that it is claimed 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 part of prEN 16157 is targeted towards all stakeholders that 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 modelling principles, the use of the ― Unified
Modelling Language (UML) and other conventions for DATEX II modelling.
Further to the UML modelling, this European Standard also defines the mapping of this model to the
eXtensible Markup Language (XML), used for formatting data in DATEX II data exchanges. XML, being
the most widely used method nowadays of formatting data for business-to-business data exchange (i.e.
centre-to-centre) over the Internet, is one of the possible solutions for mapping the UML modelling into
formatted data. Other method like UPER based on ASN.1 defined by ISO/IEC 8825-2 can also be
considered.
5
---------------------- Page: 7 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
1 Scope
This European Standard specifies and defines component facets required 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 the modelling approach, data content,
data structure and relationships.
This European Standard 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);
— Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This European Standard establishes specifications 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 European Standard may be applicable for use by other actors.
This European Standard covers, at least, the following types of informational content:
— Road traffic event information – planned and unplanned occurrences both on the road network and
in the surrounding environment;
— Information about operator initiated actions – including both advisory and mandatory measures;
— Road traffic measurement data, status data, and travel time data;
— Travel information relevant to road users, including weather and environmental information;
— Road traffic management information and information and advice relating to use of the road
network.
This part of prEN 16157 specifies the DATEX II framework of all parts of this European Standard, the
context of use and the modelling approach taken and used throughout these European Standard. This
approach is described using formal methods and provides the mandatory reference framework for all
other parts.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 19505-1:2012, Information technology — Object Management Group Unified Modeling Language
(OMG UML) — Part 1: Infrastructure
6
---------------------- Page: 8 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
NOTE Definitions 3.1 to 3.12 have been adapted from ISO/IEC 19505-1:2012 to meet the particular use of
UML within this specification.
3.1
association
semantic relationship between classes
3.2
attribute
named slot within a class that describes a range of values that instances of the class may hold
3.3
class
description of a set of objects that share the same attributes, relationships, and semantics
3.4
composition
association between two classes, where one class is a composite and the other is a part
Note 1 to entry: This characteristic is expressed in UML with an attribute named “isComposite” on the part end
of the Association being set to “true”.
3.5
dependency
implementation or functioning of one or more elements that requires the presence of one or more other
elements
3.6
enumeration
data type whose range is a list of predefined values, called enumeration literals
3.7
Enumeration Literal
element of the value space of an Enumeration data type
3.8
generalization
taxonomic relationship between a more general element and a more specific element
3.9
multiplicity
range of integers
Note 1 to entry: The upper bound of the range cannot be below the lower bound. The lower bound is a
nonnegative integer. The upper bound is a nonnegative integer or the special value unlimited, which indicates
there is no upper bound on the range.
3.10
package
grouping of model elements
7
---------------------- Page: 9 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
3.11
profile
mechanism that allows metaclasses from existing metamodels to be extended to adapt them for
different purposes
3.12
stereotype
concept provides a way of branding (classifying) model elements so that they behave in some respects
as if they were instances of new virtual metamodel constructs
3.13
binary (association)
association that connects exactly two classes
3.14
extension
set of data model elements not in the Level A model and following the Level B extension rules of
DATEX II
3.15
Globally Unique Identifier
GUID
identifier that is unique in space and time, i.e. no other object will ever have the same identifier at any
other place and at any time
3.16
Lower Camel Case
LCC
description of the practice of concatenating compound phrases without whitespace in between where
phrases are delimited by upper case letters
Note 1 to entry: Lower Camel Case describes the case where the initial letter is lower case, e.g. as in
lowerCamelCase.
3.17
Model Element
generic term for any construct of metadata used within a model to specify a particular aspect or
element of this model
3.18
Platform Independent Model
PIM
model of aspects of an information system (e.g. the data model) that is independent of any technical
platform used to implement the model
Note 1 to entry: Concrete implementations can be derived from the platform independent model by platform
specific models or mappings.
3.19
Platform Specific Model
PSM
model of aspects of an information system (e.g. the data model) that is linked to a specific technological
platform (e.g. a specific programming language or data transfer syntax).
8
---------------------- Page: 10 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
3.20
publication
traffic related information or associated management information created at a specific point in time
that can be exchanged via a DATEX II interface
Note 1 to entry: The "PayloadPublication" class is the top level root class for DATEX II Level A.
3.21
Upper Camel Case
UCC
description of the practice of concatenating compound phrases without whitespace in between where
phrases are delimited by upper case letters
Note 1 to entry: Upper Camel Case describes the case where the initial letter is upper case, e.g. as in
UpperCamelCase.
3.22
Unique Resource Identifier / Locator
URI / URL
character string of well defined structure used to uniquely identify a resource
Note 1 to entry: If that string is actually pointing at a resource accessible via the Internet, it is called a Unique
Resource Locator.
3.23
eXtensible Markup Language
XML
set of rules for encoding electronic documents defined by the World Wide Web Consortium W3C.
Note 1 to entry: Although developed for documents, it is today widely used for data exchange in general, usually
in conjunction with an XML Schema Definition.
3.24
XML Metadata Interchange
XMI
XML based specification for the interoperable exchange of metadata.
Note 1 to entry: It is today most commonly used to exchange UML models between UML tools. XMI is specified
in ISO/IEC 19508:2014.
3.25
XML Schema Definition
XSD
formal description of the allowed content of an XML document that claims compliance to the schema.
Note: XML Schema Definitions allow for formal validation of syntactical compliance of instance
documents.
3.26
extension
enlarged model incorporating new elements
3.27
profile
selection of possible, optional elements
9
---------------------- Page: 11 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
3.28
superclass
generalisation class containing elements a class shares with other classes
3.29
namespace
identifier that specifies a set of unique names
3.30
facet
defining aspect of a value space
4 Abbreviations
For the purposes of this document, the following abbreviations apply.
GUID – Globally Unique identifier
LCC – Lower Camel Case
PIM – Platform Independent Model
UML – Unified Modeling Language
W3C – World Wide Web Consortium
5 Conformance
This document provides requirements for UML models (as of ISO/IEC 19505-1) that claim conformance
with the DATEX II 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 provisions
of this European Standard. 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.
6 General conventions and requirements
6.1 Metamodelling
The DATEX II data modelling methodology uses the Unified Modelling Language (UML), version 2 as
specified in UML ISO/IEC 19505-1. More accurately the release 2.4.1 of UML 2 is used.
UML provides a vast set of modelling elements that are not all used for DATEX II data modelling. In fact,
DATEX II uses a fairly small UML Profile, based on the following metaclasses from the Core::Basic and
Core:Constructs packages specified in ISO/IEC 19505-1:
— Association (stereotypes: D2Relation);
— Attribute (stereotypes: D2Attribute, D2Literal);
— Class (stereotypes: D2Class, D2Identifiable, D2VersionedIdentifiable, D2ModelRoot, ExternalClass);
— DataType (stereotypes: D2DataType, ExternalType);
— Enumeration (stereotype: D2Enumeration);
10
---------------------- Page: 12 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
— Generalization (some of them having the stereotype: D2LevelBExtension);
— Package (stereotypes: D2Package, D2Namespace, ExternalNamespace).
DATEX II specifies metadata for the metaclasses in a UML Profile with stereotypes which are assigned
to the metaclasses, as listed above.
Simple types that may be assigned to attributes are defined as datatypes or enumerations.
Complex types (data structures) are defined as classes, with potential substructures connected via
composition.
Generalization between classes is allowed, but multiple inheritance is prohibited, i.e. each class shall
have either zero or one superclass.
Classes, datatypes and enumerations may be structured in namespace packages, which define a
namespace for their contained classes, datatypes, enumerations and sub-packages. They may also be
structured simply in packages, which have no further semantics in DATEX II, they simply serve to
structure DATEX II models and make them more accessible.
Namespaces, classes and datatypes also have an option to refer to an external namespace, class or
datatype. The stereotypes defined for this purpose contain only the metadata required to refer to the
external entity. The specification of such external model elements is entirely out of the scope of this
European Standard.
Further to that, additional properties have been defined in the normative Annex A to govern the
platform specific mapping to XML schema definitions. Other property sets may be added to generate an
alternative platform specific model. Models that claim to comply with this specification may use these
UML elements but shall comply with all provisions regarding the use of these elements.
For readers not familiar with using UML or its graphical notations there is plenty of introductory
material available to learn about UML in general and we would like to refer the reader to these
resources for further study (e.g. to [1] or [2]). It should be noted that this European Standard uses only
the default graphical representation of all UML elements used.
Note that no provisions are made regarding the existence and use of other UML elements. Thus,
compliant models may use these other elements, but they have no defined semantics in the framework
of DATEX II.
The stereotypes of the DATEX II UML Profile related to the platform independent model have defined
properties which are used in subsequent clauses to specify metamodel aspects. The allocation of which
properties are used by which stereotypes is depicted in the diagrams in clause 7. Further to that,
additional properties have been defined to govern the platform specific mapping to XML schema
definitions (ref. Annex A). Note that the following list of properties constitutes the list of properties
governed by this European Standard. Other properties may exist but are not governed by this European
Standard and have no semantics in the DATEX II specifications.
6.2 DATEX II stereotype properties
6.2.1 Properties for the Platform Independent Model are:
definition: a clear, comprehensible and unambiguous definition of the modelled concept
description: a general textual reference and explanation of an external specification that is included in a
DATEX II model by using either classes with stereotype "ExternalNamespace", "ExternalType" and/or
"ExternalClass".
extensionName: the name of an extension if the model is extended
extensionVersion: the version of an extension if the model is extended
11
---------------------- Page: 13 ----------------------
oSIST prEN 16157-1:2017
prEN 16157-1:2017 (E)
modelBaseVersion: the number of the major component of a version number, e.g. "n" in case of version
number "n.m"
namespaceUri: a Universal Resource Identifier that uniquely identifed an external namespace
order: allows determining the order in which multiple metaclasses shall occur in a serialised structure
of a container
profileName: the name of a profile if the model is profiled
profileVersion: the version of a profile if the model is profiled
regulatoryContext: a description of any relevant regulatory context that governs the creation or the
structure of a metaclass, if applicable
version: the full version number of the associated metaclass
6.2.2 Properties for the Platform Specific Model are:
facets: the value of this property shall be a valid content for the restriction element of an XML schema
simple type definition of a type restriction of the XML schema type that a DATEX II metaclass is mapped
to
prefix: a prefix used to represent a namespace in an XML Schema mapping
rootElement: the indication to generate a top level element in the schema with the class as type, using
the property value as element name
schemaAttribute: if this property is set to "yes", an attribute with simple type (datatype or enumeration)
from the platform independent model will be mapped to an XML attribute, if the property is empty or
has any other value, it will be mapped to an XML element
schemaLocation: A URL that points to an external XML schema that will be imported into the DATEX II
schema
schemaName: if this property is non-empty, its value will be used in the mapping of the metaclass
instead of the metaclass' own "name" attribute or any name following any of the naming conventions
provided in subsequent clauses of this European Standard
schemaType: this property is used to name a XML Schema simple type that a DATEX II datatype is
mapped to (ref. A.2.2.3)
schemaTypeInclude: a reference to an externally specified XML schema type to be used as a mapping for
this metaclass (ref. A.2.2.5)
targetClass: for attributes referring to other classes (i.e. classes with stereotype "D2identifiable" or
"D2VersionedIdentifiable"), this attributes depicts the name of the other class and is used to create a
typed reference.
6.3 Naming conventions
6.3.1 All names used in DATEX II UML models shall comply with the following rule set.
6.3.2 The fol
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.