| Re: Include track length information in topology [message #2113 is a reply to message #2107] |
Mon, 21 January 2019 15:34   |
Thomas Nygreen JBD
Messages: 68
Registered: February 2017
|
Member |
|
|
christian.rahmig wrote on Fri, 18 January 2019 15:28
Am 08.01.2019 um 22:37 schrieb Thomas Nygreen:
> [...]
> One concern I have is how to interpret spotLocation/@pos if
> the optional netElement/@length is missing.
one possible solution is to define the rule, that if the optional
attribute <spotLocation>@pos is being used, the other optional attribute
<netElement>@length has to be given.
Alternatively, the attribute <netElement>@length could be declared as
being mandatory.
What do you prefer?
I think there could be (strategic or template) use cases where netElement length is not needed and @intrinsicCoord would still be used. Therefore, I am in favour of keeping <netElement>@length optional and only require it when a <spotLocation>@pos is not used on that <netElement>.
There is also a possible conflict if both @intrinsicCoord and @pos are used and (@intrinsicCoord * <netElement>@length) calculates to something else than @pos. Should there be a rule that only one of the two attributes can be used on the same element, or should they be interpreted differently?
Best regards,
Thomas Nygreen
Railway capacity engineer
Jernbanedirektoratet
|
|
|
|
Members
Search
Help
Login
Home
