| Re: Re-factoring of <infraAttributes> [message #1846 is a reply to message #1844] |
Mon, 18 June 2018 14:17   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear all,
another remark about the <infraAttributes>:
Long time ago, we said that <infraAttributes> shall not be used, but
that <*change> elements (e.g. <speedChange>) shall be used instead.
However, <infraAttributes> have some advantages. In particular,
<infraAttributes> can be used to model "global" parameters. This makes
sense e.g. for specifying the track gauge of a whole railway network.
Therefore, we slightly adapted the documentation in the wiki [1] to
conclude: please use <infraAttributes> for global parameters and use
<*change> elements for all changes (and local definitions) of parameters.
Please let us know whether you have a different opinion on that issue or
if you agree with that concept.
[1] https://wiki.railml.org/index.php?title=IS:infraAttributes
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
