IS:trainProtectionElement

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IS:trainProtectionElement of railML^® version 3.2 UML-visualization of IS
Documentation	Allows specifying technical installations to ensure safe operation in the event of human error.
Subschema	infrastructure
Parents^*	trainProtectionElements
Children	areaLocation (0..), designator* (0..), external* (0..), gmlLocations* (0..), isValid* (0..), linearLocation* (0..), name* (0..), networkLocation* (0..), spotLocation* (0..), typeDesignator* (0..*)
Attributes: basedOnTemplate: reference to a template train protection element/system (optional; `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}\}), trainProtectionSystem: definition of the national train protection system, which is installed at the track; use value from the separate codelist file 'TrainProtectionSystems.xml'/trainProtectionSystemsAtTrack (optional; `xs:string`), medium: the medium for transferring the control command from the interlocking unit to the train protection field element, e.g. "inductive" for magnets (optional; `xs:string`) Possible values: cable inductive mechanical radio rail, monitoring: the way how the train protection field element is communicating with the monitoring central interlocking unit (optional; `xs:string`) Possible values: continuous intermittent none, id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; `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 IS:trainProtectionElement of railML^® version 3.1 UML-visualization of IS
Documentation	This element is not documented in the schema!
Subschema	infrastructure
Parents^*	trainProtectionElements
Children	any (0..), areaLocation* (0..), designator* (0..), external* (0..), gmlLocations* (0..), isValid* (0..), linearLocation* (0..), name* (0..), networkLocation* (0..), spotLocation* (0..*)
Attributes: basedOnTemplate: reference to a template train protection element/system (optional; `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}\}), trainProtectionSystem: definition of the national train protection system, which is installed at the track; use value from the separate codelist file 'TrainProtectionSystems.xml'/trainProtectionSystemsAtTrack (obligatory; `xs:string`), medium: the medium for transferring the control command from the interlocking unit to the train protection field element, e.g. "inductive" for magnets (optional; `xs:string`) Possible values: cable rail radio inductive mechanical, monitoring: the way how the train protection field element is communicating with the monitoring central interlocking unit (optional; `xs:string`) Possible values: continuous intermittent none, id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; `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}\})
^*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 element documentation has been changed.

The children have changed.

The attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues