| Re: [railML2] Proposed semantic constraint for <specialService> [message #3468 is a reply to message #3464] |
Thu, 13 February 2025 17:45  |
Milan Wölke
Messages: 206
Registered: April 2007
|
Senior Member |
|
|
In todays timetable developer meeting we decided to go ahead with Davids proposal. We decided against the approach of Christian reasoning that a semantic constraint should be short and precise. The actual semantics of an attribute should be explained in the semantics part of the wiki pages.
Therefore we will update the exiting semcon TT:018 with the following wording:
Quote:Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given.
and introduce two new semantic constraints as follows:
TT:021:
Quote:Within the same <operatingPeriod> element, a date must not be contained in more than one <specialService> element.
TT:022
Quote:The values of @singleDate, @startDate and @endDate of <specialService> must not be outside of the time period defined in the enclosing <operatingPeriod>.
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
