CO:organizationalUnits: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
No edit summary |
(Einige ''None'') |
||
| Line 8: | Line 8: | ||
|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. | ||
{{AddAnn|| }} | {{AddAnn|| }} | ||
|inheritedAttributes=''None'' | |||
|ownAttributes=''None'' | |||
|constraints = Child elements should occur in the defined order (see XML-Schema). Each child element may be omitted, occur once or as much you like. | |constraints = Child elements should occur in the defined order (see XML-Schema). Each child element may be omitted, occur once or as much you like. | ||
{{AddAnn|| }} | {{AddAnn|| }} | ||
Revision as of 18:27, 26 February 2017
organizationalUnits
Scheme 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.
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.