TT:commercialScheduling

Documentation

Syntax

Autoexport from the XML-Schema for element TT:commercialScheduling of railML® version 3.3      UML-visualization of TT
Documentation	A commercial scheduling maps an operational train or parts of it to a commercial train or parts of it. The sum of all commercial schedulings encodes which operational trains are used to provide the services described with the commercial trains.
Subschema	timetable
Parents*	commercialSchedulings
Children	operationalRange (1..*)
Attributes: end: Reference to the last base itinerary point of the commercial train section referenced with the attribute @sectionRef that is part of the enclosing commercial scheduling. (optional; xs:IDREF), sectionRef: Reference to the commercial train section that is described with the enclosing commercial scheduling. (obligatory; xs:IDREF), start: Reference to the first base itinerary point of the commercial train section referenced with the attribute @sectionRef that is part of the enclosing commercial scheduling. (optional; xs:IDREF), validityRef: Allows referencing a validity if the commercial scheduling does not apply to the full validity provided for the commercial train variant of the commercial train section referenced by the attribute @sectionRef. (optional; 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.

Autoexport from the XML-Schema for element TT:commercialScheduling of railML® version 3.2      UML-visualization of TT
Documentation	A commercial scheduling maps an operational train or parts of it to a commercial train or parts of it. The sum of all commercial schedulings encodes which operational trains are used to provide the services described with the commercial trains.
Subschema	timetable
Parents*	commercialSchedulings
Children	operationalRange (1..*)
Attributes: end: Reference to the last base itinerary point of the commercial train section referenced with the attribute @sectionRef that is part of the enclosing commercial scheduling. (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}}), sectionRef: Reference to the commercial train section that is described with the enclosing commercial scheduling. (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}}), start: Reference to the first base itinerary point of the commercial train section referenced with the attribute @sectionRef that is part of the enclosing commercial scheduling. (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}}), validityRef: Allows referencing a validity if the commercial scheduling does not apply to the full validity provided for the commercial train variant of the commercial train section referenced by the attribute @sectionRef. (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}}), 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, 3.3. 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.