| Re: Something about platforms, platformEdges, serviceSections and their relation to a track [message #459 is a reply to message #457] |
Wed, 21 November 2012 23:30   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Dear Christian, Carsten and others,
Christian Rahmig <coord(at)infrastructurerailmlorg> writes:
>> 4. As discussed in Zürich it is necessary to link two <platform> or
>> <platformEdges> from an ocpTT. (This is more topic for timetable scheme).
>
> How about the possibility of grouping platform edges similar to the
> concept of the ocp grouping? Using the optional parameter
> "parentPlatformEdgeRef" several platform edges (with lengths) can
> refer to their common parent platform edge (without length). The ocpTT
> from the timetable schema may then refer to the parent platform edge
> and there is no need for further references.
I'm sorry I don't really understand the difference between this aspect
(Trac ticket #122, comment #8, [1]) and the one written in Trac ticket
#209 [2].
The grouping of platform edges offers the possibility to refer only one
platform from the ocpTT (from the train part). That's is already an
important step into the direction of modelling "real" platforms.
The "parentPlatformEdgeRef" should only refer to platform edges that are
"in sequence" not "parallel", shouldn't it? If you may group "parallel
platform edges" that would mean to model a "platform" and should not be
defined with the same "parentPlatformEdgeRef".
If the "parent platform edge" should not have any length and/or height
parameters (what I would prefer because of reduced redundancy) their
should be another element definition for it. It is not similar to the
'ocp concept' because you may not "overwrite" some features at the
children level and inherit some features from the parent level. It is
more or less a grouping concept like the "trackGroup/line" concept.
This would possibly need to define two distinct levels, one for single
platform edges with defined length and height and side values and one
for grouping them with the ocpRef reference. The grouping element should
be referred from the ocpTT. That would enable to define a "platform
number" without any knowledge of length and height.
Any comments appreciated.
[1] http://trac.assembla.com/railML/ticket/122#comment:8
[2] http://trac.assembla.com/railML/ticket/209
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
