This element does not appear in railML® 3.3 within the CO subschema. It is available only in railML® 3.1, 3.2. Do not hesitate to contact railML.org for further questions.
This element does not appear in railML® 3.3 within the CO subschema. It is available only in railML® 3.1, 3.2. Do not hesitate to contact railML.org for further questions.
Autoexport from the XML-Schema for element CO:infrastructureManager of railML® version 3.2 | |
Documentation | DEPRECATED with railML 3.2; use organizationalUnit instead; The infrastructure manager owns and operates the railway network and related infrastructure. |
Subschema | common |
Parents* | organizationalUnits |
Children | isConcessionaire (0..1), isContractor (0..1), isCustomer (0..1), isInfrastructureManager (0..1), isOperationalUndertaking (0..1), isRailwayUndertaking (0..1), isVehicleManufacturer (0..1), isVehicleOperator (0..1), isVehicleOwner (0..1), name (0..*) |
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. |
Autoexport from the XML-Schema for element CO:infrastructureManager of railML® version 3.1 | |
Documentation | This element is not documented in the schema! |
Subschema | common |
Parents* | organizationalUnits |
Children | name (0..*) |
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. |
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
The element documentation has been changed.
The children have been changed.
The attributes have been changed.
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
Removed with version 3.3.