Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:loop of railML ® version 3.3 |
| Documentation
|
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*
|
loops
|
| Children
|
areaLocation (0..*), designator (0..*), elementState (0..*), gmlLocation (0..*), isEuroLoop (0..1), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
|
Attributes:
- spreadSpectrumCode: Allows specifying the Q_SSCODE in context of ETCS. If this is some other kind of loop the value is considered to indicate to the receiver which settings to use in order to receive data from the loop. In context of ETCS the expected value range is between 0 and 15 (0..15). (optional;
xs:byte),
- 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 IS 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 IS 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