| Re: Signal characteristics (de: Signaleigenschaften) [message #1719 is a reply to message #1717] |
Mon, 12 March 2018 15:23   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Tobias,
Am 12.03.2018 um 13:28 schrieb Tobias Bregulla:
> Hello Christian,
>
> we do not use <signal>@sigSystem in our exports as we find a modelling
> way to have the same meaning by using <signal>@ruleCode. Last week we
> filled some examples for speed signals and signals in the corresponding
> Wiki page (see http://wiki.railml.org/index.php?title=IS:signal) with
> OUR way of modelling. I think that this is far away from being perfect
> but we are expecting a more granular modelling from railML 3.x IS & IL
> work. I expect good results from the communities work in these use cases
> than in railML 2.x.
Thank you for this feedback and for adding these valuable examples in
the wiki!
> By the way, what about:
> - <signal>@maskableRoute,
> - <signal>@maskableATC,
> - <signal>@sight and
> - <signal>@distNearestDangerPoint?
>
> These elements are neither well documented in the Wiki than clear from
> the semantics. It seems that there are also a lot of dependencies to a
> IL scheme which does not exists in railML 2.x for now.
I created a Trac ticket based on your input [1]. If there are no
objections from the railML community, the mentioned attributes are going
to be marked DEPRECATED with railML 2.4.
[1] https://trac.railml.org/ticket/322
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
