Test for collaborative profile documentation
Notes / ideas for structure:
TODO: Check and harnonice towards Transmodel and NeTEx standard for naming
Align structure with Transmodel and NeTEx
- Introduction - Get to know NeTEx, its Terms, common usage and tools (like XSD) provided
- Frames - Deep dive into the NeTEx structure and the basic usage of frames
- Guides - Where can i start? How should i model my data? See no further, these guides will help you a long way
- Reference Data examples - How have others solved the issue with external data sources?
Introduction to NeTEx
NeTEx (CEN TS 16614-1, 16614-2 og 16614-3) is a CEN-standard which defines the data format and description for public transport data exchanges. The standard is based on Transmodel (EN 12896), and the reference model for permanent objects required for access to public transport: IFOPT (Identification of Fixed Objects in Public Transport, EN 28701).
NeTEx supports the exchange of data necessary for stop place information, journey planning, and ticketing, and is divided into three main categories:
- Network Topology (CEN TS 16614-1)
- Scheduled Timetables Plan data (CEN TS 16614-2)
- 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 a general-purpose XML format that facilitates the exchange of complex public transport 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 modelled using NeTEx.
NeTEx is a comprehensive data format intended to describe different concepts for public transport data in various ways. In many cases, there will be parts of the specification that exceed requirements in actual implementation. Therefore, 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.
Profiles
XSD
You can use XSD (XML Schema Definition) to validate XML files by linking the XML document to an XSD schema and running a validation process that checks whether the XML structure, elements, and data types conform to the rules defined in the schema.* ☕ Java: Use SchemaFactory and Validator classes. * 🐍 Python: Use xmlschema.XMLSchema("person.xsd").is_valid("person.xml"). * ⚙️ .NET: Use XmlReaderSettings with XmlSchemaSet.
Click [here](https://github.com/NeTEx-CEN/NeTEx/tree/master/xsd) for the offical and current NeTEx XSD
Standard (NeTEx) vs Profile
Frames are used for logical grouping of different NeTEx concepts:
- 🧩 CompositFrame - Grouping of multiple frames
- 🛠️ ResourceFrame - frame for common objects, i.e. organisations, responsibilities, equipments etc.
- 📍 SiteFrame - frame for information regarding stop places and places of interest.
- 🗺️ ServiceFrame - frame for information regarding networks lines, routes, planned stops etc.
- 📅 ServiceCalendarFrame - frame for defining calendar-information - types of days, operating days, and their relations etc.
- 🕒 TimetableFrame - frame for describing the actual journeys, such as calendar references, departure times, and waiting times etc.prop
- 🚍 VehicleScheduleFrame - frame for vehicle usage planning with vehicle information, equipment and blocks.
- 🛞 DriverScheduleFrame - frame for planning of personnel scheduling
- 🎟️ FareFrame - frame for fare definitions and price information including products and sales offers.
Some useful guides
Guides
Some data may not be contained in the exchanged dataset but provided trough a external source. Here are some implementation examples of referenced data: