CO:organizationalUnits
organizationalUnits
Schema description / Schemenbeschreibung
Position of organizationalUnits in the XML-Tree / Position von organizationalUnits im XML-Baum
- Parent: <metadata>
- Children: <infrastructureManager>, <vehicleManufacturer>, <vehicleOperator>, <vehicleOwner> (introduced with version 2.5), <customer>, <railwayUndertaking>, <operationalUndertaking>, <concessionaire>, <contractor>
Multiplicity / Anzahl
Semantics / Bedeutung
(introduced with version 2.2) Container element for pre-defining organisations or companies (like infrastructure managers, railway undertakings, vehicle keepers, freight forwarders, ...) taking part in the railway business or operation. These organisational units will be referred from within the railML® file in the <organizationalUnits> element.
Each element may be used several times for several entries, as e.g. a network may be divided into areas with different infrastructure managers, and as within the network there will usually move vehicles from different producers. Every element entry within this container has, at least, an attribute name plus an attribute id. It can be addressed via this id from certain other places within the railML®-file
Attributes of organizationalUnits / Attribute von organizationalUnits
None
Syntactic Constraints / Syntaktische Beschränkungen
Child elements should occur in the defined order (see XML-Schema). Each child element may be omitted, occur once or as much you like.
Best practice & Examples / Empfohlene Anwendung & Beispiele
When compared to the model of actors in the TAF/TAP TSI, the railML® organizational units are mapped as displayed in the following diagram:
| ERA | railML® |
|---|---|
| InfrastructureManager and derived | <infrastructureManager> |
| RailwayUndertaking and derived | <railwayUndertaking> or <operationalUndertaking> |
| TransportCustomer and derived | <customer> |
Notes / Anmerkungen
None.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.