| Re: railML 3.2: Additional information for travel paths in a macroscopic netElement [message #2934 is a reply to message #2919] |
Mon, 07 March 2022 12:09   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear all,
apart from the solution proposed by Thomas and the timetable related approach mentioned by Dirk, I want to suggest a very basic change in the RTM foundation. Currently, a <netRelation> connects two <netElement> objects via child elements <elementA> and <elementB>. Based on discussions related to the driving directions in macroscopic nodes, I propose to adapt the model for enabling connections of more than two <netElement> objects. In particular, the approach foresees:
* renaming elements <elementA> and <elementB> into <fromElement> and <toElement>
* adding new optional, repeatable child element <viaElement> (0..*)
In order to keep topology simple, there should be no further attributes or features added in a <netRelation>. Consequently, the attributes suggested by Thomas in his approach need to be moved somewhere else. Maybe, a combination with the timetable related ideas from Dirk is feasible.
Dear community, what do you think about this proposal? Any feedback is highly appreciated...
Best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
