| [railML3] Semantic constraint for etcsLevelTransition/switchToLevel [message #3737] |
Wed, 08 October 2025 12:54  |
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
|
|
|
|
|
|
|
|