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)
[railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation [message #3485] Thu, 27 February 2025 16:14 Go to previous message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 101
Registered: November 2022
Senior Member
Dear all

During the certification of a railML3 export interface we noticed that the railML3 schemas syntactically allow to define netElement and netRelation elements which belong to no level. Furthermore while testing a new version of railVIVID it became apparent that it's possible to have a syntactically valid railML file with intersecting network levels.

To prevent these issues, we suggest the following semantic constraint IS:022 and IS:023:

Each IS:netElement must belong to exactly one RTM:level.

Each IS:netRelation must belong to exactly one RTM:level.

Please let us know if you do not agree with the suggested semantic constraint IS:022 and IS:023 till 2025-04-30. How could the wording be improved to avoid misunderstandings especially for people new to railML?

Sincerely,

Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

[Updated on: Tue, 04 March 2025 15:32]

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
Previous Topic: [railML3] Remodelling levelCrossingIS in railML 3.4
Next Topic: Turntable and Transfer table
Goto Forum:
  

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

Current Time: Fri May 08 17:32:59 CEST 2026