Handle booking for unlimited capacity

[nickevansuk]

Proposer

Played

Use Case

Unlimited capacity is currently being handled in open data feeds by replacing maximumAttendeeCapacity and remainingAttendeeCapacity with registrationCount however this is not currently handled by the booking spec.

Why is this needed?

To allow for opportunities with unlimited capacity to be booked.

Proposal

Move registrationCount out of beta, and allow for opportunities with this property to be booked.

A property such as this that indicates "unlimited capacity" in the affirmative is required as we need to keep open the possibility for "null" (not known) within the open data.

This proposal allows the scenario to be handled with only a minor change to the spec, in a way that only affects implementations where unlimited capacity is available.

[lukehesluke]

@nickevansuk with this new field, do the requirements become:

An opportunity is bookable if:

• EITHER:
  • The remainingAttendeeCapacity / remainingUses field is PRESENT and have values greater than the number of spaces being booked in the Order
  • OR the remainingAttendeeCapacity / remainingUses field is ABSENT and the registrationCount field is present (whose presence implies infinite spaces)
• ...other stuff that's unrelated to capacity

I find that the spec is not clear, currently, on whether or not an opportunity could be considered bookable if remainingAttendeeCapacity is undefined