Home » railML newsgroups » railML.infrastructure » Link a "doubleSwitchCrossing" to two switchesIL (Special Scenario for Treating a "dobleSwitchCrossing" differently in system landscape)
Re: Link a "doubleSwitchCrossing" to two switchesIL [message #2876 is a reply to message #2875] Mon, 17 January 2022 11:53 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Martin,

thank you very much for your new proposal. From infrastructure point of view, it looks good, as it does not introduce new elements, but only new types for the <switch> element. The new types "doubleSwitchCrossingPartitioned" and "partitionSwitch" can be used to define semantic rules on the appearance and multiplicity of <switch> child elements, e.g. branches.

In order to have a synchronized approach: is it also necessary to partition simple switch crossings? If yes: can we use your approach also for simple switch crossings (partitioned)? If no: is the approach described in [1] with only one <switch> element for a simple switch crossing sufficient for all your needs?

[1] https://cloud.railml.org/index.php/f/77969

Thank you very much and best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Grouping IS:trainProtectionElement-s
Next Topic: Function location
Goto Forum:
  


Current Time: Sat May 04 14:12:46 CEST 2024