IL:additionalRelation

Documentation

Syntax

3.33.23.1

Autoexport from the XML-Schema for element IL:additionalRelation of railML® version 3.3      UML-visualization of IL
Description	reference to any additional relation needed for signalling of this route with the addition of functional purpose
Subschema	interlocking
Parents*	overlap, route
Children	None
Attributes: usage: functional purposes of a relation (obligatory: tRelationUsageListExt : xs:string: patterns: other:\w{2,}; consider Use of tOtherEnumerationValue too.) Possible values: asOppositeSignal: the relation marks a signal in opposite direction for the route inFlankProtection: the relation marks a related element as used for flank protection of the route inHeadProtection: the relation marks a related element as used for head protection of the route, i.e. against railway traffic towards the route exit from opposite direction inOverlapProtection: the relation marks a related element as used for protection of the overlap inRunningPath: the relation marks a related element as used for an additional condition of the route, ref: reference is required because it's the purpose of the element (obligatory: tRef : xs:IDREF)
*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:additionalRelation of railML® version 3.2      UML-visualization of IL
Description	reference to any additional relation needed for signalling of this route with the addition of functional purpose
Subschema	interlocking
Parents*	overlap, route
Children	None
Attributes: usage: functional purposes of a relation (obligatory: tRelationUsageListExt : xs:string: patterns: other:\w{2,}; consider Use of tOtherEnumerationValue too.) Possible values: asOppositeSignal: the relation marks a signal in opposite direction for the route inFlankProtection: the relation marks a related element as used for flank protection of the route inHeadProtection: the relation marks a related element as used for head protection of the route, i.e. against railway traffic towards the route exit from opposite direction inOverlapProtection: the relation marks a related element as used for protection of the overlap inRunningPath: the relation marks a related element as used for an additional condition of the route, ref: reference is required because it's the purpose of the element (obligatory: tRef : 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:additionalRelation of railML® version 3.1      UML-visualization of IL
Description	reference to any additional relation needed for signalling of this route
Subschema	interlocking
Parents*	route
Children	None
Attributes: ref: reference is required because it's the purpose of the element (obligatory: tRef : xs:IDREF: 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.

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 element documentation has been changed.

The parents have been changed.

The attributes have been changed.

Changes 3.2→3.3

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

The attributes have been changed.