Re: [railML2] Adding a new element informationArea to ocp [message #2777 is a reply to message #2773] |
Sat, 26 June 2021 06:53 |
Torben Brand
Messages: 161 Registered: March 2016
|
Senior Member |
|
|
Christian Rahmig <coord(at)infrastructurerailMLorg> wrote:
> Dear Thomas and Milan,
>
> thank you very much for your feedback. So, an implementation
> of the information area in railML 2.5 is intended.
>
> However, we still need some clarification on the naming:
> There exists already an area element in railML 2
> infrastructure (see [1]). In order to avoid confusion, we
> should agree on one of the following options:
> * introduce <trackElements/area> anyway
> * introduce <trackElements/area> and rename <ocp/area> in
> <ocp/zipCodeDistrict>
> * introduce <trackElements/genericArea>
> * introduce <trackElements/specificPurposeArea>
>
> Which solution do you prefer? As usual, any comment is
> highly appreciated...
>
> [1] https://wiki2.railml.org/wiki/IS:area
>
> Thank you very much and best regards
> Christian
Dear all,
The norwegian community would prefer a new generic implementation of «area»
as described in our earlier proposal that fullfills the use case of the
existing ocp zip code area (can then be deprecated), information area,
track section, work area, local area and project area. Note generic areas
can span over both tracks and ocps, so the suggestion is to place it in the
infrastructure root in a container: <infrastructure/areas/area> For the
rest of the suggested implementation see my previous posting.
--
TOBR
|
|
|