Introduction
Documentation
Syntax
|
|
| Documentation
|
Describes how the train is travelling from this base itinerary point to the next. followupSections listed here are understood as alternatives to one another. They are not to be combined or traversed one after another.
|
| Subschema
|
timetable
|
| Parents*
|
followupSections
|
| Children
|
lineRef (0..1), minimalTime (0..1), reserves (0..1), routeRefs (0..1), trackRefs (0..1)
|
Attributes:
- priority: Specifies the priority of this follow section. The follow up section with the highest priority is the one that is normally chosen. If there is operational conditions that indicate usage of a different route they are considered one after another with rising priority values (that indicate reduced priority). If no priority is specified that follow up section is considered highest priority. This is also reflected in the fact that default value for priority is zero, representing the highest possible priority. (optional;
xs:nonNegativeInteger),
- distance: generic type for length values measured in metres (optional;
xs:decimal)
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this Wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
|
|
| Documentation
|
Describes how the train is travelling from this base itinerary point to the next. followupSections listed here are understood as alternatives to one another. They are not to be combined or traversed one after another.
|
| Subschema
|
timetable
|
| Parents*
|
followupSections
|
| Children
|
lineRef (0..1), minimalTime (0..1), reserves (0..1), routeRefs (0..1), trackRefs (0..1)
|
Attributes:
- priority: Specifies the priority of this follow section. The follow up section with the highest priority is the one that is normally chosen. If there is operational conditions that indicate usage of a different route they are considered one after another with rising priority values (that indicate reduced priority). If no priority is specified the followup section is considered highest priority. (optional;
xs:nonNegativeInteger)
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this Wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.
Changes 3.1→3.2
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
Introduced with version 3.2.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
The parents have been changed.
The children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues