Missing AvailabilityCondition

[jomes-db]

Since this is a service that despite being bookable online is also bookable via phone call. This call center may not be staffed 24/7 (so the case for Deutsche Bahn), this is why I would assume an optional AvailabilityCondition could be very helpful in those cases.

https://github.com/NeTEx-CEN/NeTEx/blob/47fed4d3b8da8fc2315df0432371185f0cf544ce/xsd/netex_part_1/part1_ifopt/netex_assistanceBooking_version.xsd#L137

What is your opinion on that?

[ue71603]

@jomes-db I think you should do this on the level of the bookingArrangements. If you have a call center that has a limited opening hour you would add a Booking Arrangement for that with a validityCondition that reflects that:

<bookingArrangements>
		<BookingArrangement version="any" id="tbd:9100WIMBLDN@A1_SF">
			<validityConditions>
				<ValidityConditionRef ref="businessHours"></ValidityConditionRef>
			</validityConditions>
			<LatestBookingTime>16:00:00</LatestBookingTime>
			<MinimumBookingPeriod>PT1H</MinimumBookingPeriod>
			<BookingUrl>assistance.org.uk/wimbledon</BookingUrl>
			<BookingNote>Be nice.</BookingNote>
		</BookingArrangement>
</bookingArrangements>

This may result in you needing multiple BookingArrangements for different services.

@Aurige @skinkie do you concur?

[ue71603]

You can also use different things within the validityConditions to express what you really want to express (e.g. Timeband)