Introduction
Documentation
Syntax
|
|
| Documentation
|
An object controller is a computer device that is used to control track assets in the field.
|
| Subschema
|
interlocking
|
| Parents*
|
objectControllers
|
| Children
|
belongsToInfrastructureManager (0..1), belongsToOperationalPoint (0..*), controlsTrackAsset (0..*), designator (0..*), elementState (0..*), hasCommunicationSettings (0..*), hasName (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: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID); 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.
|
This element does not appear in railML® 3.2 within the IL 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 IL 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