Introduction
Documentation
Syntax
|
|
| Documentation
|
References to track assets controlled by this object controller. Track assets are elements that are derived from TrackAsset, such as levelCrossingIL, linesideElectronicUnitIL, signalIL, trackIL, tvdSection, etc.
|
| Subschema
|
interlocking
|
| Parents*
|
objectController,
signalBox
|
| Children
|
connectedTrackAsset (1..*)
|
Attributes:
- extentOfControl: The level of control of the asset by the interlocking. (optional;
xs:string)
- Possible values:
- fullControl: The control of an element is in both directions, i.e. sending commands and receiving element status
- none: There is no control at all, i.e. the element is static
- notificationOnly: The control of an element allows only for receiving the element status
- steeringOnly: The control of an element allows only for sending commands
|
*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
|
The interlocking carries a list of (references to) track assets that this interlocking controls. The controlled object has an attribute indicating the Level of Control which is most often ‘full control’. Track assets that aren't controlled by the interlocking, e.g. field controlled level crossing or open track elements can be tagged with levelOfControl='none'.
|
| Subschema
|
interlocking
|
| Parents*
|
signalBox
|
| Children
|
connectedTrackAsset (1..*)
|
Attributes:
- extentOfControl: The level of control of the asset by the interlocking. (optional;
xs:string)
- Possible values:
- fullControl: The control of an element is in both directions, i.e. sending commands and receiving element status
- none: There is no control at all, i.e. the element is static
- notificationOnly: The control of an element allows only for receiving the element status
- steeringOnly: The control of an element allows only for sending commands
|
*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
|
The interlocking carries a list of (references to) track assets that this interlocking controls. The controlled object has an attribute indicating the Level of Control which is most often ‘full control’. Track assets that aren't controlled by the interlocking, e.g. field controlled level crossing or open track elements can be tagged with levelOfControl='none'.
|
| Subschema
|
interlocking
|
| Parents*
|
signalBox
|
| Children
|
any (0..*), connectedTrackAsset (1..1), designator (0..1)
|
Attributes:
- extentOfControl: The level of control of the asset by the interlocking. (optional;
xs:string)
- Possible values:
- steeringOnly
- none
- notificationOnly
- fullControl,
- 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 element documentation has been changed.
The parents have been changed.
The children have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues