This document presents Part 2 of the European Technical Specification known as “NeTEx”. NeTEx 

provides a framework for specifying communications and data exchange protocols for organisations 

wishing to exchange scheduled Information relating to public transport operations. As defined by 

Transmodel, 'Public transport' has to be understood as services advertised and available for use by the 

general public carried out by any means of transport.  

This Technical Specification is made up of six parts defining a single European Standard, which 

provides a complete exchange format for public transport networks, timetable description and fare 

information.  

Part 1 is the description of the public transport network topology exchange format. It also contains use 

case shared with part 2, and modelling rules and the description of a framework shared by all parts.  

Part 2 is the description of the scheduled timetables exchange format.  

Part 3 is the description of the fare information exchange format.  

Part 4 is the description of the European passenger information profile.  

Part 5 is the description of the alternative modes exchange format.  

Part 6 is the description of the European passenger information accessibility profile.  

Part 1 is fully standalone, and parts 2, 3, 4, 5 and 6 rely on Part 1 and possibly any previous part..  

The XML schema can be downloaded from http://netex-cen.eu (or directly from 

https://github.com/NeTEx-CEN/NeTEx), along with available guidance on its use, example XML files, 

and case studies of national and local deployments.  

This document is highly technical, and a special care has been taken to keep the text readable. In 

particular a set of formatting conventions is followed that enhances the usual CEN writing rules in 

order to distinguish references to elements of the formal models within text:  

Transmodel terms and NeTEx conceptual model elements are in capital letters (JOURNEY PATTERN 

for example).  

NeTEx physical model names are in bold italic font and use CamelCase style with no spaces 

(JourneyPattern, for example).  

NeTEx physical model attribute types are in italic font and use CamelCase style with no spaces 

(TypeOfEntity, for example).