All six parts covered by NeTEx use the same framework of reusable components, versioning mechanisms, validity conditions, global identification mechanisms, etc., defined in a NeTEx framework in Part 1. NeTEx also includes, container elements called “version frames” to group data into coherent sets for efficient exchange.

NeTEx schema can thus be used to exchange:

• Public Transport schedules including stops, routes, departures times / frequencies, operational notes, and map coordinates.
• Routes with complex topologies such as circular routes, cloverleaf and lollipops, and complex workings such as short working and express patterns. Connections with other services can also be described
• The days on which the services run, including availability on public holidays and other exceptions.
• Composite journeys such as train journeys that merge or split trains
• Information about the Operators providing the service.
• Additional operational information, including positioning runs, garages, layovers, duty crews, useful for AVL and on-board ticketing systems.
• Data about the Accessibility of services to passengers with restricted mobility.
• Data is versioned with management metadata allowing updates across distributed systems
• Fare structures, (flat fares, point to point fares, zonal fares)
• Fare products (single tickets, return tickets, day, and season passes, etc.)
• Fare prices that apply at specific dates