| [railML2] Proposed semantic constraint for <specialService> [message #3394] |
Tue, 19 November 2024 13:59  |
Milan Wölke
Messages: 206
Registered: April 2007
|
Senior Member |
|
|
Hello community,
as some of you may know we at railML are currently developing a new version of railVIVID, the tool available for inspecting and validating railML files. While doing so we came across an issue with the element //operatingPeriod/specialService. Our developers propose to introduce a semantic constraint for this, that makes sure that any date given for specialService/singleDate must not be outside the timeframe indicated by the enclosing operatingPeriod and by extension of the associated timetablePeriod. Additionally, it should be made sure that no value specified for the attribute singleDate shall be overlapped by other <specialService> elements of the same enclosing <operatingPeriod>.
The proposed wording would be like this:
The value of @singleDate of <specialService> must not overlap with other <specialService> validity periods of the same enclosing <operatingPeriod> and must not be outside of time period defined in enclosing <operatingPeriod> and by extension the associated timetable period.
What is your opinion on this? Shall we add this or do you think this will introduce problems with existing usages? Would it be helpful for new implementors? Do you have suggestions for a better and clearer wording?
Best regards, Milan
Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
