| Re: [railML3] transfer times for connections [message #2962 is a reply to message #2950] |
Thu, 17 March 2022 15:24   |
David Lichti
Messages: 13
Registered: December 2020
|
Junior Member |
|
|
I fiddled around with this model and found it quite convincing in its flexibility and coverage. As a result, here are somme suggestions:
- Turn the startOP, and transferOP into attributes of their respective parent elements. At least with the current modelling, this does not change the data structure, but it would be more compact (and feel more natural, too).
- Remove the intermediate transferRelations and transferPoints elements, since they are pure container elements where the respective parent elements connectionTransferTime and transferRelation already seem to be fitting for that role.
- Add an optional platformRef attribute, since the transfer times from/to the two platform edges of the same platform will be identical in almost all cases, effectively halving the amount of text needed for the same data.
- Add a default transfer time for same-platform transfers. While the defaultTransferTime avoids the quadratic number of very similar platform-to-platform times, there still is the linear number of same-platform times, which will often be even more similar.
|
|
|
|
Members
Search
Help
Login
Home
