Introduction
Documentation
Syntax
|
|
| Documentation
|
The restriction effect is limited to trains that use one of the referenced tracks at the parent operational point. Otherwise, the train is not affected by this restriction area, even if its itinerary contains the exact operational point sequence.
|
| Subschema
|
timetable
|
| Parents*
|
opRef
|
| Children
|
range (0..1)
|
Attributes:
- affectedDirection: Can be used to express that the track reference only applies to a certain direction. (optional;
xs:string)
- Possible values:
- both: Both directions
- mileageFalling: affected direction is with decreasing mileage
- mileageRising: affected direction is with increasing mileage,
- ref: Reference to a track of infrastructure. (obligatory;
xs:IDREF)
|
*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