Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Offer inheritance #232

Open
nickevansuk opened this issue Jun 10, 2022 · 0 comments
Open

Offer inheritance #232

nickevansuk opened this issue Jun 10, 2022 · 0 comments
Labels
CR3 Issues relating to CR3

Comments

@nickevansuk
Copy link
Contributor

nickevansuk commented Jun 10, 2022

Clarify 8.1 Definition of a 'bookable' Opportunity and Offer pair:

The pairing of an Opportunity of type Event, ScheduledSession, HeadlineEvent, Slot or CourseInstance with an Offer is deemed to be bookable via the Open Booking API if the Offer is applicable to the Opportunity following the principles of Offer inheritance contained in [Modelling-Opportunity-Data], and if both the Opportunity and Offer meet the criteria specified below.

This section should include additional clarification for "Offer inheritance" as follows:

The identifier property of the Offers is used to identify overrides between the SessionSeries and ScheduledSession, such that a ScheduledSession Offer will override an SessionSeries Offer where the identifier is identical. The Broker MUST use the Offer of the ScheduledSession (including its @id) in place of an Offer in the SessionSeries, where the identifier exactly matches. The ScheduledSession SHOULD only contain Offers where they differ from those defined in the SessionSeries. The @id of the ScheduledSession Offer MUST be distinct from the @id of the SessionSeries Offer, when the value of any property within the Offer is different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CR3 Issues relating to CR3
Development

No branches or pull requests

1 participant