> For the complete documentation index, see [llms.txt](https://w3c.openactive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://w3c.openactive.io/meetings-archive/2019-02-27-booking-overview-and-direction-check.md).

# 2019-02-27 - Booking: Overview and direction check

## Summary

We ran through the [booking specification](https://www.openactive.io/open-booking-api/EditorsDraft) at a high level, including checking the direction taken on remaining issues. Everyone was broadly happy, with some comments to raise on GitHub and a suggestion to consolidate cancellations into a single PUT call for the Order (to allow for atomic cancellation, given the potential for additional cancellation constraints to exist).

As a result of the call we:

* Clarified the spec regarding the error raised when attempting to book a non-"bookable" opportunity.
* Amended the spec to make cancelling multiple items atomic, with an outstanding question regarding restrictions (<https://github.com/openactive/open-booking-api/issues/102>)
* Raised and linked an additional issue: <https://github.com/openactive/open-booking-api/issues/103>

## Video

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/2019-02-27-booking-overview-and-direction-check.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.
