Content
| Table of Contents |
|---|
...
NeTEx supports the exchange of data nessescary for stop place information, journey planning, and ticketing, and is divided into their main categories
- Network topology Topology (
CEN TS 16614-1) - Scheduled Timetables Plan data (
CEN TS 16614-2) - Tariff-information Fare Information (
CEN TS 16614-3)
NeTEx was created by CEN / TC278 / WG3 / SG9 lead by France. The final part of the format was published in 2015. The format was created to support the needs of a collection of public transport data providers in Europe, among others ERA (European Rail Agency) and UIC (International Union of Railways).
NeTEx is an XML format that facilitates the exchange of route timetable data between distributed systems. Data in the NeTEx format should be used to effectively update various information and operational applications through both file-based services and web service architectures. The official website contains a detailed explanation of the intention underlying the standard, data models and publicly available standard documentation. In particular, "NeTEx White Papers", available under the website's Downloads section, provides a good introduction to how different concepts in public transport can be modeled using NeTEx.
NeTEx is a comprehensive data format intended to describe concepts in public transport data in different ways, and in many cases there will be parts of the specification that are superfluous in relation to the need. In actual implementation, thereforeexceed requirements in actual implementation. Therefore, an extraction of necessary objects, which constitute a so-called NeTEx profile, should be made. Such a profile should be used to specify which parts of the NeTEx format are expected to be exchanged between systems in a given context.
This document describes NeTEx's profile Norway for the exchange of stop and route timetable data between external actors and central systems provided by Entur. Moreover, and this profile has been prepared with the assistance of the NeTEx working group in CEN (Comité européen de normalization, the European Committee for Standardization).
...
To reduce complexity, the profile is divided into several parts:
- Reusable componentsComponents: framework
- Information about stopplacesStopPlaces: stops
- Information about Transport Network Information: network
- Information about timetableTimetable: timetable
- Information about fare Fare and ticketingTicketing: fares
Each section describes data objects that belong to a given functionality. In addition, basic objects reused across the dataset are separated into a "commons" section.
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
References
The Norwegian NeTEx profile is based on the following documents:
...
| Info | ||
|---|---|---|
| ||
|
Within a PublicationDelivery, <dataObjects> > are defined, which consist of a set of Frames are defined, where each . Each frame contains all relevant objects in a single group, and specifies common validity conditions, e.g. validity and version. This mechanism supports incremental updating of individual objects in cases where the relationships between the objects are not altered , and will assist in troubleshooting down to the object- or group level.
PublicationDelivery allows for any number of frames, and the same frame type can be reused multiple times. It is good practice to use as few frames as possible, so that the grouping within the same PublicationDelivery is appropriate (avoid "wrapping" objects into their own frames). Objects that naturally belong together, ie have the same version and validity, must be collected in the same frame.
...
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Generalization
In NeTEx, objects can be place placed at many different levels, in whichever way is most purposeful. In order to avoid redundancy, the Norwegian profile dictates that all descriptions and references should be as high up in the hierarchy as possible.
...
Version control is based on the version attribute (VersionFrame), and should be placed on relevant objects at the highest possible heirarchy.Versjon for profil
Version for profile
When submitting NeTEx XML for stop place information, or time table data, NeTEx version has to be specified in order to instruct the recipient of how to read the data. This is accomplished by stating the profile version of the dataset.
...
| Info |
|---|
Note that when refering to an object with both id and version, the consistency validation of the XML-file will demand the existence of the object refered to (id and version). This also applies when version is defined as "any". When refering to external objects (for example an ID in the national stop place registry), the version attribute must be omitted in order for the XML to be valid. |
When
Stated When stated version attributes in a reference are validated as "ID + VERSION" for existing objects in the PublicationDelivery. Because XML validation uses string comparison in Schema valdation it is not possible to use version="any" for references to objects with explicit version numbers. If there are several possible versions of the objects defined internally in the file, and a reference to the latest version is desired, a reference without version attributes should be used (just like when referencing external objects).
...
The first column is omitted if the table only contains elements (it is used to separate attributes and elements).
| DataManagedObject < EntityInVersion < Entity | ||||
|---|---|---|---|---|
| Name | Type | Cardinality | Description | |
| attr | responsibilitySetRef | ResponsibilitySetIdType | 1: 1 | Peker til roller og ansvarsområder knyttet til Points to roles and responsibility areas connected to STOP PLACE, BOARDING ZONE eller or ACCESS ZONE |
| elem | keyList | KeyList | 0: 1 | Et sett med nøkkel-verdi par som beskriver tilleggsegenskaper for objektet A set of key-value pairs which describes additional properites for relevant object (LINE, STOP PLACE, BOARDING ZONE, PLANNED STOP POINT osvetc.), og som kan brukes i tredje-parts systemer: billettering, reiseinformasjon osv.and neccesary for third-party systems (eg. ticketing, journey-planning, real-time) |
| elem | Extentions | ExtentionStructure | 0: 1 | Utvidelseselement Extention element for data som ikke er definert av not defined by NeTEx. |
| elem | BrandingRef | BrandingRefStructure | 0: 1 | Referanse til varemerke (f.eksReference to Brand (e.g. Ruter, ATB, osvAtB) |
Use of Enumeration
The profile documents describe the various NeTEx-objects used in Norway, with relevant fields and datatypes. Some datatypes are Enumeration, that is a list of pre-defined values allowed for the field.
...