Introduction
Documentation
Syntax
|
|
| Documentation
|
The commercial train sections of a commercial train variant provide info about a part of the trains path.
|
| Subschema
|
timetable
|
| Parents*
|
commercialTrainVariant
|
| Children
|
additionalStopInfos (0..1), categoryRefs (0..1), freightFacilities (0..1), isCancelled (0..1), isOnRequest (0..1), passengerFacilities (0..1), range (0..1), transportServiceRef (0..1)
|
Attributes:
- ordererRef: Reference to the organizational unit that ordered the train (optional;
xs:IDREF),
- sequenceNumber: Used to explicitly specify the order of sections within the enclosing commercialTrainVariant by providing ascending sequence numbers. (obligatory;
xs:unsignedInt),
- isEmpty: Trains marked with this flag are running empty and thus can be treated differently when rescheduling and dispatching. (optional;
xs:boolean),
- isPublic: Unless specified otherwise, all trains are considered public.
Non-public trains, their schedules and other details must not be communicated to the open public. (optional; xs:boolean),
- trainType: Allows classification of trains using an extendable enumeration. Mainly used to distinguish between passenger and freight trains. (optional;
xs:string; patterns: other:w{2,}; consider Use of tOtherEnumerationValue too.)
- Possible values:
- EngineRun: Indicates that the train consists of a locomotive only
- Goods: Indicates that the train is a freight train
- Passenger: Indicates that the train is a passenger train,
- id: the identifier of the object (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
|
The commercial train sections of a commercial train variant provide info about a part of the trains path.
|
| Subschema
|
timetable
|
| Parents*
|
commercialTrainVariant
|
| Children
|
additionalStopInfos (0..1), categoryRefs (0..1), freightFacilities (0..1), isCancelled (0..1), isOnRequest (0..1), passengerFacilities (0..1), range (0..1), transportServiceRef (0..1)
|
Attributes:
- ordererRef: Reference to the organizational unit that ordered the train (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}}),
- isEmpty: Trains marked with this flag are running empty and thus can be treated differently when rescheduling and dispatching. (optional;
xs:boolean),
- isPublic: Unless specified otherwise, all trains are considered public.
Non-public trains, their schedules and other details must not be communicated to the open public. (optional; xs:boolean),
- trainType: Allows classification of trains using an extendable enumeration. Mainly used to distinguish between passenger and freight trains. (optional;
xs:string; patterns: other:w{2,}; consider Use of tOtherEnumerationValue too.)
- Possible values:
- EngineRun: Indicates that the train consists of a locomotive only
- Goods: Indicates that the train is a freight train
- Passenger: Indicates that the train is a passenger train,
- 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 e.V. 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 attributes have been changed.
Semantics
Best Practice / Examples
TT:011
The semantic constraint TT:011 is supposed to make sure that the <commercialTrainSection>'s are organized in a way that does not causes inconsistencies, in particular jumps in time or loops.
The semantic constraint in particular means that if the start and end points belong to different <baseItinerary> elements, the <range> elements referencing these <baseItinerary>'s in the <itinerary> must have increasing @sequenceNumber. If both points belong to the same <baseItinerary>, their own @sequenceNumber must increase from start to end, unless the <baseItinerary> consists of only a single <baseItineraryPoint>.
Additional Information
Notes
Open Issues
