Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:interlocking of railML ® version 3.3 |
| Documentation
|
root element for railML3 interlocking model
|
| Subschema
|
interlocking
|
| Parents*
|
railML
|
| Children
|
assetsForInterlockings (0..1), controllers (0..1), objectControllers (0..1), radioBlockCentres (0..1), signalBoxes (0..1), specificInfrastructureManagers (0..1)
|
| Attributes:None
|
*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:interlocking of railML ® version 3.2 |
| Documentation
|
root element for railML3 interlocking model
|
| Subschema
|
interlocking
|
| Parents*
|
railML
|
| Children
|
assetsForInterlockings (0..1), controllers (0..1), radioBlockCentres (0..1), signalBoxes (0..1), specificInfrastructureManagers (0..1)
|
| Attributes:None
|
*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:interlocking of railML ® version 3.1 |
| Documentation
|
root element for railML3 interlocking model
|
| Subschema
|
interlocking
|
| Parents*
|
railML
|
| Children
|
assetsForIL (0..1), controllers (0..1), signalBoxes (0..1), specificIMs (0..1)
|
| Attributes:None
|
*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.
|
Changes 3.1→3.2
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
The children have been changed.
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.
The children have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues