Re: railML 2.3 infrastructure extension proposal - locks [message #1941 is a reply to message #1521] |
Fri, 31 August 2018 10:16 |
christian.rahmig
Messages: 436 Registered: January 2016
|
Senior Member |
|
|
Dear all,
Am 03.03.2017 um 15:48 schrieb Christian Rahmig:
> [...]
> thank you very much for your feedback and answers. So, I created a Trac
> ticket for this issue, which can be found in [1]. If you think, that
> there are still some points missing, please let us know.
> [...]
>
> [1] https://trac.railml.org/ticket/305
following our latest telephone discussion on that topic, I adapted the
Trac ticket #305 [1]. For railML 2.4, a very reduced first step solution
of <lock> is planned. A <lock> element shall have a <geoCoord>,
attributes @pos and @absPos and a generic "any" (element and attribute)
anchor fur further specific extensions.
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
|
|
|