Introduction
Documentation
Syntax
|
|
| Documentation
|
A base itinerary is made up of 1 or more base itinerary points.
Instinctively one would assume that at least 2 base itinerary points would be required, however for modeling stabling of trains at a track only a single point is needed and the requirement for a second one would actually be a problem.
When describing a movement from one place to another however at least 2 base itinerary points are needed.
Each such base itinerary point represents a stop or passthrough at an operational point along the route.
|
| Subschema
|
timetable
|
| Parents*
|
baseItinerary
|
| Children
|
followupSections (0..1), pass (1..1), stop (1..1), trackRef (0..*)
|
Attributes:
- locationRef: Provides a reference to an operational point that is defined in the infrastructure. (obligatory;
xs:IDREF),
- sequenceNumber: Used to define the ascending ordering of the baseItineraryPoints within their baseItinerary. (obligatory;
xs:unsignedInt),
- 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 base itinerary is made up of 1 or more base itinerary points.
Instinctively one would assume that at least 2 base itinerary points would be required, however for modeling stabling of trains at a track only a single point is needed and the requirement for a second one would actually be a problem.
When describing a movement from one place to another however at least 2 base itinerary points are needed.
Each such base itinerary point represents a stop or passthrough at an operational point along the route.
|
| Subschema
|
timetable
|
| Parents*
|
baseItinerary
|
| Children
|
followupSections (0..1), pass (1..1), stop (1..1), times (0..*), trackRef (0..*)
|
Attributes:
- locationRef: Provides a reference to an operational point that is defined in the infrastructure. (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}}),
- 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