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: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,})
- Possible values:
- EngineRun
- Goods
- Passenger,
- 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
Introduced with version 3.2.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues