> For the complete documentation index, see [llms.txt](https://usecaseframework.openactive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usecaseframework.openactive.io/introducing-the-framework/who-is-the-framework-for.md). # Who is the framework for? The Use case framework is a tool for anyone who would like to use OA specifications to solve a problem or create a new opportunity that contributes towards the initiative’s strategic outcomes. Solutions are broad and varied, and could include: data, technology, processes, standards, training or guidance. Examples of organisations that could use the framework include: * Organisations that hold data related to opportunities for people to be active. For example: activities and events, organisations, places, routes. * Innovators and start-ups with exciting ideas about ways of using and sharing data to reach more people. * Organisations in the existing OA community that are working to grow OA through the development of their own work streams or by supporting new organisations to adopt OA infrastructure and enter the community. * Policymakers. * Organisations new to the OA community that would like to explore the ways in which the OA specifications can be applied to their work. --- # 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, and the optional `goal` query parameter: ``` GET https://usecaseframework.openactive.io/introducing-the-framework/who-is-the-framework-for.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.