> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/understand/assets/semantics.md).

# Semantics

Semantic models are the business-facing layer on top of curated outputs. They expose dimensions and measures so you can query without learning every underlying table or transformation.

In `Orders Analytics Platform`, semantic models like `CUSTOMER_PROFILE`, `DAILY_SALES`, `PRODUCT_PROFILE`, `RFM`, `SALES_FUNNEL`, and `WEEKLY_SALES` expose customer, sales, and product attributes for analysis.

## Open a semantic model

From the data product page, open **Assets**, expand **Semantics**, and click a semantic model.

The detail view shows the name, a description, a summary row with **Kind** and **Schedule**, a **View lineage** link, and the **Columns**, **Dependencies**, and **Relationships** tabs. The **Columns** tab lists each field with its **Kind** (dimension or measure), **Tags**, and **Quality**.

![Semantic model detail showing columns with kind, tags, and quality](/files/o8MlGyvfBngElm6iOrUe)

## What to review

<table><thead><tr><th width="140.1781005859375">Area</th><th>Why it matters</th></tr></thead><tbody><tr><td>Description</td><td>What the model is for. Decides whether it fits your analysis.</td></tr><tr><td>Kind</td><td>Confirms the asset is a semantic model you can query directly.</td></tr><tr><td>Columns</td><td>Dimensions and measures you can query without touching the underlying tables.</td></tr><tr><td>Dependencies</td><td>Outputs that feed the model and what's built on it.</td></tr><tr><td>Relationships</td><td>How the model joins to others. Tells you what you can combine in a query.</td></tr></tbody></table>

## Dimensions and measures

Use the columns list to confirm the semantic model exposes the fields you need. Each column shows its kind: dimensions for filtering, grouping, and slicing; measures for aggregations and numeric values.

In `CUSTOMER_PROFILE`, fields like `customer_name`, `email`, `region_name`, `first_order_date`, `last_order_date`, and `total_orders` describe customer identity and purchase behavior.

## Dependencies

Open the **Dependencies** tab for upstream and downstream models. Lets you see the curated outputs that feed the model and the metrics or models built on top.

![Semantic model dependencies tab showing upstream and downstream models](/files/oC5b1bBFgnnjtG22dpTv)

## Relationships

To see which models you can combine in a single query, open the **Relationships** tab. Each row shows the related **Model**, **Relationship** type (e.g. one-to-many), **Joins** key, and any **Tags**.

![Semantic model relationships tab showing model, relationship type, and joins](/files/1KuN66wHJlKou06T91rm)

## Lineage

Click **View lineage** to trace a semantic field back to outputs, inputs, or source datasets.


---

# 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://v2.dataos.info/consume/understand/assets/semantics.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.