Home » railML newsgroups » railml.timetable » [railML2] Proposed semantic constraint for <specialService>
Re: [railML2] Proposed semantic constraint for <specialService> [message #3401 is a reply to message #3394] Tue, 26 November 2024 14:13 Go to previous messageGo to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 80
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

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:20:29 CET 2025