| Re: Platform @belongsToParent and <ownsPlatformEdge> [message #2167 is a reply to message #2151] |
Mon, 08 April 2019 19:56   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Thomas,
thank you for your input and for summing up the topic:
Am 18.02.2019 um 20:55 schrieb Thomas Nygreen:
> [...]
> [b]Summing up:[b] I do not need a way to separate platforms
> from platform edges (alternative 4). But if someone else
> needs a way to do this explicitly, I prefer to add an
> optional attribute (alternative 1).
From my perspective there are two aspects to get feedback on:
1) Is there a need to distinguish between platforms and platform edges.
I think, there is. For example, in Czech Republic the platform
(nastupiste) has a different identifier/designator than the connected
platform edges (kolej). Other examples around Europe and the world?
2) If there is a need for both, platforms and platform edges, is it
enough to use the same element <platform> and just have a boolean
attribute @isPlatformEdge to distinguish between them or do we need
further attributes that are specific for only one of the types?
As usual, any contribution is very much appreciated...
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
