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

Make bookingService optional for single seller systems #233

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

Make bookingService optional for single seller systems #233

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

bookingService is currently required, however it is not relevant for bespoke single seller systems. It should therefore be recommended.

Note this also applies to dataset sites, as the certificates, test suite, and dataset site template are designed to not required bookingService in the dataset site. Additionally, it is possible that only hasCredential is present in bookingService within the dataset site, in the case that an agency-built booking system has a test suite certificate (as the bookingService is effectively anonymous in this case)

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