Introduction
Documentation
Syntax
|
|
| Documentation
|
A list of sections that the train may take from the OP referenced by this base itinerary point. Usually the section with the highest priority is used, however in case of operational requirement TMS may select among the others usually considering the provided priority values.
The specified followupSections are to be understood as alternatives to one another to traverse the distance between the current base itinerary point and the next. They cannot be combined or traversed one after another.
|
| Subschema
|
timetable
|
| Parents*
|
baseItineraryPoint
|
| Children
|
followupSection (1..*)
|
| Attributes:None
|
*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
|
A list of sections that the train may take from the OP referenced by this base itinerary point. Usually the section with the highest priority is used, however in case of operational requirement TMS may select among the others usually considering the provided priority values.
The specified followupSections are to be understood as alternatives to one another to traverse the distance between the current base itinerary point and the next. They cannot be combined or traversed one after another.
|
| Subschema
|
timetable
|
| Parents*
|
baseItineraryPoint
|
| Children
|
followupSection (1..*)
|
| Attributes:None
|
*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.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues