This wiki is a work in progress.
NeTEx is a CEN standard protocol describing a data model and an XML schema for the exchange of complex public transport data through XML files.
The NeTEx model is composed of three parts:
The Framework module contains generic and reusable components shared by all NeTEx parts.
Some introductory notes on the workings of the NeTEx schema.
The NeTEx versioning model allows successive versions of data elements to be identified, allowing the fine grained identification of just those elements that have changed, and the auditing of changes.
The VersionFrame mechanism provides a versionable container that allows a coherent set of related elements to be exchanged.
Each state of an object, or a set of objects, is called a Version. Versions of an object may be consecutive or competitive. Consecutive Versions describe the successive states of an object, whilst competitive Versions describe an alternative version to use in particular circumstances (as, say, described by a ValidityCondition).
The Version describes the identifier and purpose of a version state. The actual version state is described by an instance of EntityInVersion. Thus, in a given repository or documents there will be a single instance of each Entity and one or multiple instances of EntityInVersion for that Entity; these will be tied together by a common identifier and differentiated by distinct Version identifiers.
Container elements representing one-to-many relationships may possess the modificationSet attribute, which indicates whether every instance or only the ones that have changed are included:
| Name | Type | Cardinality | Description |
|---|---|---|---|
| modificationSet | ModificationSetEnum | 0:1 | Whether all contained instances or just deltas are present. |