Template:InheritOrganizationalUnits: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
m (version tag added) |
m (contraints about child element order added) |
||
| Line 11: | Line 11: | ||
|inheritedAttributes = | |inheritedAttributes = | ||
|constraints = | |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|{{{constraints|}}}|{{{constraints_de|}}} }} | {{AddAnn|{{{constraints|}}}|{{{constraints_de|}}} }} | ||
Revision as of 14:11, 16 January 2014
organizationalUnits
Scheme description / Schemenbeschreibung
Position of organizationalUnits in the XML-Tree / Position von organizationalUnits im XML-Baum
- Parent: FIXME
- Children: {{{{{ns}}}:Tag|infrastructureManager}}, {{{{{ns}}}:Tag|vehicleManufacturer}}, {{{{{ns}}}:Tag|vehicleOperator}}, {{{{{ns}}}:Tag|customer}}, {{{{{ns}}}:Tag|railwayUndertaking}}, {{{{{ns}}}:Tag|operationalUndertaking}}, {{{{{ns}}}:Tag|concessionaire}}, {{{{{ns}}}:Tag|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
Not yet described. / Noch nicht beschrieben.
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.