Home » railML newsgroups » railml.interlocking » IL-relevant Signal characteristics
IL-relevant Signal characteristics [message #1831] Mon, 11 June 2018 09:55
christian.rahmig is currently offline  christian.rahmig
Messages: 181
Registered: January 2016
Senior Member
Dear Signalling colleagues,

in railML 2.3 the element <signal> contains a number of parameters that
are unclear in their usage because of missing documentation. When
modelling upcoming railML 2.4 we briefly declared some attributes being
DEPRECATED in order to keep the data model clean. This affected (see [1]):
* @maskableRoute
* @maskableATC
* @sight
* @sigSystem
* @distNearestDangerPoint

This activity already got some feedback in the infrastructure scheme
(see [2]) and has been formulated in Trac ticket #322 (see [3]).

I would like to ask you for two/three things:
(a) Do you currently use any of the above mentioned attributes within
your data exchange interfaces?
(b) If yes, can you please write briefly how you use the attribute(s)?
(c) With respect to railML 3.1: do you see the attributes primarily in
the infrastructure domain or in the signalling/interlocking domain?

[1] https://wiki.railml.org/index.php?title=IS:signal
[2] https://www.railml.org/forum/index.php?t=msg&th=552& start=0&
[3] https://trac.railml.org/ticket/322

Thank you for your help and best regards

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
Previous Topic: Clarification on Itineraries
Next Topic: @code as element name
Goto Forum:

Current Time: Tue Dec 11 06:23:12 CET 2018