# Best practices Currently, the European Union does little to clarify how the law implements practical considerations in systems and user experience design. Thus, all best practices we know are built off of individual organisations making interpretations themselves. Thus, we end up in a space where smaller organisations follow the wave of their larger precursors, without understanding the rationale behind their decisions. With the Open Data Rights API, best practices concerning data rights are made glaringly obvious. Meanwhile, rationale behind design decisions should be made clear, so that individual implementers understand why things are built the way they are. This affords smaller and larger organisations insight into these considerations at little to no cost. Lastly, a Open Data Rights acts as a forum where discussions regarding data rights are held. This encourages continuous development of these best practices across the industry as a whole, rather than within individual organisations. This increases the amount of eyeballs that watch over technical accessibility, feasibility and security. --- # Agent Instructions: 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: ``` GET https://whitepaper.open-data-rights.org/why-a-data-request-api/best-practices.md?ask= ``` 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. 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.