Home » railML newsgroups » railML.infrastructure » [railML3] Semantic constraint for etcsLevelTransition/switchToLevel (need to take into account the relationship between @‌levelType and @‌levelValue)
[railML3] Semantic constraint for etcsLevelTransition/switchToLevel [message #3737] Wed, 08 October 2025 12:54 Go to next message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 116
Registered: November 2022
Senior Member
On 2024-01-15 on the ETCS working group meeting a semantic constraint for IS:switchToLevel was recommended to take into account the relationship between @‌levelType and @‌levelValue.

First suggested semantic constraint is as follows:

If @levelType="ETCS", then only the following values are accepted: levelValue="0", levelValue="1", levelValue="2", levelValue="3".

The second semantic constraint is as follows:

If @levelType="NTC", then the value shall conform to the NID_NTC-values specified in the ERA document "Assignment of values to ETCS variables".

Please let us know if you do not agree with above semantic constraints till 2025-11-06. How could the wording be improved to avoid misunderstandings especially for people new to railML?

Thanks in advance!

Sincerely,


Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [railML3] Semantic constraint for etcsLevelTransition/switchToLevel [message #3741 is a reply to message #3737] Sat, 11 October 2025 10:28 Go to previous messageGo to next message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 174
Registered: February 2025
Location: Brussels
Senior Member
I agree with the semantic rule

Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
Re: [railML3] Semantic constraint for etcsLevelTransition/switchToLevel [message #4018 is a reply to message #3741] Fri, 22 May 2026 13:53 Go to previous message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 116
Registered: November 2022
Senior Member
Dear all

railML coordinators decided on the modelling telco 2026-05-18 to accept semantic constraint given below.

Quote:
If @levelType="ETCS", then only the following values are accepted: levelValue="0", levelValue="1", levelValue="2", levelValue="3".

It is filed as IS:027 at https://wiki3.railml.org/wiki/Dev:SemanticConstraints

Sincerely,


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

[Updated on: Fri, 22 May 2026 13:54]

Report message to a moderator

Previous Topic: Bus replacement services
Next Topic: Relief facilities
Goto Forum:
  


Current Time: Fri Oct 16 16:49:04 GMT+2 2026