Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element TT:condition of railML ® version 3.3 |
| Documentation
|
Defines conditions for a train to be affected by the restriction. All elements of each condition are to be interpreted as and-connected.
If multiple conditions are given these are to be interpreted as or-connected.
If no condition is specified the enclosing restriction area affects all passing trains.
|
| Subschema
|
timetable
|
| Parents*
|
temporaryRestrictionArea
|
| Children
|
loadSpecification (0..1)
|
Attributes:
- categoryRef: allows referencing a category from timetable to indicate that the restriction area applies for trains of this category. Note that all other properties of the enclosing condition also need to be evaluated in order to determine which trains are affected. (optional;
xs:IDREF),
- trainType: allows specifying the type of train affected by the temporary restriction area. Note that all other properties of the enclosing condition also need to be evaluated in order to determine which trains are affected. (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