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 #4054 is a reply to message #3997] Thu, 18 June 2026 13:36 Go to previous messageGo to previous message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 107
Registered: November 2022
Senior Member
Dear all

To ensure readability of railML files coordinators approved sematic constraints given below on 2026-05-18. They are filed as IS:025 and IS:026 at https://wiki3.railml.org/wiki/Dev:SemanticConstraints.

IS:025: Each <netElement> must belong to exactly one <level>.

IS:026: Each <netRelation> must belong to exactly one <level>.

This follows existing practice of railML partners e.g. Hacon, Trafikverket and SBB.

Additionally, railML.org suggests introducing yet another semantic constraint:

IS:029: Each netRelation must reference netElements of the same level of aggregation.

Please let us know your doubts until 2026-07-21.

Sincerely,

Larissa Zhuchyi – Ontology Researcher
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: Sun Aug 09 17:59:24 CEST 2026