IL:slaveAspect

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

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:slaveAspect of railML® version 3.2
Documentation The combination of the slave signal (at route entry) and the aspect it is showing.
Subschema interlocking
Parents* aspectRelation
Children any (0..*), designator (0..*), 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: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:slaveAspect of railML® version 3.1
Documentation The combination of the slave signal (at route entry) and the aspect it is showing.
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}\})
*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.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues