CO:organizationalUnits: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(New element docu for 'organizationalUnits')
 
No edit summary
Line 1: Line 1:
{{InheritOrganizationalUnits
{{ElementDocu|
|parentLink = {{CO:Tag|metadata}}
elementName = organizationalUnits
|selfLink = {{CO:Tag|organizationalUnits}}
 
|ns = CO
|parent = {{CO:Tag|metadata}}
|semantics =
 
|semantics_de =
|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}}
|constraints =
 
|constraints_de =
|semantics = {{Intro|2.2}} Container element for pre-defining organizational units, that will be referred from within the railML file.
{{AddAnn|| }}
 
|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|| }}
 
|notes = {{Ann|None.}} {{Deu|<br> }}
 
|example = {{Ann|None.}}
}}
}}

Revision as of 18:26, 26 February 2017


organizationalUnits
 


Scheme description / Schemenbeschreibung

Position of organizationalUnits in the XML-Tree / Position von organizationalUnits im XML-Baum

Multiplicity / Anzahl

[1..1]

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.