CO:organizationalUnit

Documentation

Syntax

Autoexport from the XML-Schema for element CO:organizationalUnit of railML® version 3.3      UML-visualization of CO
Documentation	Specify the type of organizational unit using its child elements.
Subschema	common
Parents*	organizationalUnits
Children	designator (0..*), isConcessionaire (0..1), isContractor (0..1), isCustomer (0..1), isInfrastructureManager (0..1), isOperationalUndertaking (0..1), isRailwayUndertaking (0..1), isValid (0..1), isVehicleKeeper (0..1), isVehicleManufacturer (0..1), isVehicleOperator (0..1), isVehicleOwner (0..1), name (0..*)
Attributes: code: insert here the matching code from the relevant codelist (optional; xs:string), id: the identifier of the object (obligatory; xs:ID); compare: Dev:Identities
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

Autoexport from the XML-Schema for element CO:organizationalUnit of railML® version 3.2      UML-visualization of CO
Documentation	Specify the type of organizational unit using its child elements.
Subschema	common
Parents*	organizationalUnits
Children	isConcessionaire (0..1), isContractor (0..1), isCustomer (0..1), isInfrastructureManager (0..1), isOperationalUndertaking (0..1), isRailwayUndertaking (0..1), isVehicleManufacturer (0..1), isVehicleOperator (0..1), isVehicleOwner (0..1), name (0..*)
Attributes: code: insert here the matching code from the relevant codelist (optional; xs:string), id: unique identifier (obligatory; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

This element does not appear in railML^® 3.1 within the CO subschema. It is available only in railML^® 3.2, 3.3. Do not hesitate to contact railML.org e.V. for further questions.

Changes 3.1→3.2

There exists an overview of all changes between railML^® 3.1 and railML^® 3.2 on page Dev:Changes/3.2.
Introduced with version 3.2.

Changes 3.2→3.3

There exists an overview of all changes between railML^® 3.2 and railML^® 3.3 on page Dev:Changes/3.3.

The children have been changed.

The attributes have been changed.

Best Practice / Examples

For <organizationalUnit>s that are infrastructure managers (i.e. have the child <isInfrastructureManager>), the attribute @code points to a value in the railML^® codelist InfrastructureManagers.xml where many national and regional infrastructure managers are listed. If you cannot find the infrastructure manager that is of interest to you in the list, please follow our simple procedure to have it added to the codelist.

  <common id="co_01">
    <organizationalUnits>
      <organizationalUnit id="ou_01" code="SZDC">
        <isInfrastructureManager/>
      </organizationalUnit>
    </organizationalUnits>
  </common>