IL:hasPositionRestriction

From railML 3 Wiki
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:hasPositionRestriction of railML® version 3.2
Documentation It defines the position the related element shall have when the switch is to be switched in the given position.
Subschema interlocking
Parents* switchIL
Children any (0..*), designator (0..*), relatedDerailerInPosition (0..1), relatedSwitchInPosition (0..1)
Attributes:
  • restrictedPosition: This is the position to be set which requires the other element has the named state/position first. (obligatory; xs:string)
Possible values:
  • right
  • left,

  • 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:hasPositionRestriction of railML® version 3.1
Documentation It defines the position the switch shall have in dependency of the position of the related element.
Subschema interlocking
Parents* switchIL
Children any (0..*), designator (0..1), relatedDerailerInPosition (0..1), relatedSwitchInPosition (0..1)
Attributes:
  • restrictedPosition: This is the position which is needed when the other element has the named state/position. (obligatory; xs:string)
Possible values:
  • right
  • left,

  • 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