| RE: [railML3] Refactoring of OrganizationalUnits [message #3310] |
Mon, 05 September 2022 12:02  |
David Lichti
Messages: 20
Registered: December 2020
|
Junior Member |
|
|
During the last TT Dev meeting, we discussed the definition
and difference between a railway undertaking and an
operational undertaking.
Both are exported in our (HaCon, TPS) legacy railML 2.2 and
upcoming railML 2.5 export. The understanding is that the
railway undertaking is the responsible entity for operating
the planned trains. It may delegate the actual operation to
a sub-contractor. In this case, there would be a different
operational undertaking.
Best Regards
David Lichti
|
|
|
|
| Re: RE: [railML3] Refactoring of OrganizationalUnits [message #3316 is a reply to message #3310] |
Fri, 06 September 2024 14:26  |
Thomas Nygreen
Messages: 75
Registered: March 2008
|
Member |
|
|
Dear David,
This is in line with my understanding of these categories. They are currently documented as follows:
isRailwayUndertaking: The undertaking that is commercially responsible for the service
isOperationalUndertaking: The unit that is responsible for the operational planning of this service.
We also have another related category:
isVehicleOperator: Some kind of subcontractor (railway undertaking) that operates the vehicle, if different from the one that is responsible for the commercial service.
How do you suggest that we improve the documentation to clarify it?
Best regards,
Thomas
Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
