IL:relatedSectionAndVacancy

Introduction

Autoexport from the XML-Schema for element IL:relatedSectionAndVacancy of railML^® version 3.2 UML-visualization of IL
Documentation	the tuple of references to the TVD section and its state plus the level of enforcement
Subschema	interlocking
Parents^*	requiredSectionState
Children	refersToSection (1..1)
Attributes: inState: The occupation status of the TVD section. (obligatory; `xs:string`) Possible values: occupied: state when the TVD section is occupied by a railway vehicle unknown: vacancy state of the TVD section is not known vacant: state when the TVD section is clear of any railway vehicle, 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:relatedSectionAndVacancy of railML^® version 3.1 UML-visualization of IL
Documentation	the tuple of references to the TVD section and its state plus the level of enforcement
Subschema	interlocking
Parents^*	requiredSectionState
Children	any (0..), designator* (0..1), refersToSection (1..1)
Attributes: inState: The occupation status of the TVD section. (obligatory; `xs:string`) Possible values: unknown vacant occupied, 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.

The children have changed.

The attributes have been changed.