Home » railML newsgroups » railml.common » [railML2/3] Proposal for new semantic constraint for the version of railML
[railML2/3] Proposal for new semantic constraint for the version of railML [message #3751] Tue, 14 October 2025 12:13 Go to next message
Marharyta Vyskarka is currently offline  Marharyta Vyskarka
Messages: 11
Registered: April 2025
Junior Member
Dear all,

I have noticed that a situation is possible that the @version defined in <railml> can differ from the version deduced from provided railML namespace and it is not restricted. For example, @version might have value of 2.5, but namespace is https://www.railml.org/schemas/3.1, which belongs to railML 3.1.

Such situation doesn't make sense and therefore there should be similar semantic constraint:
"@version defined in the <railML> should match the version deduced from the provided railML namespace".

This proposal has been approved in the modelling telco on the 2025-10-13 in the expedited manner.

Best regards,
Margo

Marharyta Vyskarka – Software Developer
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Re: [railML2/3] Proposal for new semantic constraint for the version of railML [message #3758 is a reply to message #3751] Thu, 23 October 2025 14:02 Go to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 103
Registered: March 2008
Senior Member
Dear all,

Note that this semantic constraint applies to both railML2 (as CO:003) and railML3 (as CO:001)

Best regards,
Thomas

Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Previous Topic: Designator for linearPositioningSystem
Next Topic: [railVIVID 2.1] Visualisation issue
Goto Forum:
  

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

Current Time: Sat Nov 15 20:05:23 CET 2025