Re: [railML2] Adding a new element informationArea to ocp [message #2796 is a reply to message #2781] |
Fri, 23 July 2021 11:01 |
Christian Rößiger
Messages: 62 Registered: March 2015
|
Member |
|
|
Hello all,
Am 01.07.2021 um 23:52 schrieb Thomas Nygreen:
> Following Torben's train of thoughts, how generic should we
> make this element? Possible properties include (at least):
> The usuals: id, code, name, description
> designator
> list of references to limiting elements (defining the
> borders of the area in the track network)
> geographic coordinates
> ocp reference (or vice versa: the ocps can reference to its
> areas by id)
> zip code or other external area codes or area names
I like the idea of a generic <area>. However, I would strictly ensure
that this element does not contain any properties that are needed for a
specific use case. In my view, an <area> should simply represent an area
on the surface of the earth.
Accordingly, an <area> should not contain any references to <controller>
and <ocp> and also no <state> element as suggested by Christian Rahmig.
This implies that the areas must be referenced from their "owners"
(<controller>, <ocp>), in general several <areas> per owner should be
possible.
Likewise, I would avoid the attribute "type", as this property can also
be derived from the referencing element.
Best regards
Christian Rößiger
--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347
|
|
|