| Re: Proposal for incorporating length information in RTM NetElement [message #1907 is a reply to message #1868] |
Thu, 16 August 2018 15:24   |
Airy Magnien
Messages: 18
Registered: September 2016
|
Junior Member |
|
|
Mixed feelings here.
Topology does not presume any measure.
Length makes only sense for linear net elements, not PositioningNetElements in general.
In the case of switches (at micro level), where do you place the origin?
In the case of branches (at macro level - figure a double track line), same question.
At meso or macro level for instance, how would you deal with additivity of lengths, (internal paths inside stations may be several, even between the same entry and exit points). Without additivity, lengths are of little use.
The discussion in the infra forum reflects most of the interrogations above, and restricts the "length" attribute to the micro representation, which makes perfect sense. However, given the recursive structure of RTM, it is difficult to introduce that feature without e.g. adding, via OCL, restrictions on where the attribute should be used.
RTM may be extended at will, as foreseen in IRS30100, so you may well add the length attribute to (linear) net elements if you wish to do so. But conceptually, more work is needed for making the model unambiguous while keeping it consistent.
|
|
|
|
Members
Search
Help
Login
Home
