From railML 3 Wiki
Jump to navigation Jump to search




Autoexport from the XML-Schema for element TT:isCancelled of railML® version 3.2
Documentation Indicates that a train was scheduled to run but has been cancelled. The element may be used to provide additional information about the cancellation, such as the reasoning behind or passenger information references that could be used to inform about it.
Subschema timetable
Parents* commercialTrainSection,

commercialTrainVariant, operationalTrainSection, operationalTrainVariant

Children announcements (0..1), passengerTextInfos (0..1)
  • cancelledByRef: May be used to reference an organizational unit that is responsible for the cancellation. (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}}),

  • reason: May be used to provide a formalized reason for the cancellation. The enumeration used here is inspired by the Taf/Tap Tsi top level interruption reasons and can be extended if necessary. (optional; xs:string; patterns: other:w{2,})
Possible values:
  • CausesOfOtherIM
  • CausesOfOtherRU
  • CivilEngineeringCauses
  • CommercialCauses
  • ExternalCauses
  • InfrastructureInstallations
  • OperationalPlanning
  • Rollingstock
  • SecondaryCauses,

  • reasonDescription: May be used to provide a textual reasoning for the cancellation intended for operating and accounting. (optional; xs:string)
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 for further questions.

Changes 3.1→3.2

Introduced with version 3.2.


Best Practice / Examples

Additional Information


Open Issues