Introduction
Documentation
Syntax
|
|
| Documentation
|
Indicates that the enclosing operational connection originates from something like a planned overtaking or a crossing.
|
| Subschema
|
timetable
|
| Parents*
|
operationalConnection
|
| Children
|
None
|
Attributes:
- reason: Operational reason that makes the dependency between the feeder and the connector necessary. (optional;
xs:string; patterns: other:w{2,})
- Possible values:
- OccupationCrossing: Two trains travelling in opposite direction meet at the operational point. The connector has to wait for the feeder clearing the line to continue.
- OccupationOvertaking: Two trains traveling in the same direction meet at the operational point. The connector is reaching the operational point first, but has to let the feeder pass.
- Rollingstock: The connector depends on some of or the entire rollingstock of the feeder.
|
*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.2 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
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.
Introduced with version 3.3.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues