TT:commercialTrainReference

Documentation

Syntax

Autoexport from the XML-Schema for element TT:commercialTrainReference of railML® version 3.2 UML-visualization of TT
Documentation	Reference to a commercial train variant as the feeder of the connection.
Subschema	timetable
Parents*	connector, feeder
Children	None
Attributes: bipRef: Specifies the base itinerary point of the commercial train variant referenced by the attribute @trainVariantRef at which the connection takes place. (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}}), trainValidityRef: Allows referencing a validity that specifies when this connection can take place. The validity here is to be understood as the validity of the train itself. Example: If a train arrives at the base itinerary point referenced here on the second day of its travel (dayoffset = 1) and the day for which we would want to check if the connection takes place is the 1st of January, we would need to check in the validity specified here if the bit for 31st of December of the previous year is set. If the other part of the connection is also represented by a CommercialTrainReference, the same operation needs to be performed for the other part in case a trainValidityRef is specified there. (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}}), trainVariantRef: Reference to the commercial train variant. (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}})
*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.