| <state> for complete <infrastructure> [message #1904 is a reply to message #1634] |
Thu, 16 August 2018 14:12  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear all,
Am 01.09.2017 um 14:32 schrieb Christian Rahmig:
> [...]
> Thinking about this top level state information, I assume that it may be
> useful to have the <state> element also available directly under
> <infrastructure>. This would us allow to recognize the difference
> between the different railML files and their included "infrastructure
> scenarios" without having to look in detail into them. So, probably a
> ticket for railML 2.4?
I created the Trac ticket #337 [1] that addresses the issue of having a
<states> element for the root <infrastructure> element. Any comments and
remarks on the proposal are very welcome...
[1] https://trac.railml.org/ticket/337
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
