Home » railML newsgroups » railml.timetable » [railML2] Proposed semantic constraint for <specialService>
Re: [railML2] Proposed semantic constraint for <specialService> [message #3414 is a reply to message #3408] Thu, 19 December 2024 09:50 Go to previous messageGo to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 80
Registered: March 2015
Member
Hello Milan,

Am 11.12.2024 um 12:09 schrieb Milan Wölke:
> 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?

That's fine with me.

Best regards,
Christian

--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347

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