IL:keyLockInState

From railML 3 Wiki
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:keyLockInState of railML® version 3.2
Documentation reference to any key log and its state inside or outside the work zone required for use and/or protection
Subschema interlocking
Parents* localOperationArea,

workZone

Children any (0..*), designator (0..*), givenState (1..1)
Attributes:
  • protectingSide: indication whether the required state is for protection of the area from inside or outside (optional; xs:string)
Possible values:
  • none
  • outside
  • inside,

  • id: unique identifier (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}\})
*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:keyLockInState of railML® version 3.1
Documentation reference to any key log and its state inside or outside the work zone required for use and/or protection
Subschema interlocking
Parents* localOperationArea,

workZone

Children any (0..*), designator (0..1), givenState (1..1)
Attributes:
  • protectingSide: indication whether the required state is for protection of the area from inside or outside (optional; xs:string)
Possible values:
  • none
  • outside
  • inside,

  • 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}\})
*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