> For the complete documentation index, see [llms.txt](https://docs.industryapps.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.industryapps.net/common-faq/how-to-use-eclass-and-concept-dictionary/how-is-eclass-and-concept-dictionary-are-used.md).
# How is ECLASS and Concept dictionary are used
There are 100s of solutions that allows an asset to be represented as a Digital twin. Also there are multiple standards and protocols that streams the data to an application. The biggest challenge is that it only solves the problem of data transmission and storage but not the context.
**Context is always hidden with in the application which makes them non interoperable**
Lets take an example of a defining a property like **IP Code**, or **Ingress Protection Code** for an asset. Now every application will get this get this data and will store it under its own field name and provide its own description. Now this is all great as long as information needs to be accessed on with in the solution context. But business requires information to shared along the value chain. To customer to vendors or even other solutions.
This is where Eclass or concept dictionary plays a role. Instead of defining them under the solutions own structure they are mapped as properties in AAS and then mapped to a unique identifier ( IRDI / URI ) this is a global standard and open semantic dictionary which allows anyone to get the clear context of this information. So now your asset ( Digital twin) becomes a Industry 4.0 compliant asset which is interoperable.
Another key benefit is multi language support - Eclass offers the definition in all leading languages like English, Chinese, German, Frech, Korean etc which makes it easy for global interpretation of your information.
---
# 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.industryapps.net/common-faq/how-to-use-eclass-and-concept-dictionary/how-is-eclass-and-concept-dictionary-are-used.md?ask=&goal=
```
`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.