> 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/detailed-descriptions/functional/licenses.md).

# Licenses

{% hint style="info" %}
In the context of the iSHARE Framework, 'Licenses' and 'Conditions of Exchange' are equal and can be used interchangeably. In the [iSHARE Terms of Use](/version-3.0/detailed-descriptions/legal.md#terms-of-use), they are referred to as 'Conditions of Exchange'.
{% endhint %}

Licenses allow an Entitled Party to explicitly specify what a Service Consumer is allowed to do with the consumption of a service or with received data. The licenses are included in the [delegation evidence](/version-3.0/detailed-descriptions/technical/structure-of-delegation-evidence.md) and are, in this way, applied to specific authorisations. Since all iSHARE participants have signed the terms of use and agree to the underlying scheme rules, participants are legally obliged to comply with the license conditions. In case of any violations, participants can appeal to each other based on the provided licenses.

The licenses, as maintained by iSHARE on [https://licenses.ishare.eu](https://licenses.ishare.eu/), serve as a foundational set provided by iSHARE. Data spaces may extend this set with additional licenses, provided they ensure appropriate legal backing for any additions, such as incorporating them into relevant agreements.

iSHARE licenses are categorised into the following categories:

* General
* Country
* Industry
* Certification

Licenses can be combined using logical operators.


---

# 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/detailed-descriptions/functional/licenses.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.