Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element TT:successor of railML ® version 3.3 |
| Documentation
|
Allows specifying the successors of the transitions described by this block connection.
|
| Subschema
|
timetable
|
| Parents*
|
blockConnection
|
| Children
|
None
|
Attributes:
- blockRef: Specifies the successor block for the transition from the origin block specified in the parent element. (obligatory;
xs:IDREF),
- cohesionLevel: This attribute allows indicating if the connection between the predecessor and the successor is fixed or not. A fixed connection should not be broken by a subsequent optimization of the rostering. If a connection is indicated as preferred here it may be reorganized in subsequent optimizations. (optional;
xs:string)
- Possible values:
- fixed: A fixed connection shall not be broken up in subsequent optimization runs.
- preferred: A preferred connection may be broken up by subsequent optimizations.,
- dayOffset: The dayOffset refers to the start of the task referenced under <from> with the attribute blockRef. It is always related to the operational times. The dayOffset is independent of any specified preparation or follow-up times.
If no day offset is specified it is assumed to be 0. (optional; xs:unsignedInt; minInclusive: 0; fractionDigits: 0),
- minimumTransitionTime: Minimal transition between the originating block and its successor (optional;
xs:duration),
- validityRef: Describes on which days the connection takes place. (obligatory;
xs:IDREF)
|
*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