| Mandatory stops e.g. before a level crossing (was: Obligational stop) [message #1541 is a reply to message #516] |
Wed, 05 April 2017 13:48   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear all,
as there has not been a final solution to the topic, I want to
re-animate the discussion here in the forum:
Am 11.03.2013 um 14:38 schrieb Susanne Wunsch:
> [...]
>
> I summarized the new arguments in the appropriate Trac ticket. [1]
>
> During the last railML conference (2013-03-06) in Berlin the use case
> for "mandatory stop" was questioned.
>
> The described scenario is very specific to the German railway
> operations. In order to avoid country-specific operation rules in the
> context of the more general railML data exchange, the current
> implementation should be removed.
>
> As a short-term solution, the partners may use any-Attributes instead.
>
> An implementation following the idea of an operational stop would be
> preferred to the current implementation as a "speedChange".
>
> Any comments* appreciated.
>
> [1] http://trac.assembla.com/railML/ticket/100#comment:4
> * +1, -1, hints, questions...
>
The main question to be answered:
Shall a mandatory stop e.g in front of a level crossing be modelled
using the current solution with <speedChange>@mandatoryStop [boolean] or
shall we define an operational point there?
I would like to get this topic clarified with the upcoming version 2.4.
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
