Introduction
Documentation
Syntax
|
|
| Documentation
|
Activation of the level crossing may be delayed, depending on the aspect of the approach signal, thus, the activation delay timer depends on a) the signal and b) the signal aspect.
|
| Subschema
|
interlocking
|
| Parents*
|
activationCondition
|
| Children
|
refersToIndicator (0..*), refersToSignal (1..1), showsAspect (1..*)
|
Attributes:
- delay: Delay between signal aspect detection and level crossing activation. This delay depends on the signalled speed of the approaching train hence on signal aspect. (obligatory;
xs:duration),
- isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional;
xs:boolean)
|
*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
|
Activation of the level crossing may be delayed, depending on the aspect of the approach signal, thus, the activation delay timer depends on a) the signal and b) the signal aspect.
|
| Subschema
|
interlocking
|
| Parents*
|
activationCondition
|
| Children
|
refersToSignal (1..1), showsAspect (1..*)
|
Attributes:
- delay: Delay between signal aspect detection and level crossing activation. This delay depends on the signalled speed of the approaching train hence on signal aspect. (obligatory;
xs:duration),
- isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional;
xs:boolean)
|
*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
|
Activation of the level crossing may be delayed, depending on the aspect of the approach signal, thus, the activation delay timer depends on a) the signal and b) the signal aspect.
|
| Subschema
|
interlocking
|
| Parents*
|
activationCondition
|
| Children
|
any (0..*), designator (0..1), refersToSignal (1..1), showsAspect (1..*)
|
Attributes:
- delay: Delay between signal aspect detection and level crossing activation. This delay depends on the signalled speed of the approaching train hence on signal aspect. (obligatory;
xs:duration),
- isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional;
xs:boolean),
- id: unique identifier (optional;
xs:ID; 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.
|
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.
The parents have been changed.
The children have been changed.
The attributes have been changed.
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 parents have been changed.
The children have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues