> For the complete documentation index, see [llms.txt](https://developer.openactive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.openactive.io/guide-to-openactive-on-github/controlled-vocabularies.md).

# Controlled Vocabularies

SKOS-based taxonomies and term lists for use in OpenActive data.

OpenActive uses a number of [Controlled Vocabularies](https://en.wikipedia.org/wiki/Controlled_vocabulary) (including the [Activity List](/guide-to-openactive-on-github/activity-list.md)) in order to ensure the consistency and quality of OpenActive data. These are all expressed in SKOS, and developers working on Controlled Vocabularies may thus also wish to review [OpenActive's `skos` repos](/guide-to-openactive-on-github/skos.md).

* [**activity-list**](https://github.com/openactive/activity-list)**:** The code used to parse Activity List data and present it via the web front-end.
* [**accessibility-support**](https://github.com/openactive/accessibility-support)**:** A small JSON-LD vocabulary describing different classes of impairment.
* [**facility-types**](https://github.com/openactive/facility-types)**:** A JSON-LD vocabulary describing leisure centre and sport facilities.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.openactive.io/guide-to-openactive-on-github/controlled-vocabularies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.