Introduction
Documentation
Syntax
|
Documentation
|
signal for transmitting a command from traffic control to the train driver by optical means for stopping or proceeding, e.g. main signal, distant signal, signal repeater, shunting signal
|
Subschema
|
infrastructure
|
Parents*
|
signalIS
|
Children
|
None
|
Attributes:
- type: This attribute is not documented in the schema! (optional;
xs:string )
- Possible values:
- distant: this signal indicates the aspect of an upcoming movement signal but gives no movement authority on it own
- main: signal with highest safety level for train movement authority
- repeater: this signal repeats the aspect of a movement signal/the movement authority
- shunting: signal for degraded safety level for train movement (secondary to "main", but with more flexible operations)
|
*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
|
signal for transmitting a command from traffic control to the train driver by optical means for stopping or proceeding, e.g. main signal, distant signal, signal repeater, shunting signal
|
Subschema
|
infrastructure
|
Parents*
|
signalIS
|
Children
|
None
|
Attributes:None
|
*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
|
This element is not documented in the schema!
|
Subschema
|
infrastructure
|
Parents*
|
signalIS
|
Children
|
any (0..*)
|
Attributes:None
|
*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 element documentation has been changed.
The parents have been changed.
The children 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 attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues