Content
| Table of Contents |
|---|
...
Reusable Components: framework
Information about StopPlaces: stops
Information about Transport Network Information: network
Information about Timetable: timetable
Information about Fares https://enturas.atlassian.net/wiki/spaces/ROR/pages/1638137934
Information about Sales sales (work in progress)
Each section describes data objects that belong to a given functionality. In addition, basic objects reused across the dataset are separated into a "commons" section.
| Gliffy | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Gliffy | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Gliffy | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Overriding of Timetable- and ServiceCalendar related data must be done in a complete TimetabelFrame, and ServiceCalendarFram with an unambiguous ValidityCondition for its subordinate elements.
Conventions
...
Structure of ID's
The ID attribute of NeTEx objects must follow a common pattern, and should be structured in the following way:
...
The first column is omitted if the table only contains elements (it is used to separate attributes and elements).
DataManagedObject < EntityInVersion < Entity | ||||
|---|---|---|---|---|
Name | Type | Cardinality | Description | |
attr | responsibilitySetRef | ResponsibilitySetIdType | 1: 1 | Points to roles and responsibility areas connected to STOP PLACE, BOARDING ZONE or ACCESS ZONE |
elem | keyList | KeyList | 0: 1 | A set of key-value pairs which describes additional properties for the relevant object (LINE, STOP PLACE, BOARDING ZONE, PLANNED STOP POINT etc.), and necessary for third-party systems (eg. ticketing, journey-planning, real-time) |
elem | Extentions | ExtentionStructure | 0: 1 | Extension element for data not defined by NeTEx. |
elem | BrandingRef | BrandingRefStructure | 0: 1 | Reference to Brand (e.g. Ruter, AtB) |
...