Introduction
Documentation
Syntax
|
|
| Documentation
|
An operational train variant is a specific variant of a train that is operated in this way on all operating days indicated by the provided validity. It is expected that the validities of all operational train variants within an operational train do not overlap. The difference between one variant and the next of an operational train is that the trains path may differ to some degree.
|
| Subschema
|
timetable
|
| Parents*
|
operationalTrain
|
| Children
|
identifiers (0..1), isCancelled (0..1), isOnRequest (0..1), operationalTrainSection (1..*)
|
Attributes:
- itineraryRef: References the itinerary of the operational train variant. The operational train variant is expected to stop or passthrough all of the OPs specified by the base itinerary points that are referenced by this itinerary. (obligatory;
xs:IDREF),
- offset: Allows to specify a temporal offset to the times provided with the itinerary.
This means that the resulting arrival and departure times of the individual base itinerary points are calculated by adding the offset of the itinerary AND the offset of the operational train variant to them. Of course the offset may also be negative. (optional; xs:duration),
- validityRef: Reference to a validity. This validity specifies if the operational train variant is operated on a certain day, or if it is not. (obligatory;
xs:IDREF),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID); compare: Dev:Identities
|
*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
|
An operational train variant is a specific variant of a train that is operated in this way on all operating days indicated by the provided validity. It is expected that the validities of all operational train variants within an operational train do not overlap. The difference between one variant and the next of an operational train is that the trains path may differ to some degree.
|
| Subschema
|
timetable
|
| Parents*
|
operationalTrain
|
| Children
|
identifiers (0..1), isCancelled (0..1), isOnRequest (0..1), operationalTrainSection (1..*)
|
Attributes:
- itineraryRef: References the itinerary of the operational train variant. The operational train variant is expected to stop or passthrough all of the OPs specified by the base itinerary points that are referenced by this itinerary. (obligatory;
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}}),
- offset: Allows to specify a temporal offset to the times provided with the itinerary.
This means that the resulting arrival and departure times of the individual base itinerary points are calculated by adding the offset of the itinerary AND the offset of the operational train variant to them. Of course the offset may also be negative. (optional; xs:duration),
- validityRef: Reference to a validity. This validity specifies if the operational train variant is operated on a certain day, or if it is not. (obligatory;
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}}),
- id: unique identifier (obligatory;
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}}); compare: Dev:Identities
|
*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
Violation and fixes of semantic constraint TT:002
Violation
Below is an example of the code violating the semantic constraint TT:002. Interpretation of the code given below results in a conflict, because both <operationalTrainVariant>s "ov-1" and "ov-2" run on Monday.
<operationalTrain id="ot-1">
<operationalTrainVariant id="ov-1" itineraryRef="it-1" validityRef="va-2">
<identifiers>
<identifier number="OT1066" type="OperationalTrainNumber"/>
</identifiers>
<operationalTrainSection>
<operationalTrainSectionPart id="os-1">
<formationInformation formationRef="fm-1"/>
</operationalTrainSectionPart>
</operationalTrainSection>
</operationalTrainVariant>
<operationalTrainVariant id="ov-2" itineraryRef="it-1" validityRef="va-2">
<identifiers>
<identifier number="OT1067" type="OperationalTrainNumber"/>
</identifiers>
<operationalTrainSection>
<operationalTrainSectionPart id="os-2">
<formationInformation formationRef="fm-1"/>
</operationalTrainSectionPart>
</operationalTrainSection>
</operationalTrainVariant>
</operationalTrain>
<validity>:
<validity id="va-2">
<operatingDayValidity timetableScenarioRef="ts01" pattern="1111100"/>
</validity>
How to solve this issue? Setting @offset of whatever length to e.g. "os-2" does not fix the conflict as it arises because of 2 or more <operationalTrainVariant>s referring to the same <validity>.
Fix by cancelling
Invalid code above can be fixed by cancelling one the trains by <isCancelled>.
<operationalTrain id="ot-1">
<operationalTrainVariant id="ov-1" itineraryRef="it-1" validityRef="va-2">
<identifiers>
<identifier number="OT1066" type="OperationalTrainNumber"/>
</identifiers>
<operationalTrainSection>
<operationalTrainSectionPart id="os-1">
<formationInformation formationRef="fm-1"/>
</operationalTrainSectionPart>
</operationalTrainSection>
</operationalTrainVariant>
<operationalTrainVariant id="ov-2" itineraryRef="it-1" validityRef="va-2">
<identifiers>
<identifier number="OT1067" type="OperationalTrainNumber"/>
</identifiers>
<isCancelled/>
<operationalTrainSection>
<operationalTrainSectionPart id="os-2">
<formationInformation formationRef="fm-1"/>
</operationalTrainSectionPart>
</operationalTrainSection>
</operationalTrainVariant>
</operationalTrain>
Fix by request of dispatcher
Invalid code above can also be fixed by providing a child <isOnRequest> to "ov-1" or "ov-2" meaning that one of the trains is not cancelled but will not run until further command of dispatcher is given. However, if this command is given, then a new timetable should be produced with no conflicts in it, i.e. no two trains departing from the same track to the same station at the same time. As a result still only one train will go on Monday within this timetable.
<operationalTrain id="ot-1">
<operationalTrainVariant id="ov-1" itineraryRef="it-1" validityRef="va-2">
<identifiers>
<identifier number="OT1066" type="OperationalTrainNumber"/>
</identifiers>
<operationalTrainSection>
<operationalTrainSectionPart id="os-1">
<formationInformation formationRef="fm-1"/>
</operationalTrainSectionPart>
</operationalTrainSection>
</operationalTrainVariant>
<operationalTrainVariant id="ov-2" itineraryRef="it-1" validityRef="va-2">
<identifiers>
<identifier number="OT1067" type="OperationalTrainNumber"/>
</identifiers>
<isOnRequest/>
<operationalTrainSection>
<operationalTrainSectionPart id="os-2">
<formationInformation formationRef="fm-1"/>
</operationalTrainSectionPart>
</operationalTrainSection>
</operationalTrainVariant>
</operationalTrain>
Additional Information
Notes
An <operationalTrainVariant> is specific for a certain day. It shall not be used to describe different alternative train paths of a microscopic infrastructure model [1] a train may go on a certain day, e.g. use track A or B to get from OP 1 to OP 2.
Open Issues
References
