IL:signalDelayTime

From railML 3 Wiki
Revision as of 17:47, 19 December 2019 by RailML Coord Documentation (talk | contribs) (Created page with "{{subst:docBase |element=signalDelayTime |subschema=IL}}")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:signalDelayTime of railML® version 3.2
Documentation After activation of the level crossing the opening of a signal is delayed.
Subschema interlocking
Parents* activationCondition
Children hasDelayedSignal (1..1)
Attributes:
  • delay: Time during which the signal remains closed. Starts counting when the level crossing is triggered. (obligatory; xs:duration)
*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:signalDelayTime of railML® version 3.1
Documentation After activation of the level crossing the opening of a signal is delayed.
Subschema interlocking
Parents* activationCondition
Children any (0..*), designator (0..1), hasDelayedSignal (1..1)
Attributes:
  • delay: Time during which the signal remains closed. Starts counting when the level crossing is triggered. (obligatory; xs:duration),

  • 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.


Changes 3.1→3.2

The children have changed.

The attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues