| Re: [railML3] rail3:netElement.relation seems useless [message #2830 is a reply to message #2827] |
Thu, 16 September 2021 21:36   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Raphael,
thank you for your post and welcome to the railML forum. You are absolutely right with noticing that the (optional) reference from the NetElement to the NetRelation is redundant to the (mandatory) reference from the NetRelation to the NetElement. However, fundamental RailTopoModel (RTM) that railML 3.x is based on, contains both references in the model.
Your remark, that this redundancy may cause conflicts, is correct. I suggest the following solution: In order to stay compliant with RTM, we leave the syntax as it is with a (mandatory) reference from the NetRelation to the NetElement and an (optional) reference from the NetElement to the NetRelation. But, as we do not want to have the optional references, we document them as being DEPRECATED and not to be used in order to avoid potential inconsistencies.
This is a proposal and I am eager to hear other opinions from the community...
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
|
|
|
|
Members
Search
Help
Login
Home
