Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:controller of railML ® version 3.2
|
Documentation
|
Container with reference to connected interlockings and system assets controlled by this operational terminal.
|
Subschema
|
interlocking
|
Parents*
|
controllers
|
Children
|
belongsToInfrastructureManager (0..1), belongsToOperationalPoint (0..*), controlledAssets (1..1), designator (0..*), hasCommunicationSettings (0..*), hasName (0..1), routeSequences (0..1)
|
Attributes:
- elementNumber: element number of the asset for internal reference in engineering data (optional;
xs:nonNegativeInteger ),
- model: The model name of the asset from the supplier. (optional;
xs:string ),
- softwareVersion: The specific software version of the asset itself. (optional;
xs:string ),
- id: unique identifier (obligatory;
xs:string ; 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.
|
Autoexport from the XML-Schema for element IL:controller of railML ® version 3.1
|
Documentation
|
Container with reference to connected interlockings and system assets controlled by this operational terminal.
|
Subschema
|
interlocking
|
Parents*
|
controllers
|
Children
|
any (0..*), controlledAssets (1..1), designator (0..1), itineraries (0..1)
|
Attributes:
- 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
The children have changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues