IL:relatedSwitchInPosition

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:relatedSwitchInPosition of railML® version 3.2
Documentation This is the reference and the state/position of the other switch of the relation.
Subschema interlocking
Parents* hasPositionRestriction
Children refersToSwitch (1..1)
Attributes:
  • inPosition: The position the switch is in. (obligatory; xs:string)
Possible values:
  • left: position of a switch for use of left branch
  • right: position of a switch for use of right branch,

  • 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:relatedSwitchInPosition of railML® version 3.1
Documentation This is the reference and the state/position of the other switch of the relation.
Subschema interlocking
Parents* hasPositionRestriction
Children any (0..*), designator (0..1), refersToSwitch (1..1)
Attributes:
  • inPosition: The position the switch is in. (obligatory; xs:string)
Possible values:
  • right
  • left,

  • isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional; xs:boolean),

  • 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