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 #4055 is a reply to message #4054] Thu, 18 June 2026 17:49 Go to previous messageGo to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 167
Registered: February 2025
Location: Brussels
Senior Member
Considering IS:025 and IS:026, I assume that with your proposal for IS:029, with "same level of aggregation" you mean "same network level"? In that case, it's in line with those two constraints but I would use the word 'network level' instead of 'level of aggregation'.

Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium

[Updated on: Thu, 18 June 2026 21:45]

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
Read Message
Read Message
Previous Topic: [railML3] Order of geometricCoordinate attributes
Next Topic: [railML3.4 beta4] Changed placement of sub-element elementState
Goto Forum:
  

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

Current Time: Fri Sep 11 12:24:58 CEST 2026