| Sequence of infrastructure-subelements [message #2975] |
Thu, 24 March 2022 11:41  |
Dominik Looser
Messages: 18
Registered: March 2020
|
Junior Member |
|
|
The railML3.2 beta versions show a different order of the subelements of <infrastructure> compared to railML 3.1:
railML3.1:
- <topology>
- <geometry>
- <functionalInfrastructure>
- <physicalFacilites>
- <infrastructureVisualizations>
- <infrastructureStates>
railML3.2 beta: (alphabetical order)
- <functionalInfrastructure>
- <genericLocations>
- <geometry>
- <infrastructureStates>
- <physicalFacilites>
- <topology>
There already exist two tickets ([1], [2]) to this topic, where it says that the order should stay the same. One ticket is open, one is closed, but the order is still alphabetical.
Will the order stay the same now or will it be reverted to the railML 3.1 order?
For compatibility reasons we would propose to not change the order of the subelements, especially since the order in 3.1 also makes more sense (defining topology first, then going into details with functional infrastructure elements and then their states).
The same topic exists for subelements of <common> [3] and in railML 3.2 beta3 also top-level <railML> where the order of the subelements has changed. If wished, I will gladly create additional posts in the respective forums.
[1] https://development.railml.org/railml/version3/-/issues/446
[2] https://development.railml.org/railml/version3/-/issues/462
[3] https://development.railml.org/railml/version3/-/issues/464
Thank you in advance for feedback
|
|
|
|
Members
Search
Help
Login
Home
