Home » railML newsgroups » railml.timetable » [railML2] Proposed semantic constraint for <specialService>
Re: [railML2] Proposed semantic constraint for <specialService> [message #3464 is a reply to message #3394] Thu, 13 February 2025 09:15 Go to previous messageGo to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 80
Registered: March 2015
Member
Quote:
The first one, strictly speaking, only excludes overlaps of date periods (start/end date) with other date periods or single dates.
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. Must not overlap with other <specialService> validity periods or single dates of the same enclosing <operatingPeriod>.
It does not exclude overlaps of two single dates.
Suggest to define two separate constraints.

Yes, I agree that we could be more specific here. But since in both cases (single days and periods) the parent 'problem' is the same, I wouldn't necessarily be in favour of splitting the SemCon into 2. Perhaps the following formulation would be a compromise:

Within the same operatingPeriod element, a date must not be contained in more than one specialService element. A date is considered to be contained in a specialService element if
- it is stated directly in a singleDate attribute or
- it is within the time span between startDate and endDate (inclusive in both cases)

Best regards
Christian Rößiger
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML2] Wording of semantic constraints TT:015 and TT:016
Next Topic: [railML 2] New semantic constraint for <operatingPeriod>
Goto Forum:
  


Current Time: Sat Nov 15 19:30:39 CET 2025