IL:relatedToTunnelGateAndState

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:relatedToTunnelGateAndState of railML® version 3.3
Documentation the tuple of references to the tunnel gate and its state
Subschema interlocking
Parents* requiredTunnelGateState
Children refersToTunnelGate (1..1)
Attributes:
  • inState: The state (blockingClosed/passableOpen) the tunnel gate has. (obligatory; xs:string)
Possible values:
  • blockingClosed: The gate is in a closed position, which blocks the railway traffic through it.
  • passableOpen: The gate is in an open position, which allows the passage of railway traffic through it.
  • unknown: The gate position is not known,

  • isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional; xs:boolean)
*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:relatedToTunnelGateAndState of railML® version 3.2
Documentation the tuple of references to the tunnel gate and its state
Subschema interlocking
Parents* requiredTunnelGateState
Children refersToTunnelGate (1..1)
Attributes:
  • inState: The state (blockingClosed/passableOpen) the tunnel gate has. (obligatory; xs:string)
Possible values:
  • blockingClosed: The gate is in a closed position, which blocks the railway traffic through it.
  • passableOpen: The gate is in an open position, which allows the passage of railway traffic through it.
  • unknown: The gate position is not known,

  • isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional; xs:boolean)
*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 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.


Changes 3.1→3.2

There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.

Introduced with version 3.2.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues