IL:hasCommand

From railML 3 Wiki
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:hasCommand of railML® version 3.2
Documentation References to pre-defined operator commands available for this element.
Subschema interlocking
Parents* atpDevice,

basculeBridge, combinedRoute, conflictingRoute, controller, dangerPoint, derailerIL, destinationPoint, endOfTrack, genericDetector, implementsElementGroup, interface, itinerary, keyLockIL, levelCrossingIL, localOperationArea, movableCrossing, overlap, permissionZone, powerSupplyIL, radioBlockCenter, route, routeEntry, routeExit, routeRelation, routeReleaseGroupAhead, routeReleaseGroupRear, routeStatusIndicator, shuntingZone, signalIL, signalIndicator, stationIndicator, switchIL, trackIL, trainNumberField, tunnelGateIL, tvdSection, workZone

Children None
Attributes:
  • entityCode: It is necessary for the coding of command/indication for relay interlockings. Each command/indication is coded of a byte/bit information, but this coding is different for each interlocking instance and therefore also for each infrastructure element instance (optional; xs:string),

  • 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.

This element does not appear in railML®3.1. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues