Home » railML newsgroups » railml.interlocking » [railML3]: Referencing between IS and IL
Re: [railML3]: Referencing between IS and IL [message #2632 is a reply to message #2445] Wed, 13 January 2021 06:21 Go to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 89
Registered: March 2016
Member
Dear all,

in consequence of the first post about this topic in the interlocking schema the element <trackIL> was introduced, which
has a 1:1 relation to a <track> in IS. At the same time a <tvdSection> has a 1:n relation to <trackIL>.

The second step to cleanup the references in IL shall be the introduction of <endOfTrack> which defines a limit of the
signalBox either by a physical "obstacle" (bufferstop) or the end of supervision by a final trainDetectionElement. This
<endOfTrack> element would be needed as possible <routeExit> or <routeEntry>.

The proposal is to have a type attribute with enum (physical, endOfSupervision) and a <refersTo>@ref into IS depending
on the named type, i.e. "physical" ref to <bufferStop> and "endOfSupervision" ref to <trainDetectionElement>.

See also attached illustration.


Regards,
Jörg von Lingen - Interlocking Coordinator
Joerg von Lingen wrote on 25.05.2020 14:52:
> Hi,
>
> in addition to the first post considering the actual list of functionalInfrastructure it might be questionable, to have
> a counterpart in IL schema for really each of that elements. Thus only few out of the list may be really useful in IL part.
>
> Regards,
> Jörg von Lingen - Interlocking Coordinator
>
 
Read Message
Read Message
Read Message
Previous Topic: Restricted Areas: limitedBy vs. elements inside
Next Topic: [railML3] Train Number Description Field / Beschreibungsfeld für Zugnummern
Goto Forum:
  


Current Time: Tue Jul 23 13:19:56 CEST 2024