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 #3816 is a reply to message #3753] Fri, 05 December 2025 18:22 Go to previous messageGo to previous message
Martin Zien is currently offline  Martin Zien
Messages: 16
Registered: December 2021
Junior Member
Hello,

regarding topic 1) I would agree to follow the implementation as it is in RTM by now.


regarding topic 2)
Mathias' Option 1: This could be further followed up for modeling of Gantries and Signals applied to Gantries. But it's not covering all the use cases of Georg.

Mathias' Option 2: Sounds quite plausible. There are some detailing questions open:
Where would you see such <supportConstruction> be located in railML: In parallel to <signalsIS> (would allow to involve also support constructions for other purposes than signal mounting) or subordinated to <signalsIS>? Should it be limited to "special cases" as described by Georg, or may it be consequently needed for each and every signal?

Mathias' Option 3: Such <designnator> would then refer to an entry in a rule book (= Generic Type in a railway infrastructure) or an itm in a(public?) asset/inventory list of the Infrastrucutre Manager?

Mathias' Option 4: to me it's not clear, how that should work. More explanation is needed.

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 14:24:08 CEST 2026