Home » railML newsgroups » railML.infrastructure » [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation (Ensuring that each netElement and netRelation belongs to exactly one RTM:level)
Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation [message #3491 is a reply to message #3487] Mon, 03 March 2025 13:38 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 566
Registered: January 2016
Senior Member
Dear Rémi,

thank you for your feedback. The semantic constraints formulated by Larissa are focusing on linking each netElement and each netRelation with a level of aggregation. As a result, there should be no netElement and no netRelation that is not linked with any level. However, your question is valid and I want to re-formulate it to: "Can a netElement or netRelation be linked with more than one level of aggregation?"

Dear community, what do you think? As usual, any kind of feedback is highly appreciated...

Best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
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: [railML 3.4 bèta 3] BaliseGroup attribute validityDirection
Next Topic: [railML3] @lateralSide and @verticalSide and distances
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue Jul 21 06:11:50 CEST 2026