Introduction
Documentation
Syntax
|
|
| 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..*)
|
Attributes:
- 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.
|
|
|
| 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..*)
|
Attributes:
- 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. 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.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues