Home » railML newsgroups » railml.interlocking » [railML3] Split Structure of AssetsForInterlocking
[railML3] Split Structure of AssetsForInterlocking [message #2457] Sat, 13 June 2020 14:47
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 87
Registered: March 2016
Member
Dear all,

currently we have one container in IL part taking a lot of different child
elements called <assetsForInterlocking>. As the number of childs may further
increase I would suggest to split this container in at least three new ones
according the already defined classes:

- <trackAssetsForInterlocking>
- <routeObjectsForInterlocking>
- <systemAssetsForInterlocking>

This would mean a breach of compatibility with the existing railML3.1-IL. As a
result of responses to the posts "Abbreviations in element names" this
compatibility does not exist due to changes in element names.

What is your opinion on the issue? Shall we do this restructuring for better
clarity?
--
Best regards,
Joerg v. Lingen - Interlocking Coordinator
Previous Topic: [railML3.1] Modelling of a double slip switch
Next Topic: [railML3] Specific commands and indications of signal box user interface
Goto Forum:
  


Current Time: Mon Jun 17 03:39:22 CEST 2024