Home » railML newsgroups » railML.infrastructure » [railML3] Extensions to the Modelling of Signals (Two more options related to the physical location of signals)
Re: [railML3] Extensions to the Modelling of Signals [message #3817 is a reply to message #3816] Mon, 08 December 2025 05:50 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 580
Registered: January 2016
Senior Member
Dear all,

topic 1)
is solved as described by Mathias.

topic 2)
All the different options have their pros and cons, but one option is also missing: You can group signals together by @belongsToParent. The information that the signal is installed at a gantry can be modelled with <signalConstruction>@type="gantry".
In order to select the right option as best practice (including maybe also an extension of the schema), we need to conclude, which information about the gantry (or the pole) are necessary to know for the use case.

Best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Modelling serviceSections
Next Topic: [railML3] Additional Switch attributes
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Sep 09 15:25:11 CEST 2026