Page Comparison

Content

...

in order to efficiently collect all timetable data from each data provider, ensure consistency of data, and increase data quality. This allows the creation of multimodal information systems which may be used to implement nationwide journey planning solutions and publicize business neutral information to all interested parties.

for travellers

...in order to present relevant, and high-quality journey suggestions.

for public transport operators

...in order to re-use the data in their own journey planning-, ticketing-, and information systems, and offer a better service to their customers.

for third party service providers

...in order to minimize unnecessary costs related to supporting multiple different exchange formats, and to contribute to a continued growth of standardized public transport data exchange.

...

NeTEx is an XML format that facilitates the exchange of 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 modelled 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 exceed requirements in actual implementation. Therefore, an the 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.

...

The information should be delivered with one XML file per Line, packed as ZIP-file with a flat structure (no subdirectories). It is technically possible to deliver each line separately, packed in separate ZIP-files , if all the data objects used by each Line are defined within its PublicationDelivery. However, in order to avoid issues with overwriting and ensure good data update/deletion management, it is strongly recommended that only complete datasets containing all lines are exchanged. Data objects used by multiple Lines can be defined in a separate "common" XML-file (must be prefixed with an underscore, e.g. "_common.xml") to avoid redundancy of unique objects.

...

Within a PublicationDelivery, <dataObjects>  are defined, which consist of a set of Frames. 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, i.e. have the same version and validity, must be collected in the same frame.

...

For example: Operator can be referenced from the individual ServiceJourney in Timetable, but in most cases, a Line will have only one main operator. This should, therefore, be referenced in Line, and any exceptions will instead be overwritten per ServiceJourney (with reference to "additionalOperators" in Line).

...

Version control is based on the version attribute (VersionFrame) , and should be placed on relevant objects as high up in the hierarchy as possible.

...

• NeTEx xsd-version is a numeric value specifying the NeTEx XSD version being used (format X.Y)
• NO-NeTEx-<profilnavn> is the profile name with one of the following values:
  • stops
  • networktimetable
  • fares
• Profil-versjon Profile version is a numeric value specifying the Norwegian NeTEx-profile version being used (format X.Y)

...

When the NeTEx format , or the profile is updated, it will usually be backward compatible. When backward compatibility is not possible, both active versions will be considered valid and supported, until otherwise stated.

...

Individual elements are also versioned, and here it is up to the creator of the dataset to define a versioning system.

• Version The version number must be a positive whole number (integer).
• Version The version number must be increased in such a way that the latest version of the object always has the highest number.

...

Most objects with an ID must also have a version (see Example catalogcatalogue for more details) to ensure all changes lead to an increase of version number.

...

NeTEx allows you to explicitly specify that an object is not versioned by defining the version attribute as "any".

Object An object defined outside the submitted dataset, such as external objects from the national stop place registry will always be the "current" version.

...

...

All objects with a version attribute must have a validity. Validity can be implicitly based on inherited values, or defined explicitly on the object through ValidityConditions. ValidityConditions can be set for a single line , or a set of lines.

This is done in one of the following ways:

• ValidityCondition set explicitly per frame in PublicationDelivery.
• ValdityCondition for a CompositeFrame, which contains all the frames in PublicationDelivery.
  This defines a validity which is inherited by all objects in the dataset , and applies implicitly to all subordinate frames. It is not possible to override ValidityCondition for subordinate frames within a CompositeFrame.
  

...

• codespace
  Codespace represents the owner, creator, or administrator of the data. (see codespaces)
• type 
  Should always be the name of the data type (for example Network, Line, StopPlace, Quay etc.)
• id
  A numeric value, unique for the data type (unique in the context of the first two parts of the ID). Please note that the ID string only allows numbers (0-9), both cases of characters (A-z), dash (-), underscore (_), and the structuring colon (:).

...

When exchanging stop place information (StopPlace, Quay etc.) with the central database, usage of nationally defined ID's is required. This ensures data integrity , and uniformity over time.

...

Just as namespace is used to identify a unique XML Schema, codespace is used in NeTEx to ensure that all elements and attributes in the XML is are unique when combined with other datasets. The central agency (Entur) assigns each data provider a unique codespace, consisting of a three letter code, for example, "KOL" for the provider Kolumbus. Each dataset must have the correct codespace to pass validation.

...

Cardinality is a property which describes the number of instances of XML elements per document, as well as whether the element is required or not, according to the Norwegian NeTEx profile.

• 0: 1 - Optional - None, or a maximum of 1 instances instance allowed.
• 0: * - Optional - None, or a maximum of 1 or more instances allowed.
• 1: 1 - Required - At least one instance is required, but no more than one.
• 1: * - Required - At least one or more instance is required.

...

The first column is omitted if the table only contains elements (it is used to separate attributes and elements).

...

The profile documents describe the various NeTEx-objects used in Norway, with relevant fields and datatypes. Some datatypes data types are Enumeration, that is a list of predefined values allowed for the field.

There are two ways to use Enumeration:

1. Simple Enumeration
   Whem When the datatype is set to xxxEnumeration (for example : FacilitySetEnumeration), it means only one value is allowed:

   Code Block
   language xml
   ... <facilitySet>seatingOnly</facilitySet> ...

   
   

2. List of Enumerations
   When the datatype is set to xxxListOfEnumerations (for example : MealFacilityListOfEnumerations), it means multiple values are allowed for the same element:

   Code Block
   language xml
   ... <mealFacilityList>breakfast dinner drinks</mealFacilityList> ...

   
   

...

Description of all NeTEx terminology used in the profile:

...