IL:keyLockIL

From railML 3 Wiki
Revision as of 18:48, 19 December 2019 by RailML Coord Documentation (talk | contribs) (Created page with "{{subst:docBase |element=keyLockIL |subschema=IL}}")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:keyLockIL of railML® version 3.2
Documentation A device for locking a key which is released from interlocking or by using a master key.
Subschema interlocking
Parents* keyLocksIL
Children acceptsKey (0..1), assetName (0..*), belongsToOperationalPoint (0..1), designator (0..*), hasCommand (0..*), hasIndication (0..*), hasInterface (0..1), hasSlaveLock (0..*), hasTvdSection (0..1), refersTo (0..1), takesControlOf (0..*)
Attributes:
  • function: The functional element the keylock is controlling. (optional; xs:string; patterns: other:w{2,})
Possible values:
  • handThrownSwitch: The key lock is used to control the position of a manually operated switch within a station
  • sidingProtection: The key lock is used to control the position of a manually operated switch used to enter a siding from the open line.
  • workZone: The key lock is used to control the status of a work zone.,

  • hasAutomaticKeyLock: The key may be automatically relocked when returned into the lock. Thus the key can be used only once. (optional; xs:boolean),

  • hasAutomaticKeyRelease: The key of a siding on open line may be released automatically when the related TVD section (trigger) becomes occupied. (optional; xs:boolean),

  • keyAuthoriseTime: The time period the key release is active after commanded by the operator. Afterwards a not removed key will be automatically relocked again. (optional; xs:duration),

  • keyRequestTime: The time period a request for key release is indicated to the operator. (optional; xs:duration),

  • description: Description of the logic. (optional; xs:string),

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

Autoexport from the XML-Schema for element IL:keyLockIL of railML® version 3.1
Documentation A device for locking a key which is released from interlocking or by using a master key.
Subschema interlocking
Parents* keyLocksIL
Children acceptsKey (0..1), any (0..*), designator (0..1), hasInterface (0..1), hasSlaveLock (0..*), hasTvdSection (0..1), refersTo (0..1), takesControlOf (0..*)
Attributes:
  • hasAutomaticKeyRelease: The key of a siding on open line may be released automatically when the related TVD section (trigger) becomes occupied. (optional; xs:boolean),

  • hasAutomaticKeyLock: The key may be automatically relocked when returned into the lock. Thus the key can be used only once. (optional; xs:boolean),

  • keyRequestTime: The time period a request for key release is indicated to the operator. (optional; xs:duration),

  • keyAuthoriseTime: The time period the key release is active after commanded by the operator. Afterwards a not removed key will be automatically relocked again. (optional; xs:duration),

  • description: Description of the logic. (optional; xs:string),

  • 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

The children have changed.

The attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues