TT:operationalTrainSection

Documentation

Syntax

Autoexport from the XML-Schema for element TT:operationalTrainSection of railML® version 3.2 UML-visualization of TT
Documentation	The operational train sections of an operational train variant provide info about a part of the trains path.
Subschema	timetable
Parents*	operationalTrainVariant
Children	additionalStopInfos (0..1), isCancelled (0..1), isOnRequest (0..1), operationalTrainSectionPart (1..*), range (0..1)
Attributes: operatorRef: Allows referencing the operator of the train (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}\}), slotHolderRef: Allows referencing the organizational unit holding the slot of the train (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}\}), categoryRef: Allows assigning a category to the train. The category refers to all operationalTrainSectionParts running coupled on this section. The referenced category is therefore often assigned by the infrastructureManager. (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}\})
*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. It is available only in railML^® 3.2. Do not hesitate to contact railML.org for further questions.

Changes 3.1→3.2

Introduced with version 3.2

Semantics

Semantic Constraint "TT:004":   The itinerary sections of an <operationalTrainVariant>, defined by the <operationalTrainSection>s and their respective <range>s, that are not <isCancelled> and not marked as <isOnRequest>, must be pairwise disjoint, except for their respective first and last <baseItineraryPoint>s.   Proposed on January 12th 2023 Approved on March 09th 2023 Discuss this semantic constraint Please, recognize our guidelines on semantic constraints

Semantic Constraint "TT:005":   The first(last) <baseItineraryPoint> of each <operationalTrainSection> within an <operationalTrainVariant> must either be the referenced <itinerary>'s first(last) <baseItineraryPoint>, or coincide with another section's last(first) <baseItineraryPoint>.   Proposed on January 12th 2023 Approved on March 09th 2023 Discuss this semantic constraint Please, recognize our guidelines on semantic constraints