CO:organizationalUnits: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
Line 4: Line 4:
|parent = {{CO:Tag|metadata}}
|parent = {{CO:Tag|metadata}}


|childs = {{CO:Tag|infrastructureManager|organizationalUnits}}, {{CO:Tag|vehicleManufacturer}}, {{CO:Tag|vehicleOperator}}, {{tag|co|vehicleOwner}}, {{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}}, {{tag|co|vehicleOwner}} {{intro|2.5}}, {{CO:Tag|customer}}, {{CO:Tag|railwayUndertaking}}, {{CO:Tag|operationalUndertaking}}, {{CO:Tag|concessionaire}}, {{CO:Tag|contractor}}
|minocc=0
|minocc=0
|semantics = {{Intro|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{{synonym|organisationalUnits}} will be referred from within the {rml} file in the {{CO:Tag|organizationalUnits}} element.
|semantics = {{Intro|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{{synonym|organisationalUnits}} will be referred from within the {rml} file in the {{CO:Tag|organizationalUnits}} element.

Revision as of 13:51, 23 May 2022


organizationalUnits
 


Schema description / Schemenbeschreibung

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

Multiplicity / Anzahl

[0..1]

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 {rml} 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

None.

Notes / Anmerkungen

None.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.