| Re: [railML2] SemCon TT:011 - Consistency of <times> with same @scope [message #3030 is a reply to message #3026] |
Tue, 19 July 2022 15:03  |
David Lichti
Messages: 16
Registered: December 2020
|
Junior Member |
|
|
In our last TT Dev meeting, we revisited this semantic constraint question and finally opted to drop it entirely for several reasons:
- earliest and latest are used in early planning stages to model constraints to possible train runs. These requirements may actually be contradictory, indicating that such a train run would not be feasible.
- published is used for publication timetables which may differ from actual operational times. Depending on rounding rules and buffer times at different stations, these times may not be strictly increasing in real world examples.
- Some tools allow the user to enter non-increasing or inconsistent times. Putting a semantic constraint on scheduled times would prohibit the exchange of these schedules, even for planning purposes with different tools. There are even real world examples, where impossible schedules are used in production, even though it makes operational delays unavoidable.
|
|
|
|
Members
Search
Help
Login
Home
