> For the complete documentation index, see [llms.txt](https://open-dataspaces.gitbook.io/ods-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-dataspaces.gitbook.io/ods-docs/odp/overview.md).

# Introduction

## Purpose and Background

This protocol specification document (Open Dataspaces Protocol: ODP) aims to provide an abstract specification of interoperable communication procedures (Protocol) that references the Open Data Spaces Reference Architecture Model (ODS-RAM) and aligns with its design principles. It translates the functions of each layer and perspective described in ODS-RAM into an abstract protocol specification, providing implementers with technical development guidelines grounded in its design philosophy. Furthermore, it seeks to deliver an abstract specification with extensibility and generality that, while presenting reference implementation examples, offers implementers flexibility in their choice of technology stack.

***

## Status of the Protocol Specification

This protocol specification is established as the official normative protocol specification within the ODS ecosystem and will be continuously updated in accordance with revisions to the ODS-RAM and related documents.

***

## Scope

This specification covers the following domains and corresponds to each layer and perspective defined in the ODS-RAM.

| ODS-RAM                | Protocol Name                               | Protocol Category |
| ---------------------- | ------------------------------------------- | ----------------- |
| Common Functionalities | Logging                                     | Fundamental       |
| Common Functionalities | Monitoring                                  | Fundamental       |
| Common Functionalities | Notifier                                    | Fundamental       |
| L1                     | Data Trust Assessment                       | Fundamental       |
| L1                     | Data Trustworthiness and Quality Assessment | Fundamental       |
| L2                     | Transaction                                 | Fundamental       |
| L3                     | Identity and Trust                          | Fundamental       |
| L4                     | Metadata Exchange                           | Fundamental       |
| L4                     | Discovery and Search                        | Fundamental       |
| P1                     | Heuristic Contracting                       | Complementary     |
| P1                     | Clearing and Payment                        | Complementary     |

![Relationship Between Layers and Perspectives in ODS-RAM](/files/AwzWg189ZBdG51GkoJIO)

<p align="center">Figure 1 Relationship Between Layers and Perspectives in ODS-RAM</p>

***

## Intended Audience

The primary readers of this specification include:

* System architects and engineers who design and operate Open Dataspaces
* Developers implementing transaction connector, identity infrastructures, and semantic infrastructures
* Data management departments engaged in cross-industry data collaboration
* Research institutions, standardization bodies, and participants in pilot projects
* Technical leaders of companies and municipalities participating in the ODS ecosystem


---

# 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://open-dataspaces.gitbook.io/ods-docs/odp/overview.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.
