IL:hasTVDresetStrategy/3.2

Automatic Schemaexport for Element hasTVDresetStrategy

Autoexport from the XML-Schema for element IL:hasTVDresetStrategy of railML® version 3.2 UML-visualization of IL
Documentation	Classification of TVD section reset strategies
Subschema	interlocking
Parents*	usesTypes
Children	designator (0..*)
Attributes: resetStrategy: The classification of the reset strategy. (obligatory; xs:string) Possible values: conditionalReset: The section will only be reset, if some conditions are fulfilled. In case of several variants one can include the condition information in the <designator> of the reset strategy. Such conditions can be that the TVD section must be failed or the last counting action of delimiting detection points was “in”. procedure: This is a placeholder for any other procedure to reset a TVD section. sweepRunWithConfirmation: Here a sweep run is also requested. However, after the notification of the correct occupation and clearance sequence the operator needs to confirm the result by command before the section is reset within the interlocking. sweepRunWithoutConfirmation: Especially for axle counter sections a sweep run (de: Bügelfahrt) can be requested. Although the TVD section reset takes place, with receipt of the operator command to the axle counter unit the interlocking keeps it logically failed until a correct occupation and clearance sequence from a passing train is notified from the axle counter. In this case the section is reset immediately without any further operator action. unconditionalReset: The section will be reset on command without any conditions, i.e. after the reset command was accepted by the interlocking system the TVD section is set to clear/vacant status., id: unique identifier (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}\}); 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.