(C) 2009-2026 NeTEx, CEN, Crown Copyright

NeTEx is CEN Technical Specification (CEN/TS); it is published as a series referenced as CEN/TS 16614. It is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V6.2 (EN 12896 series) and SIRI (CEN/TS 15531-4/-5 and EN 15531-1/-2/-3) and supports the exchange of information of relevance for passenger information about public transport services and also for running Automated Vehicle Monitoring Systems (AVMS).

Although the data exchanges targeted by NeTEx are predominantly oriented towards provisioning passenger information systems and AVMS with data from public transport scheduling systems, it is not restricted to this purpose. NeTEx can also provide an effective solution to many other use cases for transport data exchange.

Note : Many NeTEx concepts are taken directly from Transmodel. The definitions and explanation of these concepts are extracted directly from the respective standard and reused in NeTEx, sometimes with adaptions in order to fit the NeTEx context.

This repository contains the XML Schemas (XSD) for:

• The core part of NeTEx
• NeTEx Part 1 (Network topology)
• NeTEx Part 2 (Scheduled Timetables)
• NeTEx Part 3 (Fare information)
• NeTEx Part 5 (Alternative modes )

In each branch, we have:

• The folder xsd in which all the XML schemas can be found,
• The folder examples in which all examples can be found,
• At the root folder, Siri.spp which is the project for XMLSpy and Siri.xpr for Oxygen.

The xsd folder is sub-divided as follow:

• gml for all geometry-related elements,
• netex_framlework for all shared components and frames,
• one sub-folder per NeTEx Part (from 1 to 5),
• other complementary sub-folders. At the root of the xsd folder, the file NeTEx_publication.xsd should be used as the main one for production and validation purposes. It includes references to all the other XSD.

All other branches are considered as feature branches, meaning that they are used for development only and are to be deleted once a Pull Request is merged. See below for more details on contributions.

Important notes:

• Any branch marked wip is a non-stable branch.
• For a specific XML Schema matching a published CEN document, use releases.

1. netex_publication.xsd
   • Embeds NeTEx XML model elements in a bulk output file format for use in asynchronous publication.
   • The intended content scope can be indicated by a filter object.
   • It should be used as the main XSD for production and validation purposes.

Note: netex_publication_noConstraint.xsd is the same as netex_publication.xsd but without all the XSD constraints (e.g., unicity of attributes). It is convenient to speed up the work in development phases, but at the price of a much weaker validation.

2. netex_siri.xsd

   • Embeds NeTEx XML model elements in the SIRI protocol for dynamic exchange of elements between servers.
   • Supports both request/response and publish/subscribe.

3. nx.xsd

   • Embeds NeTeX XML model elements within a simple thematic organisation to facilitate browsing and inspection of NeTEx.
   • The NX schema is not intended for actual use.

The schema is systematically divided into small modular files. Generally, for each functional package in the design model there are two XML schema files:

• netex_xxxx_version.xsd: Contains the definitions of each element or group,
• netex_xxxx_suppport.xsd: Contains the data type, reference structures and values for enumerations.

1. Functions

The folder contains snippets of XML files focused on a specific function or element of Public transport services (e.g., timetable, stop places, fares, etc.). They are meant to illustrate how to use NeTEx to model part of the public transport service.

2. Standards

The folder contains more comprehensive NeTEx files that aim to represent either an entire dataset as commonly found in other specifications, domains or Member States. They are meant to illustrate several parts of one public transport service. They should be used as an ensemble rather than single files.

Either for a modelling question or a request for change, please start a discussion using the GitHub issues. In your issue, make sure that:

• The title is a clear summary of your question / requst for change,
• The content sufficiently details:
  • The context,
  • The elements / features you want to discuss,
• If relevant, include extracts of your NeTEx file.

1. Identify which branch you need to target:
   • v2.1-wip for all changes that will apply to NeTEx v2.0 (e.g., bug fixes, typos, improvement of certain features without breaking changes, etc.)
   • v3.0-wip for all changes that will apply when NeTEx migrates to EN (e.g., deprecation of features, refactor of certain elements, breaking changes including new features, etc.)
2. Create a feature branch with a clear name (e.g., bugfix_vehicletype)
3. Work on the changes and do the Pull Request

For new features, the decision between targetting v2.1-wip or v3.0-wip will be made by the group.

Upcoming: templates for Pull Request

Important notes:

• Releases (and their tags) are a snapshot of the corresponding working branch in time.
• For any official reference to a NeTEx version, it is recommended to point to a 2-digit version (e.g., v1.3, v2.0).
• For any development work, it is recommended to use the latest 3-digit version of NeTEx XML Schema.

The comprehensive versions history is available in change_log.md