| Re: <crossSection>.ocpTrackID [message #465 is a reply to message #445] |
Sat, 24 November 2012 14:02  |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear Dirk, Susanne and other railML users,
>>> 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.
after revision I reverted the renaming and marked the parameter
"ocpTrackID" of type "xs:unsignedByte" as deprecated.
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
