| Re: [railML 3] New semantic constraint for trainVariant [message #3079 is a reply to message #3069] |
Tue, 02 May 2023 17:57  |
Milan Wölke
Messages: 139
Registered: April 2007
|
Senior Member |
|
|
We discussed this question in our last TT developer call. If, as stated above a new use case needs to be supported a modelling for that use case needs to be found that does not collide with the established semantic constraints. Usually this is possible. In this case for example a different kind of variant could be imagined that would then encode the needed data for the use case. That way the semantic constraint would remain valid and importing software would only import the parts that apply to it (assuming an importing software does not support the new use case) with all assumptions applicable.
Just to have this also documented here.
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
