(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Introduction
Documentation
Syntax
|
|
| Documentation
|
The references to the element groups which are configured for this interlocking
|
| Subschema
|
interlocking
|
| Parents*
|
signalBox
|
| Children
|
assetName (0..*), belongsToOperationalPoint (0..1), designator (0..*), elementState (0..*), groupType (1..1), hasCommand (0..*), hasIndication (0..*), hasStationIndicator (0..1), refersToInfrastructureElement (0..*), refersToMember (0..*)
|
Attributes:
- belongsToParent: The reference to another ElementGroup used as parent for grouping them together.
- if some information exists in parent and child, then information in child overwrites it in child
-if some information exists only in parent, then child inherits this information from parent (optional; xs:IDREF),
- elementNumber: element number for internal referencing in the engineering data (optional;
xs:nonNegativeInteger),
- 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.
|
|
|
| Documentation
|
The references to the element groups which are configured for this interlocking
|
| Subschema
|
interlocking
|
| Parents*
|
signalBox
|
| Children
|
assetName (0..*), belongsToOperationalPoint (0..1), designator (0..*), groupType (1..1), hasCommand (0..*), hasIndication (0..*), hasStationIndicator (0..1), refersToInfrastructureElement (0..*), refersToMember (0..*)
|
Attributes:
- belongsToParent: The reference to another ElementGroup used as parent for grouping them together.
- if some information exists in parent and child, then information in child overwrites it in child
-if some information exists only in parent, then child inherits this information from parent (optional; 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}}),
- elementNumber: element number for internal referencing in the engineering data (optional;
xs:nonNegativeInteger),
- 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.
|
|
|
| Documentation
|
The references to the element groups which are configured for this interlocking
|
| Subschema
|
interlocking
|
| Parents*
|
signalBox
|
| Children
|
any (0..*), designator (0..1), groupType (1..1), refersToMember (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
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
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 children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues