Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element TT:trainSketch of railML ® version 3.3 |
| Documentation
|
Used to describe that the block is used for a train operation. That train operation, however, is not yet fully planned and thus is only provided as a sketch with limited operation information.
|
| Subschema
|
timetable
|
| Parents*
|
block
|
| Children
|
identifiers (0..1), itineraryRef (1..1), movementSketch (1..1)
|
Attributes:
- categoryRef: Allows specifying a category for the train sketch. (optional;
xs:IDREF),
- runLength: generic type for length values measured in metres (optional;
xs:decimal),
- 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: 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
|
*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.2 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
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.
Introduced with version 3.3.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues