# Sources and licences ## Github repositories The deliverables we produce are shared on Github. Feel free to fork and to propose changes with pull requests! \>>> [Access to the semantic specification (ontology, including machine readable owl files)](https://github.com/datafoodconsortium/ontology) \>>> [Access to this present documentation including the technical specification](https://github.com/datafoodconsortium/standarddocumentation) \>>> [Access to the prototype code](https://github.com/datafoodconsortium/dfc-prototype-V3) ## Licences Until now we use three licences for these deliverables: * [CC-BY-ND](https://creativecommons.org/licenses/by-nd/2.0/) : for the articles we publish. We authorize anyone to share and use, even commercially, what we publish. But if you want to modify it, we want you to join the consortium and do it with us so we cooperate and cocreate, improve, together. So you can't distribute modified versions of it. * [AGPL 3](https://www.gnu.org/licenses/agpl-3.0.en.html) : for the ontology and technical standard. We are happy for you to modify it but if you do we want your production to remain in the commons sphere. Ideally we invite you to join the consortium and improve the current version with us! * [MIT](https://en.wikipedia.org/wiki/MIT_License) : for the prototype. It is very permissive, you can do whatever you want with the code of the prototype, even build commercial applications. As we want as many people to use the standard and build applications on it, we don't want to put any barrier to it. If you are an expert in licences and want to advice us, please contact us! --- # 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://docs.dfc-standard.org/dfc-standard-documentation/sources-and-licences.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.