| Re: <crossSection>.ocpTrackID [message #445 is a reply to message #440] |
Mon, 12 November 2012 13:54   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
>> But where should the "ocpTrackRef" refer to?
>
> I also did ask myself that question.
>
> We could probably rename it "platformEdgeRef" which would be of some
> practical relevance. But in rare cases there could be two platform
> edges at one cross-section. (The relation from a cross-section to its
> platforms is also given by both relating to the same <ocp> and laying
> at the same track. So if this is not too much around the corner, we
> could also declare ocpTrackRef as obsolete.)
I reopened the Trac ticket in order to clarify this issue with railML
2.2:
http://trac.assembla.com/railML/ticket/151#comment:3
I would assume that the current implementation already fulfills all
needed requirements.
A 'crossSection' has a position on a certain track. The 'platformEdge's
each have positions and lengths on the same track. That means one could
find out the appropriate 'crossSection' for a certain 'platformEdge' by
traversing along the 'track.
But anyway, why to refer from 'crossSection' to a 'platformEdge'? The
platformEdge already itself refers to an 'ocp' with the attribute
'ocpRef'. The 'track' itself may be "part of an ocp" with the element
propEquipment/trackRef.
If 'ocpTrackID' was used for a "platform number" I would declare it
deprecated.
Any comments appreciated.
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
