IL:requiredDerailerPosition

Introduction

🗒️ Please, recognize our outline on state space.

Documentation

Syntax

3.33.23.1

Autoexport from the XML-Schema for element IL:requiredDerailerPosition of railML® version 3.3      UML-visualization of IL
Description	References to a particular derailer and its required position to fulfil the route relation
Subschema	interlocking
Parents*	routeRelation
Children	relatedDerailerAndPosition (1..1)
Attributes: isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional: xs:boolean : xs:boolean), mustOrShould: level of enforcement (optional: tMustOrShould : xs:string) Possible values: must: flag, that the given state of an element is mandatory none: flag, that the given state of an element is neither “must” nor “should” should: flag, that the given state of an element is desired but not mandatory, proving: The way the state is proven. (optional: tProving : xs:string) Possible values: continuously: the status/position of a related element is continuously checked oneOff: the status/position of a related element is only checked at the beginning staffAcknowledged: the status/position of a related element is only checked by staff without any technical support
*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:requiredDerailerPosition of railML® version 3.2      UML-visualization of IL
Description	References to a particular derailer and its required position to fulfil the route relation
Subschema	interlocking
Parents*	routeRelation
Children	relatedDerailerAndPosition (1..1)
Attributes: isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional: xs:boolean : xs:boolean), mustOrShould: level of enforcement (optional: tMustOrShould : xs:string) Possible values: must: flag, that the given state of an element is mandatory none: flag, that the given state of an element is neither “must” nor “should” should: flag, that the given state of an element is desired but not mandatory, proving: The way the state is proven. (optional: tProving : xs:string) Possible values: continuously: the status/position of a related element is continuously checked oneOff: the status/position of a related element is only checked at the beginning staffAcknowledged: the status/position of a related element is only checked by staff without any technical support
*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:requiredDerailerPosition of railML® version 3.1      UML-visualization of IL
Description	References to a particular derailer and its required position to fulfil the route relation
Subschema	interlocking
Parents*	routeRelation
Children	designator (0..1), relatedDerailerAndPosition (1..1), any (0..*)
Attributes: mustOrShould: level of enforcement (optional: tMustOrShould : xs:string) Possible values: none should must, proving: The way the state is proven. (optional: tProving : xs:string) Possible values: staffAcknowledged continuously oneOff, isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional: xs:boolean : xs:boolean), id: unique identifier (optional: tID : 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

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

The children have been changed.

The attributes have been changed.