IL:reasonForConflict

From railML 3 Wiki
Revision as of 18:50, 19 December 2019 by RailML Coord Documentation (talk | contribs) (Created page with "{{subst:docBase |element=reasonForConflict |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:reasonForConflict of railML® version 3.2
Documentation Description of the reason for the conflict.
Subschema interlocking
Parents* conflictingRoute
Children None
Attributes:
  • origin: The type of route conflict. (obligatory; xs:string; patterns: other:w{2,})
Possible values:
  • conflictingHeadProtection: This value is used in case any signal that shall provide flank/head protection to either route is used as route destination for the other route, which is excluded to be simultaneously.
  • conflictingOverlap: This value is set in case of the overlap of either route causes the conflict.
  • conflictingStatus: This value is used in case the status of any element like logical device or signal is not in accordance with the needs of the route because of the conflicting route.
  • conflictingSwitchPosition: This value is used in case any movable element, not only switches, required by the route needs another position then the conflicting route.
  • overlappingTVDsection: This value is used in case of any TVD section of the route is also used by the conflicting one.,

  • refersTo: The reference to the track asset (movable element, TVD section or signal) causing the conflict. (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 IL:reasonForConflict of railML® version 3.1
Documentation Description of the reason for the conflict.
Subschema interlocking
Parents* conflictingRoute
Children any (0..*), designator (0..1)
Attributes:
  • origin: The type of route conflict. (obligatory; xs:string; patterns: other:w{2,})
Possible values:
  • overlappingTVDsection
  • conflictingSwitchPosition
  • conflictingStatus
  • conflictingOverlap
  • conflictingHeadProtection,

  • refersTo: The reference to the track asset (movable element, TVD section or signal) causing the conflict. (obligatory; 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}}),

  • 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