Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:dangerArea of railML ® version 3.3 |
| Documentation
|
An area that may be activated by a sensor (typically one or more avalanche detectors), resulting in
the trains typically having to run slowly in case of dangerous conditions ahead.
|
| Subschema
|
interlocking
|
| Parents*
|
dangerAreas
|
| Children
|
assetName (0..*), belongsToOperationalPoint (0..1), designator (0..*), detectorInState (0..*), elementState (0..*), hasCommand (0..*), hasIndication (0..*), isLimitedBy (0..*), signalWithAspect (0..*), trackAssetInArea (0..*)
|
Attributes:
- belongsToParent: The reference to another RestrictedArea of the same type used as parent to group them together.
- if some information exists in parent and child, then information in child overwrites it in child
-if some information exists only in parent, then child inherits this information from parent (optional; xs:IDREF),
- elementNumber: element number for internal referencing in the engineering data (optional;
xs:nonNegativeInteger),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID); 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.2 within the IL subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
Introduced with version 3.3.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues