| [railML3] XML-IDs for linearLocation and areaLocation [message #3847] |
Wed, 17 December 2025 18:02  |
Milan Wölke
Messages: 213
Registered: April 2007
|
Senior Member |
|
|
Hi all,
in one of our last modelling meetings among the coordinators we discussed the issue of having ids for elements that are not referenced in railML. Most prominent examples would be <linearLocation> and <areaLocation> (<spotLocation> actually is referenced from <mileageChange>, in case you are wondering).
The @id attributes have been added there because:
* the was a formal modelling guideline in earlier versions of railML 3 that mandated that all elements should have an @id attribute not matter if used or not.
* the RTM, the infrastructure is based upon defines ids for these classes.
The modelling guideline seems a bit outdated given that the @ids in question are simple XML-ID which cannot be relied on outside the enclosing XML document.
Regarding RTM, one could argue that the ids should also be removed in the RTM as the id member for these classes that are clearly part of a composition does not serve any purpose.
I am writing you because I am interested in your opinion on the two resulting questions:
* Should this modelling guideline still be followed, or better yet, if so be enforced (would lead to many many @id attribute, all mandatory)?
* How about elements that have an @id element due to their origin in the RTM? Keep the @id? Remove it in railML? Remove it in the RTM as well?
Let us know your view? Do you see any purpose for these @ids? Looking forward to you replies.
Thanks in advance.
Best regards, Milan
Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|
Members
Search
Help
Login
Home
