> For the complete documentation index, see [llms.txt](https://bdi.gitbook.io/bdi-public-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bdi.gitbook.io/bdi-public-documentation/readme/semantics-kit/alternative-semantics-frameworks-1.md).

# Alternative Semantics Frameworks

## 1. Introduction

When interacting parties do not share an existing semantics standard, the use of LEO is required. Note, however, that it is possible for BDI parties to use any other framework.

For example, consider a multi-model trip from a manufacturer to the BCO that partly travels over sea. The parties involved in the sea trip may, in interactions with one another, make use of the DCSA standard. This is a well-known standard that has been in use for a long time. For the communication with other stakeholders, however, DCSA may not be the best standard, as these parties are not familiar with it or are not currently using it. Therefore, LEO may be required for the interactions with these stakeholders.

## 2. Other standards

### 2.1 DCSA

The DCSA ([**Digital Container Shipping Association**](https://dcsa.org/)**)** maintains a set of standards for data exchange between stakeholders in the maritime world. These standards are widely adopted and can be considered for support in data exchange within BDI implementations. However, when using these standards, one must consider whether the BDI principles — e.g. security, zero trust, data sovereignty and data at the source — can still be maintained, as very few of these are required by the DCSA standards.

{% hint style="warning" %}
**Other frameworks**

The DCSA described above is only one example of an an alternative semantic framework that can be used in the context of the BDI. Other frameworks, such as the IATA standard used for air freight, will be added later when necessary.
{% endhint %}


---

# 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://bdi.gitbook.io/bdi-public-documentation/readme/semantics-kit/alternative-semantics-frameworks-1.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.