Home » railML newsgroups » railml.timetable » [railML 3] New semantic constraint for trainVariant
[railML 3] New semantic constraint for trainVariant [message #3057] Mon, 13 March 2023 17:22 Go to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 141
Registered: April 2007
Senior Member
Hi all,

in the last few timetable developer group meetings we have been discussing another semantic constraint in order to help understanding the new timetable model and in order to improve data exchange. This time it is focused on the operationalTrainVariant as well as the commercialTrainVariant. We propose for both of these to define the following semantic constraint:


When calculating which <commercialTrainVariant> of a <commercialTrain> is valid on a particular day always a maximum of one active <commercialTrainVariant> shall be the result. If the result is more than one <commercialTrainVariant>, all except one shall be marked as <isCancelled> or <isOnRequest>.
The above wording exists in the same way for the operationalTrainVariant.
From our point of view this should help make it clear how to export and how import a railML 3 timetable. What do you think? Do you have use cases in mind where this semantic constraint would be a burden?

Best regards, Milan

Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Read Message
Read Message
Read Message
Read Message
Previous Topic: Semantic Constraints for Train Section
Next Topic: Extension of railML's Advanced Example
Goto Forum:

Current Time: Tue May 21 00:45:58 CEST 2024