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 #3995 is a reply to message #3590] Wed, 06 May 2026 17:52 Go to previous messageGo to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 230
Registered: April 2007
Senior Member
Hi all,

in general I would agree with Larissas Semantic Contraint proposals. They reflect the way I would understand the model. Like David pointed out, connections between netElements of different levels would somehow connect the graphs when this should rather be done using aggregation.

@Mathias: Can you provide some short example how that would look like? I think I am missing something with your scenario. If the netElement is shared between meso and micro, how can you aggregate?

Best regards, Milan



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


Current Time: Sun Aug 09 19:07:57 CEST 2026