| [railML3] Semantic constraints in railML 2 that should be also in railML 3 [message #3832] |
Wed, 10 December 2025 16:20  |
Marharyta Vyskarka
Messages: 20
Registered: April 2025
|
Junior Member |
|
|
Hello everyone,
As you may know, there are multiple semantic constraints in railML 2 that make sure that start/end times or dates of some elements are specified in chronological order, and that some element's time periods for which they are valid don't overlap (CO:001, CO:002, IS:020, IS:021, RS:002, RS:003, RS:004, TT:001, TT:019, TT:024) [1].
However it came to my attention that there is only one proposed semantic constraint for railML 3 (IS:001), while such semantic constraints might make sense for more elements. Mentioned semantic constraints in railML 2 took some time to develop, as there are some cases where it either makes sense to have end date before start date or have some overlapping.
So I want to ask, do the same semantic constraints make sense for all the elements mentioned in railML 2 that are also in railML 3? Are there also any other elements in railML 3 which should be restricted by similar constraint and which their aspect would need to be restricted?
Please let me know what you think.
[1] https://wiki2.railml.org/wiki/Dev:SemanticConstraints
Best regards,
Margo Vyskarka
Marharyta Vyskarka – Software Developer
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
[Updated on: Thu, 11 December 2025 13:17] Report message to a moderator |
|
|
|
|
|
Members
Search
Help
Login
Home
