Home » railML newsgroups » railml.common » Suggested refined definitions and extension to organizationalUnits (CO:organizationalUnits)
Re: Suggested refined definitions and extension to organizationalUnits [message #2601 is a reply to message #2408] Thu, 26 November 2020 06:46 Go to previous messageGo to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 68
Registered: March 2008
Member
Dear all,

We have a new trac ticket for this request: https://trac.railml.org/ticket/435

In addition to adding the <vehicleOwner> elements requested by Norway, it would be natural to add an <owner> child of the rolling stock vehicle <classification> element.

One thing I noted when looking at the current implementation is that the different types of organisational units are very restricted with key/keyref constraints. Specifically, the vehicle operator classification in RS can only reference a vehicleOperator, not a railwayUndertaking. The consequence is that some organisations have to be specified multiple times, one time for each role. This is hard to change without breaking minor version compatibility, so we will have to live with it in railML 2.

Best regards,
Thomas


Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Where to place a "comment" value?
Next Topic: [all versions] Using sequences in XSD schemas
Goto Forum:
  


Current Time: Sun Apr 28 15:39:46 CEST 2024