| Re: [railML3] Suggested extension for operating rules [message #2392 is a reply to message #2352] |
Wed, 11 March 2020 06:34   |
Jörg von Lingen
Messages: 87
Registered: March 2016
|
Member |
|
|
Hi,
the currently discussed operating rules are not a direct characteristic of the infrastructure. They seem to be related
more to the interlocking functions. However, we shall investigate how operators typically collect such rules. Are they
aggregated by station, signal box or other criteria. This would give the hint where to place them.
In the give example of "Hamar stasjon" I would collect them per signal box. Thus making a child list of <signalBox> for
these operational rules.
Regards,
Jörg von Lingen - Interlocking Coordinator
Thomas Nygreen wrote on 26.02.2020 17:11:
> Dear Torben,
> Dear Christian,
>
> The rules that Torben link to concern how the infrastructure
> can be used. As such, they may belong with interlocking (in
> 3.x)?
>
> Unlike the rules in the link, the example that Torben
> provides above, is to me not a rule, but a comment or
> information about a property of the infrastructure. It is
> maybe best handled as some kind of annotation on the signal
> element.
>
> Another example, which is more like a rule is the following
> extract from the page Torben linked to:
>
> Shunting signal R11
>
> The driver of a vehicle shall always report to the local
> dispatcher. Train radio shall be used for the communication.
> If the way is free then permission will be given by shunting
> signal R11 using aspect 44 "Cautious shunting allowed" or
> aspect 45 "Shunting allowed".
>
> I think this could be solved in the way Torben proposes, or
> very similarly by referencing the rule from a route element
> (in 3.x), where it would be a kind of verbal constraint on
> the route.
>
> Best,
> Thomas
>
|
|
|
|
Members
Search
Help
Login
Home
