| Re: [railML3] Mandatory <length> element for <track>s [message #2244 is a reply to message #2241] |
Mon, 02 September 2019 12:05   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Christian,
Am 29.08.2019 um 17:16 schrieb Christian Rößiger:
> [...]
> If the <length> property must actually be mandatory, because it is
> required for the calculation of positions, then it should also be forced
> in the scheme that it is the structural length of the <track>, which
> must also be identical for both directions.
Thank you for your input on this discussion.
I think it is not guaranteed that <length> is always ment to address
physical lengths in each use case. For example, the
RINF/NetworkStatement use case [1] will be more likely to work with
usable lengths only.
So, considering these use case specific modelling issues I assume that
you want to have <length> becoming optional?
@all: what is your opinion on this?
[1] https://wiki.railml.org/index.php?title=UC:IS:NetworkStateme nt
Best regards
Christian
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
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
