| railML3/POMA: Removal of reservedForShuntingOperation [message #3374] |
Thu, 24 October 2024 15:51 |
Milan Wölke
Messages: 150
Registered: April 2007
|
Senior Member |
|
|
Hi all,
in todays timetable developer group meeting we discussed about the flag @reservedForShuntingOperation that could be defined for a restriction area. In particular this flag could be specified if the impact of the restriction was an actual closure of an area. In this case one could use a flag to specify that although normal operation would not be permitted, the area was available and used for shunting.
In the discussion it turned out that this could also be expressed by making the restriction area conditional and specify the types of trains that were not allowed to be operated in the restricted area via <category> references. Additionally shunting trains could also be named as excluded from the restriction using the element //temporaryRestrictions/operations.
Therefore it was decided to remove this flag. I created this post to let the community know about this decision and allow for feedback on this, in case it was something that was really important to someones use case for some reason. In this case please let us know, and help us understand your requirements better.
Thanks in advance.
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
