> For the complete documentation index, see [llms.txt](https://whitepaper.open-data-rights.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.open-data-rights.org/future-considerations/reference-implementations.md).

# Reference Implementations

Given the wide variety of available data sources, the process of implementing data request for large organisations is positively massive. Any efforts that can help make this process easier should be an accepted part of Open Data Rights API practice.

First of all, we encourage the development of open-source reference implementations of the Data Rights API. These implementations could also feature dashboards and experiences that facilitate the process of data requests on the organisational side. These reference implementation should support a wide gamut of languages.

Secondly, a number of plug-ins for common data sources could be made available that easily integrate with Open Data Rights API-based systems. These should face the same scrutiny as the Open Data Rights API. If this development ends up being popular, further standardisation is certainly desirable.

Thirdly, reference implementations for citizen-facing applications implementing the Open Data Rights API should be considered as well. If this development is significantly desirable, a particular solution for citizen-facing applications could be developed, standardised and maintained by the Open Data Rights community.


---

# 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://whitepaper.open-data-rights.org/future-considerations/reference-implementations.md?ask=<question>&goal=<endgoal>
```

`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.