| Description | This element allows describing a loop that is part of the infrastructure. A loop is a device for transmitting information electromagnetically between the infrastructure and the rollingstock without a direct connection between the sender and the receiver. |
| Subschema | infrastructure |
| Parents* | |
| Children** |
name (0..*), isValid (0..*), areaLocation (0..*), linearLocation (0..*), spotLocation (0..*), gmlLocation (0..*), networkLocation (0..*), designator (0..*), typeDesignator (0..*), elementState (0..*), isEuroLoop (0..1) |
Attributes:
| |
| *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. **Notice: To learn, how to interpret multiplicity information like (0..*) go to Class diagram ( | |
IS:loop
Jump to navigation
Jump to search
Introduction
Loop ‒ track mounted device for the transmission of data between track-to-train [1].
Documentation
Syntax
This element does not appear in railML® 3.2 within the IS subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.
This element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. 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.