> 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/technical/structure-of-delegation-evidence/data-rights-credential-vc.md).

# Data Rights Credential (VC)

This page explains how delegation evidence can be conveyed as a Verifiable Credential (VC), without changing the existing policy model (`policyIssuer`, `accessSubject` , `policySets` , `rules`). The purpose is interoperability with ecosystems using VCs while preserving iSHARE semantics.

#### Main Differences

* **Semantics stay the same**: the delegation evidence JSON (targets, actions, constraints, licenses, validity) and the authorisation decision logic at the Service Provider are unchanged.
* **Envelope and Transport changes**: instead of receiving and sending a signed JWT, parties issue and present a VC (or a Verifiable Presentation). Status lists enable revocation and suspension states that are not available with plain short-lived JWTs.
  * The Authorisation Registry MAY issue the credential (on behalf of the Entitled Party) and MAY act as the Verifiable Data Registry; alternatively, scheme owner/data spaces publish the JSON Schemas.

### Credential Structure

When using VCs, the Authorisation Registry can issue a **DatarightsCredential** that embeds the existing **datarights evidence**. Service Providers verify the credential (including revocation status) and then evaluate the embedded policies as they do today. A **DatarightsCredential** issued by, or on behalf of, the Authorisation Registry carries the current evidence under `credentialSubject.datarightsEvidence`. The VC conforms to VC Data Model 2.0 (JSON-LD or VC-JWT).

```json
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://schemas.ishare.eu/v3/datarights.json"
  ],
  "id": "http://authorisationregistry.example/credentials/e25d402a-d240-48e7-b749-fb5b01546bfd",
  "type": [
    "VerifiableCredential",
    "DatarightsCredential"
  ],
  "issuer": "did:ishare:EU.NL.NTRNL00000000",
  "validFrom": "2025-05-10T08:00:00Z",
  "credentialSubject": {
    "id": "did:ishare:EU.NL.NLNTR-12345678",
    "alsoKnownAs": [
      "did:elsi:LEIXG-724500AZSGBRY55MNS59",
      "did:key:z6MkhfrsD3GUMjGvRxTTSamE1WnS9w3nDJLeZzT1KZVrU5tE",
      "did:web:example.com",
      "AS.JA.NTA:1234567890123"
    ],
    "datarightsEvidence": {
      "notBefore": 1541058939,
      "notOnOrAfter": 2147483647,
      "policySets": [
        {
          "maxDelegationDepth": 0,
          "target": {
            "environment": {
              "licenses": [
                "https://licenses.ishare.eu/general-unrestricted/1.0"
              ]
            }
          },
          "policies": [
            {
              "target": {
                "resource": {
                  "type": "GS1.CONTAINER",
                  "identifiers": [
                    "180621.ABC1234"
                  ],
                  "attributes": [
                    "GS1.CONTAINER.ATTRIBUTE.ETA"
                  ]
                },
                "actions": [
                  "ISHARE.READ"
                ]
              },
              "rules": [
                {
                  "effect": "Permit",
                  "conditions": {
                    "allOf": [
                      {
                        "leftOperand": "serviceProvider",
                        "operator": "equal",
                        "rightOperand": "did:ishare:EU.NL.NTRNL-10000003"
                      }
                    ]
                  }
                }
              ]
            }
          ]
        }
      ]
    }
  },
  "credentialStatus": {
    "id": "https://authorisationregistry.example/status/2025-05#12345",
    "type": "BitstringStatusListEntry",
    "statusPurpose": "revocation",
    "statusListIndex": "12345",
    "statusListCredential": "https://authorisationregistry.example/status/2025-05"
  }
}
```


---

# 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/technical/structure-of-delegation-evidence/data-rights-credential-vc.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.