Home » railML newsgroups » railML.infrastructure » <crossSection>.ocpTrackID
Re: <crossSection>.ocpTrackID [message #439 is a reply to message #312] Mon, 12 November 2012 12:37 Go to previous messageGo to previous message
Susanne Wunsch railML is currently offline  Susanne Wunsch railML
Messages: 0
Registered: January 2020
Christian Rahmig <coord(at)infrastructurerailmlorg> writes:
>> the attribute <crossSection>.ocpTrackID is defined as "xs:unsignedByte".
>> This is impracticable and probably unintended. We should either define
>> it as something like tGenericRef (and probably rename it into
>> "ocpTrackRef") or define it as a simple xs:string for common use.
>
> Thank you for your comment. With the ticket [1] I renamed the
> attribute <crossSection>.ocpTrackID into ocpTrackRef and assigned it
> to type tGenericRef.
>
> [1] https://trac.assembla.com/railML/ticket/151

I'm sorry but I don't understand the semantics of the attribute
'ocpTrackRef' within the element 'crossSection'.

A 'crossSection' is already positioned at a certain track and may refer
to its appropriate ocp with the attribute 'ocpRef'.

The old "ocpTrackID" typed as 'unsignedByte' looks a bit like an
intended platform number. That may be now defined with the newly
introduced 'platformEdge' element.

But where should the "ocpTrackRef" refer to? What have I missed?

Any comments appreciated.

Kind regards...
Susanne

--
Susanne Wunsch
Schema Coordinator: railML.common
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Something about platforms, platformEdges, serviceSections and their relation to a track
Next Topic: small issues on "register" and "tLineInfrastructureManagerCode"
Goto Forum:
  


Current Time: Mon May 13 03:12:40 CEST 2024