| [railML3] Refactoring of straightBranch and turningBranch of switchIS [message #3890] |
Wed, 11 February 2026 12:30  |
Milan Wölke
Messages: 219
Registered: April 2007
|
Senior Member |
|
|
Hi all,
in a recent review of the modelling of <switchIS> we identified an issue we want to correct in the upcoming version 3.4 of railML. In particular we found that currently (3.3) the <straightBranch> as well as the <turningBranch>, so elements that are intended to be used when modelling switch crossings, each contain the attributes @joiningSpeed and @branchingSpeed. We found that this does not make sense for these. Specifying a speed, does make sense but providing separate values for joining and branching does not. Therefore we intend to update the modelling so that only the attribute @speed will be available on <straightBranch> and <turningBranch>.
<leftBranch> and <rightBranch> will be left untouched by this change.
Is there anyone who disagrees with that? Is there a need for someone to specify a branchingSpeed and a joiningSpeed for <straightBranch> or <turningBranch>? If so, please let us know the background so that we can update the documentation.
Best regards, Milan
Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|
Members
Search
Help
Login
Home
