From railML 3 Wiki




Autoexport from the XML-Schema for element TT:timetableScenario of railML® version 3.2
Documentation A timetable scenario is an abstract entity used to group validities and in turn trains. By itself it only provides a name. It can be used to exchange parallel timetabling ideas at an early stage of planning or indicate later on the conceptual origin of trains.
Subschema timetable
Parents* timetableScenarios
Children name (0..*), timePeriodRef (0..*)
  • 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}\})
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. 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