IL:refersTo

From railML 3 Wiki
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:refersTo of railML® version 3.2
Documentation reference to track element in functional infrastructure
Subschema interlocking
Parents* activatedBy,

basculeBridge, derailerIL, destinationPoint, endOfTrack, genericDetector, keyLockIL, levelCrossingIL, movableCrossing, routeEntry, routeExit, signalIL, switchIL, trackIL, tunnelGateIL

Children None
Attributes:
  • ref: reference is required because it's the purpose of the element (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}\})
*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:refersTo of railML® version 3.1
Documentation Reference to the physical movable element in the infrastructure.
Subschema interlocking
Parents* activatedBy,

derailerIL, destinationPoint, genericDetector, keyLockIL, levelCrossingIL, movableCrossing, routeEntry, routeExit, signalIL, switchIL

Children None
Attributes:
  • ref: reference is required because it's the purpose of the element (obligatory; xs:IDREF; 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}\})
*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.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues