Home » railML newsgroups » railml.interlocking » [railML3]: Referencing between IS and IL
[railML3]: Referencing between IS and IL [message #2441] Tue, 19 May 2020 09:29 Go to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 89
Registered: March 2016
Member
Hi,

in railML3 we use a lot of referencing to other elements in order to enhance the
information. In <assetsForInterlocking> we have at the moment only references
into <functionalInfrastructure> of IS when there is a physical representation of
the element at trackside. All other references are strictly inside IL part.
However, there are some physical items which are not in IL but would needed
there without adding additional information, e.g. <bufferStop> would be used as
<routeExit>.

Subsequently it is not always that way the references from functional
interlocking items like <route> are limited to IL elements. Thus it was
suggested to have for each element in <functionalInfrastructure> of IS a
counterpart in IL. This would limit the area of possible reference targets.

SAMPLE:
bufferStop <-- bufferStopIL
signalIS <-- signalIL
routeStart --> signalIL
routeExit --> bufferStopIL

Would you appreciate this change or would you strictly avoid such "auxiliary"
elements without any additional information?

--
Best regards,
Joerg v. 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:59:54 CEST 2024