Skip to content

Home

Jump to bottom
Nicholas Knowles edited this page Aug 12, 2020 · 21 revisions

Welcome to the NeTEx XML Schema wiki!

This Wiki provides advice and information about the NeTEx XML Schema for Public Transport data.

NeTEx (Network Exchange) is a CEN standard for the exchange of Public Transport Information. It is part of the Transmodel ecology of transport standards.

NeTEx is one of the data standards mandated by the European Commission under the ITS directive.

NeTEx XML Schema

NeTEx is provided as a W3C XML schema, defined with .xsd files. The schema can be used both to validate NeTEx conformant XML documents and to automatically build bindings to software tools that use NeTEx data..

  • The NeTex schema is modularised into small W3C .xsd files, each corresponding to a package in the NeTEx UML design Model.
  • The Directory Structure uses folders to organise the packages according to the design model parts.
  • If you wish to browse or edit the NeTEAx Schema we recommend the use of a fully featured XML editor that can integrate the separate subfiles into a visualisation. e A NeTEx conformant XML document must contain a reference to the schema root .xsd file (usually netex_publication.xsd).

NeTEx Release Versions

Historically, NeTEx has used an informal point release system, with major releases indicated by a major number (e.g. v1.0) and interim releases indicated by subnumber e.g. v1.12. CEN documentation Interim releases are mostly small, backwards compatible fixes. The release number is used in the directory structure so that it is possible to host multiple versions on the same computer at the same time.

There is thus a separate set of subdirectories for each release

\GitHub\NeTEx\schema\1.11\...     Jan 2015 Minor corrections to WSDL

\GitHub\NeTEx\schema\1.10\...     August 2018 Version 1 minor changes

\GitHub\NeTEx\schema\1.00\...     August 2018 Version 1

Semantic versioning

From September 2020 the NeTEx schema will follow the more formal Semantic Versioning model, summarised as follows.

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes, (And also to accompany new versions of the CEN Specification).
  • MINOR version when you add functionality in a BackwardsCompatibility manner,
  • PATCH version when you make backwards compatible bug fixes.

NeTEx Wiki Home. CEN NeTEx GITHUB

Clone this wiki locally