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 #3487 is a reply to message #3485] Mon, 03 March 2025 09:05 Go to previous messageGo to previous message
Rémi Collet is currently offline  Rémi Collet
Messages: 13
Registered: November 2024
Junior Member
I don't think that RTM restricts NetRelations from linking NetElements from different levels. Perhaps I am too used to RSM and there is a difference here, though ?

With that premice in mind, a NetRelation that links NetElements from different levels (say micro and macro) should be categorized as which ? I don't have a definitive answer, and to me, the NetRelation could be categorized as belonging to both levels in that case.

Ontologist @Infrabel (Belgian Railway Infrastructure Manager)
remicollet(at)infrabelbe

[Updated on: Mon, 03 March 2025 09:05]

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: Mon Jul 20 03:15:37 CEST 2026