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..*)

1. The netElement and netRelation objects are the very fundament of the model. Even renaming objects should only be considered for new major versions, and should be done only if there are major reasons for it (or against keeping the old structure).
   
   
2. This suggestion does not only rename, but it changes semantics. Right now we can assume that netRelations connect netElements that are adjacent, so the netRelation itself has no extension, travel time or other dimension. The netElement are the places that have an extension where a train can be. Your suggestion changes this, now there could be an extension between fromElement and toElement. This would break any code that, for example, assumes that there is zero travel time and distance between netElements when traversing a netRelation.