# Semantic vocabulary (/docs/okf/semantic-vocabulary)
A link that just says "related" tells an engine very little. The semantic vocabulary gives every concept a precise type and every link a precise meaning, so an engine knows that a table *joins with* another table, or that a new policy *supersedes* an old one.

## How it's used [#how-its-used]

- **Types are hierarchical.** A `database-table` is a kind of data structure, which is a kind of concept, so a question can match at any level.
- **Variations are normalized.** "DB table", "db_table", and "Database Table" all become `database-table`.
- **Questions map to types.** A question about how data flows looks for tables, pipelines, and datasets, not playbooks.
- **Links are checked.** Only relationship types that make sense between two concept types are kept.

## Concept types [#concept-types]

| Area | Types |
| --- | --- |
| Data | `database-table`, `database-view`, `data-pipeline`, `data-model`, `dataset`, `schema` |
| APIs and events | `api-endpoint`, `api-schema`, `webhook`, `event`, `message-queue` |
| Software | `service`, `module`, `function`, `class`, `configuration`, `library` |
| Business | `metric`, `kpi`, `playbook`, `process`, `policy`, `rule`, `decision-record`, `requirement` |
| People | `team`, `role`, `person`, `department`, `vendor` |
| Documentation | `document`, `guide`, `tutorial`, `faq`, `runbook`, `specification` |
| Infrastructure | `service-deployment`, `environment`, `dependency`, `resource`, `alert` |
| General | `concept` |

## Relationship types [#relationship-types]

| Area | Types |
| --- | --- |
| Data | `joins-with`, `references`, `contains`, `derived-from` |
| Dependencies | `depends-on`, `required-by`, `imports`, `extends` |
| Flow | `feeds-into`, `produces`, `consumes`, `triggers`, `reads-from`, `writes-to` |
| Structure | `has-child`, `part-of`, `belongs-to`, `instance-of` |
| Purpose | `documents`, `implements`, `validates`, `monitors`, `configures` |
| Change | `supersedes`, `contradicts`, `preceded-by`, `evolved-from` |
| Ownership | `owned-by` |

`supersedes` and `contradicts` change how retrieval ranks. A superseded concept is dropped, and contradicting concepts are both returned and marked. See [How OKF retrieval works](/docs/okf/how-okf-retrieval-works).

<Callout type="idea">
When you write OKF content yourself, name things the way the vocabulary does. "The orders table joins the customers table" is turned into a typed link more reliably than "orders and customers are connected".
</Callout>

## Next steps [#next-steps]

You know the vocabulary. See how concepts are kept consistent next.

<Cards>
  <Card title="Merging and conflicts" href="/docs/okf/merging-and-conflicts" description="Duplicates, conflicts, and supersession." />
  <Card title="Concept files" href="/docs/okf/concept-files" description="Where types and links are written." />
  <Card title="Generate OKF" href="/docs/okf/generate-okf" description="How links are discovered." />
</Cards>
