# 2018-08-15 - Booking

## Summary

We reviewed progress on the booking API specification and several recent additions, including:

* Support for exposing terms and conditions and privacy notices
* Support for cancellations and refunds

The key conclusions are that:

* we need to add support for privacy notices, in addition to terms and conditions
* we should consider how best to provide this, often service level information, in ways that minimises repetition of data
* we need to support marketing opt-in information
* we need to be careful around conformance language re: marketing opt-in, etc to ensure that we are inline with current GDPR and marketing email guidance
* that as not all platforms support refunds, we cannot mandate refund/cancellation support, but it will be recommended
* there is a need to include windows during which cancellations/refunds can be accepted, and whether cancellations are allowed, to improve user experience of bookings
* we also agreed to review how URL discovery is currently specified to ensure we're avoiding need to replicate data in feeds

## Slides

{% embed url="<https://docs.google.com/presentation/d/1VEsicULV18n2NOKKw-Vl7V8z9dKcTWfVdDsw9YrBJWI/edit>" %}

## Video

{% embed url="<https://youtu.be/rOoIPFNDgXw>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://w3c.openactive.io/meetings-archive/2018-08-15-booking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
