CO:organizationalUnits: Difference between revisions
| [checked revision] | [checked revision] |
No edit summary |
(multiple use) |
||
| Line 4: | Line 4: | ||
|parent = {{CO:Tag|metadata}} | |parent = {{CO:Tag|metadata}} | ||
|childs = {{CO:Tag|infrastructureManager}}, {{CO:Tag|vehicleManufacturer}}, {{CO:Tag|vehicleOperator}}, {{CO:Tag|customer}}, {{CO:Tag|railwayUndertaking}}, {{CO:Tag|operationalUndertaking}}, {{CO:Tag|concessionaire}}, {{CO:Tag|contractor}} | |childs = {{CO:Tag|infrastructureManager|organizationalUnits}}, {{CO:Tag|vehicleManufacturer}}, {{CO:Tag|vehicleOperator}}, {{CO:Tag|customer}}, {{CO:Tag|railwayUndertaking}}, {{CO:Tag|operationalUndertaking}}, {{CO:Tag|concessionaire}}, {{CO:Tag|contractor}} | ||
|semantics = {{Intro|2.2}} Container element for pre-defining organizational units, that will be referred from within the railML file. | |semantics = {{Intro|2.2}} Container element for pre-defining organizational units, that will be referred from within the railML file. | ||
Revision as of 15:55, 15 February 2018
organizationalUnits
Schema description / Schemenbeschreibung
Position of organizationalUnits in the XML-Tree / Position von organizationalUnits im XML-Baum
- Parent: <metadata>
- Children: <infrastructureManager>, <vehicleManufacturer>, <vehicleOperator>, <customer>, <railwayUndertaking>, <operationalUndertaking>, <concessionaire>, <contractor>
Multiplicity / Anzahl
Semantics / Bedeutung
(introduced with version 2.2) Container element for pre-defining organizational units, that will be referred from within the railML file.
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
None.
Notes / Anmerkungen
None.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.