IL:routeStatusIndicator

From railML 3 Wiki
Revision as of 16:16, 5 March 2021 by RailML Coord Documentation (talk | contribs) (Created page IL:routeStatusIndicator using XSD2MediaWiki Converter 1.0.6)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:routeStatusIndicator of railML® version 3.2
Documentation virtual logical object used for indication of route status on HMI
Subschema interlocking
Parents* routeStatusIndicators
Children designator (0..*), hasCommand (0..*), hasIndication (0..*)
Attributes:
  • positionInRoute: This marks the position of the indicator in the route in case not clear by reference from routeEntry or routeExit. It is related to the functions the indicator will fulfil. (optional; xs:string)
Possible values:
  • end: indicator is located at the end of the route path
  • start: indicator is located at the start of the route path,

  • elementNumber: number of the element in the set of interlocking data (optional; xs:nonNegativeInteger),

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

This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.


Changes 3.1→3.2

Introduced with version 3.2.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues