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

# DID

A DID (Decentralised Identifier) is issued to legal entities during onboarding in compliance with the iSHARE framework, utilising the DID method.

DID Method is used to issue a unique iSHARE identifier to legal entities when onboarding, following the iSHARE framework compliant method `did:ishare`. Specification of the iSHARE DID method is available here: <https://did.ishare.eu>.

This identifier follows a standardised format conforming to global decentralised identity protocols and points to a REST-compliant API for retrieval. The identifier consists of the organisation’s unique ID as defined by national or international standards (e.g., PKI certificate or eIDAS), ensuring secure identity verification. Core elements about DID can be found [here](https://www.w3.org/TR/did-core/).


---

# 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://dev.ishare.eu/version-3.0/introduction/specific-technical-standards/did.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.