TimetableValidityPeriod

Start and end of timetable validity (time window) of journeys for which schedules are to be returned by the data producer. The ValidityPeriod of the timetable must not exceed the ValidityPeriod requested by the subscriber. If omitted, then the full - by the subscriber requested - ValidityPeriod or configured data horizon applies.

Since the end of an OPERATING DAY of one ITCS does not usually coincide with the end of another ITCS, it may happen that data cannot be provided for the complete time frame requested by a subscriber. In order for the data consumer to be aware of this situation, the data producer should confirm - in each returned timetable - for which part of the requested ValidityPeriod he can actually deliver journey schedules. If the requested period is so far in the past that the data producer does no longer have any data, he should reject the subscription with "Status=false" and a BeyondDataHorizon ErrorCondition. If the requested period is so far in the future that the data producer does not yet have any data, he will deliver data as soon as it is available.

A timetable falls inside the ValidityPeriod if all of its journeys fall inside it. A journey falls inside the ValidityPeriod if the AimedDepartureTime or AimedArrivalTime at any CALL lies between the Start- and EndTime of the ValidityPeriod (regardless of whether the aimed times at a previous or subsequent CALL fall ouside of the ValidityPeriod). Careful: Journeys which themselves fall outside the ValidityPeriod, but which are linked to a journey within the ValidityPeriod by a JOURNEY RELATION, are also regarded as falling inside the ValidityPeriod. Examples are journeys where the vehicle is split or joins with or is replaced by another vehicle.