IS:signalIS

From railML 3 Wiki
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IS:signalIS of railML® version 3.2
Documentation Schema documentation missing!
Subschema infrastructure
Parents* signalsIS
Children any (0..*), areaLocation (0..*), connectedWithBaliseGroup (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isAnnouncementSignal (0..1), isCatenarySignal (0..1), isDangerSignal (0..1), isEtcsSignal (0..1), isInformationSignal (0..1), isLevelCrossingSignal (0..1), isMilepost (0..1), isSpeedSignal (0..1), isStopPost (0..1), isTrainMovementSignal (0..1), isTrainRadioSignal (0..1), isValid (0..*), isVehicleEquipmentSignal (0..1), linearLocation (0..*), name (0..*), networkLocation (0..*), signalConstruction (0..1), spotLocation (0..*)
Attributes:
  • isSwitchable: set TRUE if the signal is able to show several signal aspects, set FALSE if the signal is a static panel that always shows the same signal aspect (optional; xs:boolean),

  • belongsToParent: reference to the (one and only) parent signal this signal belongs to (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}\}),

  • basedOnTemplate: reference to a generic signal (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}\}),

  • id: the identifier of the object; this can be either of type xs:ID or UUID (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 IS:signalIS of railML® version 3.1
Documentation Schema documentation missing!
Subschema infrastructure
Parents* signalsIS
Children any (0..*), areaLocation (0..*), connectedWithBaliseGroup (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isAnnouncementSignal (0..1), isCatenarySignal (0..1), isDangerSignal (0..1), isEtcsSignal (0..1), isInformationSignal (0..1), isLevelCrossingSignal (0..1), isMilepost (0..1), isSpeedSignal (0..1), isStopPost (0..1), isTrainMovementSignal (0..1), isTrainRadioSignal (0..1), isValid (0..*), isVehicleEquipmentSignal (0..1), linearLocation (0..*), name (0..*), networkLocation (0..*), signalConstruction (0..1), spotLocation (0..*)
Attributes:
  • isSwitchable: set TRUE if the signal is able to show several signal aspects, set FALSE if the signal is a static panel that always shows the same signal aspect (optional; xs:boolean),

  • belongsToParent: reference to the (one and only) parent signal this signal belongs to (optional; 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}\}),

  • basedOnTemplate: reference to a generic signal (optional; 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: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; 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