# v3 Examples

Examples in this directory show both the readable credential payloads and the W3C
enveloped form used when credentials are carried in a Verifiable Presentation.

The v3 party examples show the **semi-modular** packaging: the participant's data is
split across three credentials — a base **party ID** credential carrying identity, a
**Framework Compliance** credential carrying the `frameworks` the participant
adheres to, and a **dataspace participant** credential carrying the `dataspaces` it takes
part in. The same information is also shown combined in a single
**Trusted Participant** credential:

- `party/credentials/party-credential.json` is the decoded payload for the base
  party (identity) example — `id`, `name`, and `alsoKnownAs`.
- `party/credentials/framework-compliance-credential.json` is the decoded payload
  for the Framework Compliance example (`credentialSubject.frameworks`).
- `party/credentials/dataspace-participant-credential.json` is the decoded payload
  for the dataspace participant example (`credentialSubject.dataspaces`).
- `party/credentials/trusted-participant-credential.json` is the decoded payload
  for the combined iSHARE participant example (identity + `frameworks` + `dataspaces`).
- `party/credentials/claims/` holds one decoded payload per fully-modular claim
  credential (framework role, framework agreement, framework compliance, dataspace
  role, dataspace agreement, dataspace membership, X.509 certificate, IdP assertion,
  auth registry).
- `party/enveloped/party-credential.json` contains the W3C
  `EnvelopedVerifiableCredential` for the party example.
- `party/enveloped/framework-compliance-credential.json` contains the W3C
  `EnvelopedVerifiableCredential` for the Framework Compliance example.
- `party/enveloped/dataspace-participant-credential.json` contains the W3C
  `EnvelopedVerifiableCredential` for the dataspace participant example.
- `party/enveloped/trusted-participant-credential.json` contains the W3C
  `EnvelopedVerifiableCredential` for the combined iSHARE participant example.
- `party/presentations/participant-presentation.json` shows one Verifiable
  Presentation that carries the three enveloped semi-modular credentials (party,
  compliance, dataspace) in a `verifiableCredential` array.
- `party/enveloped-presentations/participant-presentation.json` contains the W3C
  `EnvelopedVerifiablePresentation` for that presentation.

The identity (`name`, `alsoKnownAs`) lives only in the party ID credential; the
compliance and dataspace credentials carry just `credentialSubject.id` alongside their
domain data. A participant without an identity credential is issued a Party ID credential
alongside its Framework Compliance credential at onboarding.
Their JSON-LD contexts and JSON Schemas live directly under `v3/party-id/`,
`v3/dataspace-participant/`, `v3/framework-compliance/`, and `v3/trusted-participant/`.
The enveloped examples follow the W3C Verifiable Credentials Data Model 2.0 envelope shape:

```json
{
  "@context": "https://www.w3.org/ns/credentials/v2",
  "id": "data:application/vc+jwt,...",
  "type": "EnvelopedVerifiableCredential"
}
```

Enveloped presentation examples use the same pattern with `data:application/vp+jwt`
and `type` set to `EnvelopedVerifiablePresentation`.

The `id` value is a `data:` URL containing a compact JWS-shaped example for the
corresponding plain VC or VP payload. The example issuer public key is available
at `keys/example-issuer-public-jwk.json`. The key is for examples only.