> 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/activity-list.md). # Activity List The code behind the OpenActive's Activity List Controlled Vocabulary. Repos tagged with the `activity-list` topic are used to power OpenActive's [Activity List](https://www.openactive.io/activity-list/), our [Controlled Vocabulary](https://en.wikipedia.org/wiki/Controlled_vocabulary) used to assign unique identifiers to sport activities. * [**activity-list**](https://github.com/openactive/activity-list)**:** This repo contains the code used to parse the activity list and present it via a web front-end * [**activity-list-json-xml**](https://github.com/openactive/activity-list-xml-json)**:** A small repo; takes XML-encoded activity input and converts it into a JSON-LD representation. * [**concept-scheme-restriction generator**](https://github.com/openactive/concept-scheme-restriction-generator): Outputs complete Concept Scheme files from ConceptSchemeRestrictions. In other words, given a parent Concept Scheme and a list of attributes to exclude from it, generates a Concept Scheme consisting of only those attributes which remain. The Activity List Controlled Vocabulary is expressed in [SKOS](https://en.wikipedia.org/wiki/Simple_Knowledge_Organization_System). Developers working on the Activity List may thus also wish to investigate [OpenActive's `skos` repos](/guide-to-openactive-on-github/skos.md). --- # 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/activity-list.md?ask=&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.