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: 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}}), 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}})
*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

Introduced with version 3.2.

Semantics

Proposed Semantic Constraint "TT:004":   An <operationalTrainVariant> specified the trains path by its itineraryRef. Each <operationalTrainSection> or a <operationalTrainVariant> may specify via its <range> which part of the itinerary it represents. No <operationalTrainSection> shall overlap with another of the same <operationalTrainVariant> except for the baseItineraryPoint that connects it to another <operationalTrainSection>.   Proposed on January 12th 2023 FIXME: add Link to discussion! Please, recognize our guidelines on semantic constraints

Proposed Semantic Constraint "TT:005":   The sum of all <operationalTrainSection>'s of a <operationalTrainVariant> shall cover the full itinerary referenced by the <operationalTrainVariant>'s itineraryRef attribute.   Proposed on January 12th 2023 FIXME: add Link to discussion! Please, recognize our guidelines on semantic constraints