| Re: [railML3] Interpreting @applicationDirection of <linearLocation> [message #3307 is a reply to message #3302] |
Wed, 04 September 2024 16:45  |
Thomas Nygreen
Messages: 75
Registered: March 2008
|
Member |
|
|
Dear all,
Item 1 in the suggested approach leads to a lot of comparisons when reading a file. Furthermore, it fails as soon as there is a mileage change or change of positioning system between the netElements. Mostly this has little consequence, as one will move on to item 2, but item 1 can incidentally provide the wrong order. Lastly, we need a tiebreaker if item 2 also fails.
I would rather say that the defining <associatedNetElement> is
1) The one with the lowest @sequence number (these should be unique, but if they are not, take the first of the lowest)
2) If no @sequence numbers are specified, the one listed first in the <linearLocation>
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
