Introduction
Documentation
Syntax
|
|
| Documentation
|
Operational connection describe a unidirectional relationship between two trains. This could be the transfer of crew from one train to the other or an operational dependency such as a scheduled overtaking at an operational point or waiting for oncoming traffic in a single track section ahead.
|
| Subschema
|
timetable
|
| Parents*
|
operationalConnections
|
| Children
|
connector (1..1), feeder (1..1), isCrewDependency (1..1), isTripDependency (1..1)
|
Attributes:
- minimalTransferTime: The minimalTransferTime is the time which is at least necessary for the passengers or freight that are transferred from the feeder to the connector to traverse the distance between the two trains.
If no minimalTransferTime is specified here the times defined in the connectionTransferTimes at the root level of the timetable subschema apply. (optional; xs:duration)
|
*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® 3.3. Do not hesitate to contact railML.org e.V. for further questions.
This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. 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