# Page Not Found

The URL `meetings/2018-02-27-booking-overview-and-direction-check` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [2019-02-27 - Booking: Overview and direction check](https://w3c.openactive.io/meetings-archive/2019-02-27-booking-overview-and-direction-check.md)
- [2019-03-27 - Booking: Overview and feedback](https://w3c.openactive.io/meetings-archive/2019-03-27-booking-overview-and-feedback.md)
- [2019-03-13 - Booking: Overview and feedback](https://w3c.openactive.io/meetings-archive/2019-03-13-booking-overview-and-feedback.md)
- [2023-03-29 Facilities and Activities](https://w3c.openactive.io/meetings/2023-03-29-facilities-and-activities.md)
- [2024-02-21 Phase 5 Extension and Club Data](https://w3c.openactive.io/meetings/2024-02-21-phase-5-extension-and-club-data.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` 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.

### Option 2 — Browse the documentation index

Full index: https://w3c.openactive.io/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://w3c.openactive.io/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/meetings-archive/2019-02-27-booking-overview-and-direction-check.md`).

You may also use `Accept: text/markdown` header for content negotiation.