TT:vehicleRostering

Documentation

Syntax

3.33.23.1

Autoexport from the XML-Schema for element TT:vehicleRostering of railML® version 3.3      UML-visualization of TT
Description	sequence of train runs or tasks (maintenance, refueling, etc.), which a formation of vehicles has to perform
Subschema	timetable
Parents*	vehicleRosterings
Children**	name (0..*), blocks (1..1), blockConnections (0..1)
Attributes: depotRef: Allows referencing the associated depot of the enclosing vehicle rostering. The reference endpoint is expected to be an infrastructure OP (optional: tRef : xs:IDREF), formationRef: Allows referencing a formation of rollingstock in order to associate the enclosing vehicle rostering with the vehicles assigned to the referenced formation (optional: tRef : xs:IDREF), id: the file-internal ID of the object (obligatory: tID : 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. **Notice: To learn, how to interpret multiplicity information like (0..*) go to The W3C Recommendation on XML Schema

This element does not appear in railML^® 3.2 within the TT subschema. It is available only in railML^® 3.3. Do not hesitate to contact railML.org e.V. for further questions.

This element does not appear in railML^® 3.1 within the TT subschema. It is available only in railML^® 3.3. Do not hesitate to contact railML.org e.V. for further questions.

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.
Introduced with version 3.3.