> For the complete documentation index, see [llms.txt](https://framework.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://framework.ishare.eu/version-3.0/introduction/goals-and-scope-of-the-ishare-trust-framework.md).

# Goals and scope of the iSHARE Trust Framework

The iSHARE Trust Framework is a collaborative effort to improve the exchange of data between organisations in and across data spaces. The Framework results in a set of agreements which improve circumstances for data exchange.

The ambition of iSHARE is to lower barriers for sharing data, to empower new forms of collaboration between organisations and to help scale up existing initiatives that aim to improve conditions for data exchange. The underlying assumption is that if data can flow in a controlled and smart way, it will lead to a more efficient use of infrastructure, less carbon emissions and more competitiveness.

The Trust Framework's scope focuses on three main topics that are crucial in any data exchange context:

1. [Identification;](/version-3.0/glossary-and-legal-notices/glossary.md#glossary-identificationidentification)
2. [Authentication](/version-3.0/glossary-and-legal-notices/glossary.md#glossary-authenticationauthentication);
3. [Authorisation](/version-3.0/glossary-and-legal-notices/glossary.md#glossary-authorisationauthorization).

iSHARE focuses on these three aspects as they are considered indispensable in any communication between parties, also in the context of exchanging logistical data. Within the Trust Framework, agreements are made on the above three topics to work towards a more uniform, straightforward and controlled way of exchanging data on a bigger scale than is possible right now\*.

* Uniform: one uniform way of working across all types of modalities, small and large organisations, public and private organisations, suppliers and receivers of data or their software partners, etc. iSHARE aims to create new possibilities for efficiency improvements, time gains and cost savings.
* Straightforward: Easy to connect with new, existing and third-party business partners throughout the sector, more certainty on the trustworthiness of parties you exchange data with, a building block which is easy to implement by your software partners or your IT department and an addition that empowers your existing solutions.
* Controlled: The basic principle within iSHARE is that the owner of the data stays in control at all times; the owner decides with whom what data is exchanged and on what terms.

These three aims can only be reached when a variety of perspectives are considered during the establishment of the Framework. To this end, a variety of organisations are involved in defining the agreements for iSHARE.

{% hint style="info" %}

* The scope of the iSHARE Trust Framework does not include the specification of possible business models for sharing data and/or payments related to data exchange.
* The iSHARE Trust Framework can in some way be compared with the institution of the passport: the Trust Framework will be usable by anyone who owns a digital identity compatible with the framework. This will greatly simplify authentication and authorisation processes, also between different organisations (however, even though organisations can have valid certificates, it does not rule out possible malicious intentions).
  {% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://framework.ishare.eu/version-3.0/introduction/goals-and-scope-of-the-ishare-trust-framework.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.