Home » railML newsgroups » railml.timetable » [railML2] Proposed semantic constraint for <specialService>
Re: [railML2] Proposed semantic constraint for <specialService> [message #3408 is a reply to message #3401] Wed, 11 December 2024 12:09 Go to previous messageGo to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 206
Registered: April 2007
Senior Member
Hi Christian,

thanks for your reply. That makes sense. So we change TT:018 to:

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. Must not overlap with other <specialService> validity periods or single dates of the same enclosing <operatingPeriod>.
and adapt the new semantic constrain to be like this:

Quote:

The values of @singleDate, @startDate and @endDate of <specialService> must not be outside of time period defined in enclosing <operatingPeriod>.
Do you agree?

Best regards, Milan

Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
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:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Nov 15 19:26:35 CET 2025