Home » railML newsgroups » railml.common » [railML3] Refactoring of OrganizationalUnits
[railML3] Refactoring of OrganizationalUnits [message #2979] Mon, 28 March 2022 15:38
Milan Wölke is currently offline  Milan Wölke
Messages: 142
Registered: April 2007
Senior Member
Hi all,

the ITMS use case working group asked me to write this forum post to inform the community about the intended changes regarding organizational units.

In railML 3.1 organizational units have been defined in the same fashion as in railML 2.x. That means that an organizational unit always was defined in a singular role.

<common><organizationalUnits>
  <vehicleOperator id="operator1" code="SomeRail">...</vehicleOperator>
  <vehicleOperator id="operator2" code="SomeOtherRail">...</vehicleOperator>
  <vehicleOwner id="owner1" code="SomeRail">...</vehicleOwner>
</organizationalUnits></common>

As a consequence organizationalUnits that were operating in multiple roles needed to be matched.

The new model in railML3 allows specifying an organizationalUnit and then assigning it multiple roles. Like this it is far easier to identify organizationalUnits that are referenced in multiple roles.

<common><organizationalUnits>
  <organizationalUnit id="ou1" code="SomeRail">
    ...
    <isVehicleOperator/>
    <isVehicleOwner/>
  </organizationalUnit>
  <organizationalUnit id="ou2" code="SomeOtherRail">
    ...
    <isVehicleOperator/>
  </organizationalUnit>
</organizationalUnits></common>

This should make dealing with organizationalUnits more flexible and easier to use. Please let us know what you think.

Best regards, Milan


Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML3] status and life cycle (Common)
Next Topic: [railML3] Extension methods
Goto Forum:
  


Current Time: Fri Jun 14 14:40:39 CEST 2024