Introduction
Documentation
Syntax
|
|
| Documentation
|
Used to provide information about the used rolling stock.
|
| Subschema
|
timetable
|
| Parents*
|
operationalTrainSectionPart
|
| Children
|
freightFacilities (0..1), passengerFacilities (0..1)
|
Attributes:
- formationRef: Reference to the actual formation planned to be used for the enclosing operational train section part. (optional;
xs:IDREF),
- length: Length used during timetable planning. The value provided here is usually larger or equal to the length indicated by the formation. (optional;
xs:decimal),
- maxSpeed: This attribute allows specifying a maximum speed applied for the enclosing operational train section part. This maximum speed is expected to be lower than the speed implied by the infrastructure and the referenced rollingstock. Typically this is provided for survey runs or maintenance runs. (optional;
xs:decimal),
- orientationReversed: Allows to specify that the referenced formation is actually in reversed order. This flag does not indicate that the train was reversed at the beginning of the enclosing operational train section part. This would be encoded using an appropriate stop activity. It also needs to be noted that this flag does not make sense to be used without providing a reference to a formation in the first place. It is meant as a shortcut to avoid providing each formation in forward and reverse order in the rolling stock sub schema. If not specified the it is assumed that the orientation is not reversed. (optional;
xs:boolean),
- timetableLoad: Specifies the additional load to be considered when calculating run times for the enclosing operational train section part. The value given here is to be added to the tare weight for the calculation of runtimes. (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
|
Used to provide information about the used rolling stock.
|
| Subschema
|
timetable
|
| Parents*
|
operationalTrainSectionPart
|
| Children
|
freightFacilities (0..1), passengerFacilities (0..1)
|
Attributes:
- formationRef: Reference to the actual formation planned to be used for the enclosing operational train section part. (optional;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),
- orientationReversed: Allows to specify that the referenced formation is actually in reversed order. This flag does not indicate that the train was reversed at the beginning of the enclosing operational train section part. This would be encoded using an appropriate stop activity. It also needs to be noted that this flag does not make sense to be used without providing a reference to a formation in the first place. It is meant as a shortcut to avoid providing each formation in forward and reverse order in the rolling stock sub schema. (optional;
xs:boolean)
|
*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