IL:distantAspect

From railML 3 Wiki
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:distantAspect of railML® version 3.2
Documentation The combination of the master's distant signal (within the route or its start) and the aspect it is showing. This is also used for any repeater.
Subschema interlocking
Parents* aspectRelation
Children refersToSignal (1..1), showsAspect (1..*)
Attributes:
  • isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional; xs:boolean)
*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:distantAspect of railML® version 3.1
Documentation The combination of the master's distant signal (within the route or its start) and the aspect it is showing. This includes also any repeaters.
Subschema interlocking
Parents* aspectRelation
Children any (0..*), designator (0..1), refersToSignal (1..1), showsAspect (1..*)
Attributes:
  • isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional; xs:boolean),

  • 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 element documentation has been changed.

The children have changed.

The attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues