Home » railML newsgroups » railml.common » Suggested refined definitions and extension to organizationalUnits (CO:organizationalUnits)
Re: Suggested refined definitions and extension to organizationalUnits [message #2329 is a reply to message #2325] Thu, 13 February 2020 13:49 Go to previous messageGo to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 66
Registered: March 2008
Member
Dear Torben,
Dear all,

I don't know why Torben's link did not become clickable, so I'll try to post it again, as well as the related trac issue:
Forum: https://www.railml.org/forum/index.php?t=msg&goto=1102
Trac: https://trac.railml.org/ticket/178

I have not found any further context, and in the old forum thread a "vehicleOwner" value was also suggested, but it was apparently not included at the end. Are there anyone in the community who can provide (best practice) examples of current usage? Would Torben's suggestions break any current functionality?

In addition to Torben's suggested changes, I would as if we really need both <railwayUndertaking>, <vehicleOperator> and <operationalUndertaking>. I propose to also deprecate at least one of the last two. Again, please comment!

Best,
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: Thu Mar 28 23:13:48 CET 2024