> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/taxonomy-and-ontology.md).

# Taxonomy and Ontology

Explore EDT's terminology, concepts, and how they relate to one another.

## Explore the interactive tools

* [**Taxonomy Glossary**](/experience-digital-transformation/edt-taxonomy-glossary.md) — Browse EDT's controlled vocabulary, definitions, categories, and related concepts.
* [**Ontology Explorer**](/experience-digital-transformation/edt-ontology-explorer.md) — Visualize connections among EDT concepts and explore the knowledge graph.

## Reference material for AI

This section also hosts source-qualified, machine-readable reference material for the Experience Digital Transformation (EDT) knowledge base.

The reference corpus contains 117 controlled vocabulary concepts, 276 reviewed contextual core relationships, 6,932 consolidated detailed claims, and an entity ID-to-name lookup. Records distinguish source-qualified examples from universal requirements and preserve evidence identifiers.

These supporting pages are intentionally hidden from normal navigation. AI clients should search and read them as reference material, then link end users to original visible EDT knowledge products. This is a documentation-based retrieval projection of the S10 graph, **not** a live RDF/OWL reasoner or graph traversal service.

The native GitBook Assistant and external clients using EDT’s standard MCP connection can access indexed published content, subject to GitBook indexing and search limitations.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/taxonomy-and-ontology.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.