| [railML2] Proposed semantic constraint for <specialService> [message #3394] |
Tue, 19 November 2024 13:59  |
Milan Wölke
Messages: 153
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 Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
| Re: [railML2] Proposed semantic constraint for <specialService> [message #3401 is a reply to message #3394] |
Tue, 26 November 2024 14:13  |
Christian Rößiger
Messages: 64
Registered: March 2015
|
Member |
|
|
Hello Milan,
I think that's a good idea and I see little potential for affecting existing implementations. However, I would take look at the existing semantic constraint TT:018 on the same page: This one already defines that specialServices must not overlap, but probably more in regard to time periods (attributes 'startDate' and 'endDate'). I would therefore define in one semantic constraint that specialServices must not overlap (neither single days nor time periods) and in a second one that all specialService definitions must be within the validity of the enclosing operationPeriod.
Best regards,
Christian
|
|
|
|
Members
Search
Help
Login
Home
