| Re: [railML2] extend the elements under <organisationalUnits> with the <designator> element [message #2515 is a reply to message #2485] |
Wed, 19 August 2020 17:28  |
Thomas Nygreen
Messages: 66
Registered: March 2008
|
Member |
|
|
Dear Torben,
The coordinators discussed this topic in our telco on 26 June and I was
given the task to create a Trac ticket and present it in the forum. You
can find the Track ticket at [1], but then I left for the summer and the
forum post was postponed. So I thank you for saving me the work :)
One correction, though: this issue also applies to railML 3, as
<designator> was not applied to organisational units in railML 3.1.
As Christian writes, we also need feedback from the community on whether
we should:
a) Keep the InfrastructureManagers.xml code list as an authoritative
reference for @code in <infrastructureManager> (in addition to <designator>)
b) Stop using the code list for future versions and recommend using
<designator> instead. @code will still exist in 2.5, but will function
like it does on other elements, and no longer be a universal reference.
I prefer b. It saves maintenance, is more consistent with how @code is
used elsewhere, and gives consistency between different types of
organisational units.
[1] https://trac.railml.org/ticket/383
Best regards,
Thomas Nygreen - Common schema coordinator, railML.org
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
