IL:routeRelation/3.2

Automatic Schemaexport for Element routeRelation

Autoexport from the XML-Schema for element IL:routeRelation of railML® version 3.2 UML-visualization of IL
Documentation	states the conditions that must be fulfilled for a given signal to be open
Subschema	interlocking
Parents*	routeRelations
Children	belongsToOperationalPoint (0..*), designator (0..*), hasCommand (0..*), hasIndication (0..*), objectName (0..*), requiredCrossingPosition (0..*), requiredDerailerPosition (0..*), requiredDetectorState (0..*), requiredKeyLockState (0..*), requiredLevelCrossingState (0..*), requiredSectionState (0..*), requiredSignalAspect (0..*), requiredSwitchPosition (0..*), requiredTunnelGateState (0..*)
Attributes: elementNumber: element number of the object 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.