Am 29.05.2018 um 18:45 schrieb Thomas Nygreen:
> In Norway we discussed just a week or two ago if <border>s
> were suitable for specifying shunting areas etc. in
> stations. Would this kind of use be in line with what the
> element is intended for? Two questions we had was how to
> group borders together to actually form an area, and how to
> specify what kind of area it is. The former can be solved by
> using a common name for all borders of the same area, and
> the latter by using type="other:...", but creating a way to
> group borders together by IDREF seems preferable.

the situation that you describe here, is better being solved with a
different implementation: Instead of using border elements, I suggest to
define an <OperationalPoint> and to locate this operational point as an
area covering all the affected tracks. Further, this <OperationalPoint>
can be specified with an attribute
<propOperational>@operationalType="shuntingYard". Finally, the
interlocking element may reference this operational point.

So, to conclude: I think that grouping of borders is not the best
solution here. Borders shall be used where there is an explicit point
(e.g. on the track) where e.g. the ownership changes (without knowing
where else it will change too).