| [railML3] Proposal of a semantic constraint for mileageChange [message #3075] |
Thu, 20 April 2023 12:33  |
Milan Wölke
Messages: 139
Registered: April 2007
|
Senior Member |
|
|
Hi all,
I would like to propose the introduction of two new semantic constraints for the mileageChange element of the railML 3 infrastructure.
First one would restrict the scope of referencing spot locations with the "from" and "to" attribute to those spot locations that are enclosed by the mileageChange element that carries the attributes.
The second one would ensure that both these spot locations actually refer to the same net element.
Both these constraints should not have a negative impact on any existing interfaces as the described is actually what one would expect anyway. However, I would still propose formalizing this in order to make life easier for importing system.
What does the community think?
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
