Autoexport from the XML-Schema for element CO:isInfrastructureManager of railML® version 3.3 | |
| Description | owns and operates the railway network and related infrastructure |
| Subschema | common |
| Parents* | |
| Children |
None |
| 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. | |
CO:isInfrastructureManager
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element CO:isInfrastructureManager of railML® version 3.2 | |
| Description | The infrastructure manager owns and operates the railway network and related infrastructure. |
| Subschema | common |
| Parents* |
concessionaire, contractor, customer, infrastructureManager, operationalUndertaking, organizationalUnit, railwayUndertaking, vehicleManufacturer, vehicleOperator |
| Children |
None |
| 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. | |
This element does not appear in railML® 3.1 within the CO subschema. It is available only in railML® 3.2, 3.3. Do not hesitate to contact railML.org e.V. for further questions.
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.
Introduced with version 3.2.
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 element documentation has been changed.
The parents have been changed.
Semantics
Best Practice / Examples
Please refer to <organizationalUnit> for an example.