> For the complete documentation index, see [llms.txt](https://docs.dfc-standard.org/dfc-standard-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dfc-standard.org/dfc-standard-documentation/contributing/general-decisions/taxonomy-enrichment/taxonomy-updates.md).

# Taxonomy updates

The procedure for releasing updates to the taxon files is detailed below:

1. Initial changes are submitted to [vocBench](https://vocbench.datafoodconsortium.org/vocbench3/#/Home).
2. Changes are approved & merged by a project administrator.
3. Updated JSON-LD and RDF files are generated by export from vocBench (ensuring both Graph "<http://www.w3.org/2004/02/skos/core>" and the "Include Inferred" option are checked).
4. Updated files are pushed to the [github repository](https://github.com/datafoodconsortium/taxonomies/tree/nextTaxon), on the `nextTaxon` branch.
5. Reviews are completed and the updated files are merged into the `main` branch.
6. Following the appropriate flow (determined by whether it's a Patch, Minor, or Major Release).
7. A new release is generated and updated JSON-LD and RDF files are published to the latest release folder for the contexts to read.


---

# 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://docs.dfc-standard.org/dfc-standard-documentation/contributing/general-decisions/taxonomy-enrichment/taxonomy-updates.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.