Securing Verifiable Credentials using JOSE and COSE

W3C Working Draft

More details about this document
This version:
https://www.w3.org/TR/2023/WD-vc-jose-cose-20230920/
Latest published version:
https://www.w3.org/TR/vc-jose-cose/
Latest editor's draft:
https://w3c.github.io/vc-jose-cose/
History:
https://www.w3.org/standards/history/vc-jose-cose/
Commit history
Editors:
Orie Steele (Transmute)
Michael Jones (independent)
Michael Prorock (Mesur.io)
Feedback:
GitHub w3c/vc-jose-cose (pull requests, new issue, open issues)

Abstract

This specification defines how to secure credentials and presentations conforming to the [VC-DATA-MODEL], with JSON Object Signing and Encryption (JOSE), and CBOR Object Signing and Encryption (COSE) [RFC9052]. This enables the Verifiable Credential data model [VC-DATA-MODEL]to be implemented with standards for signing and encryption that are widely adopted.

Status of This Document

This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

This document was published by the Verifiable Credentials Working Group as a Working Draft using the Recommendation track.

Publication as a Working Draft does not imply endorsement by W3C and its Members.

This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 12 June 2023 W3C Process Document.

1. Introduction

This specification describes how to secure media types expressing Verifiable Credentials and Verifiable Presentations as described in the [VC-DATA-MODEL], using approaches described by the OAuth, JOSE, and COSE working groups at IETF. This includes SD-JWT [SD-JWT] and COSE [RFC9052], and provides an approach using well-defined content types [RFC6838] and structured suffixes [MULTIPLE-SUFFIXES] to distinguish the data types of unsecured documents conforming to [VC-DATA-MODEL] from the data types of secured documents conforming to [VC-DATA-MODEL], defined in this specification.

Selective Disclosure for JWTs (SD-JWT) [SD-JWT] provides a standardized mechanism for digitally signing JSON documents. It provides a means to ensure the integrity, authenticity, selective disclosure and non-repudiation of the information contained in a JSON document. These properties make SD-JWT especially well suited to securing documents conforming to the JSON-LD [VC-DATA-MODEL].

Issue

The working group is discussing how we might comment on recent work, that does make use of encryption in OpenID for Verifiable Presentations.

CBOR Object Signing and Encryption (COSE) [RFC9052] is a specification that defines a framework for representing signed and encrypted data using (Concise Binary Object Representation) [RFC8949] data structures. COSE provides a standardized way to secure the integrity, authenticity, and confidentiality of CBOR-encoded information. It offers a flexible and extensible set of cryptographic options, allowing for a wide range of algorithms to be used for signing and encryption. COSE supports two main operations: signing and encryption. For signing, COSE allows the creation of digital signatures over CBOR data using various algorithms such as HMAC, RSA, ECDSA, or EdDSA. These signatures provide assurance of data integrity and authenticity. COSE also supports encryption, enabling the confidentiality of CBOR data by encrypting it with symmetric or asymmetric encryption algorithms.

2. Securing the VC Data Model

This section outlines how to secure documents conforming to the [VC-DATA-MODEL] using JOSE and COSE.

Documents conforming to the [VC-DATA-MODEL], and their associated media types, rely on JSON-LD, which is a flexible and extensible format for describing linked data, see JSON-LD Relationship to RDF.

A benefit to this approach is that payloads can be made to conform directly to the [VC-DATA-MODEL] without any mappings or transformation, while at the same time supporting registered claims that are understood in the context of JOSE and COSE.

It is RECOMMENDED that media types be used to distinguish verifiable credentials and verifiable presentations from other kinds of secured JSON or CBOR.

The most specific media type (or subtype) available SHOULD be used, instead of more generic media types (or supertypes). For example, rather than the general application/sd-jwt, application/vc+ld+json+sd-jwt ought to be used, unless there is a more specific media type that would even better identify the secured envelope format.

If implementations do not know which media type to use, media types defined in this specification MUST be used.

2.1 With JOSE

2.1.1 Securing JSON-LD Verifiable Credentials with JOSE

This section details how to use JOSE to secure verifiable credentials conforming to the [VC-DATA-MODEL].

[rfc7515] MAY be used to secure this media type.

The typ parameter SHOULD be vc+ld+json+sd-jwt

When present, the cty SHOULD be vc+ld+json

See Common JOSE Header Parameters for additional details regarding usage of typ and cty.

Example 1: Example Credential
{
  "@context": ["https://www.w3.org/ns/credentials/v2",
    "https://www.w3.org/ns/credentials/examples/v2"
  ],
  "id": "http://example.edu/credentials/3732",
  "type": ["VerifiableCredential",
    "UniversityDegreeCredential"
  ],
  "issuer": "https://example.edu/issuers/14",
  "issuanceDate": "2010-01-01T19:23:24Z",
  "credentialSubject": {
    "id": "did:example:123",
    "degree": {
      "type": "BachelorDegree",
      "name": "Bachelor of Science and Arts"
    }
  }
}
graph LR 0("VerifiableCredential") 1{{"id"}} 2("http://example.edu/credentials/3732") 3(("type")) 4("UniversityDegreeCredential") 5("issuer") 6("https://example.edu/issuers/14") 7("issuanceDate") 8("2010-01-01T19:23:24Z") 9("credentialSubject") 10{{"id"}} 11("did:example:123") 12("degree") 13(("type")) 14("BachelorDegree") 15("name") 16("Bachelor of Science and Arts") 0 --- 1 1 --- 2 0 --- 3 3 --- 4 0 --- 5 5 --- 6 0 --- 7 7 --- 8 0 --- 9 9 --- 10 10 --- 11 9 --- 12 12 --- 13 13 --- 14 12 --- 15 15 --- 16
---------------- Issuer Claims ----------------
"@context":
  - https://www.w3.org/ns/credentials/v2
  - https://www.w3.org/ns/credentials/examples/v2
!sd id: http://example.edu/credentials/3732
!sd type:
  - VerifiableCredential
  - UniversityDegreeCredential
issuer: https://example.edu/issuers/14
issuanceDate: 2010-01-01T19:23:24Z
credentialSubject:
  !sd id: did:example:123
  degree:
    !sd type: BachelorDegree
    name: Bachelor of Science and Arts
---------------- Holder Disclosure ----------------
issuer:
  id: True
credentialStatus:
  id: True
credentialSubject:
  id: True
  type: False
---------------- Decoded Protected Header ----------------
{
  "alg": "ES384"
}
---------------- Decoded Protected Claimset ----------------
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://www.w3.org/ns/credentials/examples/v2"
  ],
  "issuer": "https://example.edu/issuers/14",
  "issuanceDate": "2010-01-01T19:23:24Z",
  "credentialSubject": {
    "degree": {
      "name": "Bachelor of Science and Arts"
    },
    "id": "did:example:123"
  },
  "iss": "did:web:issuer.example",
  "iat": 1695246052,
  "exp": 1726868452,
  "cnf": {
    "jwk": {
      "kty": "EC",
      "crv": "P-384",
      "alg": "ES384",
      "x": "7KxWQ6BOiWsWmpAjtn93FVRsZ2Yipurh2SgfufGHi3uggIOfJglJibeXnMhqtCzB",
      "y": "24f2mNKHgm9fp7GffbrqDk5I-sl_hSjauSKlPjOwlCno0eDzFcuj0Q1auT_H4DaB"
    }
  }
}
---------------- Compact Encoded Selective Disclosure JSON Web Token ----------------
eyJhbGciOiJFUzM4NCJ9.eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiLCJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvZXhhbXBsZXMvdjIiXSwiaXNzdWVyIjoiaHR0cHM6Ly9leGFtcGxlLmVkdS9pc3N1ZXJzLzE0IiwiaXNzdWFuY2VEYXRlIjoiMjAxMC0wMS0wMVQxOToyMzoyNFoiLCJjcmVkZW50aWFsU3ViamVjdCI6eyJkZWdyZWUiOnsibmFtZSI6IkJhY2hlbG9yIG9mIFNjaWVuY2UgYW5kIEFydHMiLCJfc2QiOlsidU1PLUhvaUt0UDkyaUVZMENFcFhZQnhnczRhR1F3UXE1cThkZVc5RkhoOCJdfSwiX3NkIjpbIkhlWm1WVFR5TzFFdWFrNUgtVXdlakpaWlRIX0F3Yzc0QWtoQlhILWVnTWciXX0sIl9zZCI6WyJEZHRXcUtjM2c4MkowdTJyS29EMDRRMTJCaVJBUkNhdHU3d3dRX2RObHZJIiwiem9NVERBVldCRnh0anMySHprX2h1MDlHY2RVTDhHS29oWGNuNU5UWEVNVSJdLCJfc2RfYWxnIjoic2hhLTI1NiIsImlzcyI6ImRpZDp3ZWI6aXNzdWVyLmV4YW1wbGUiLCJpYXQiOjE2OTUyNDYwNTIsImV4cCI6MTcyNjg2ODQ1MiwiY25mIjp7Imp3ayI6eyJrdHkiOiJFQyIsImNydiI6IlAtMzg0IiwiYWxnIjoiRVMzODQiLCJ4IjoiN0t4V1E2Qk9pV3NXbXBBanRuOTNGVlJzWjJZaXB1cmgyU2dmdWZHSGkzdWdnSU9mSmdsSmliZVhuTWhxdEN6QiIsInkiOiIyNGYybU5LSGdtOWZwN0dmZmJycURrNUktc2xfaFNqYXVTS2xQak93bENubzBlRHpGY3VqMFExYXVUX0g0RGFCIn19fQ.tl14XL3LqoU5inw1Yh-sHSRJ1fTlgnFrTc5HWF6MhEfJh9vQ3dKhZAmu2U6IvzWE5m2UOTpB1tTDY5O7BYA2v_QSjEjno1mjo_Uypy-J6uWHnxvxiT7WMLYCxYP6fd5I~WyJ0NHlMNHpIQXU2QVEtYVZNR3RHcW53IiwgImlkIiwgImRpZDpleGFtcGxlOjEyMyJd~eyJhbGciOiJFUzM4NCIsInR5cCI6ImtiK2p3dCJ9.eyJub25jZSI6Ikh0X1oxbldrenEwazJkMmp0Und0RnciLCJhdWQiOiJkaWQ6d2ViOnZlcmlmaWVyLmV4YW1wbGUiLCJpYXQiOjE2OTUyNDYwNTJ9.Zk9WJjIfvC2QMEjMK4dWF_i3W3FfKCMCF7E1vub9XrwB8o8XzHBq15Sd-_BbZsETWMrBcAldEaT5SmPONjFv206WQJMC0RHkC75K2ZLGUQ6kRZ47yPIE1l0LgozZAn3a

2.1.2 Securing JSON-LD Verifiable Presentations with JOSE

This section details how to use JOSE to secure verifiable presentations conforming to the [VC-DATA-MODEL].

[rfc7515] MAY be used to secure this media type.

The typ parameter SHOULD be vp+ld+json+sd-jwt

When present, the cty parameter SHOULD be vp+ld+json

See Common JOSE Header Parameters for additional details regarding usage of typ and cty.

Example 2: The minimal unsecured verifiable presentation
{
  "@context": ["https://www.w3.org/ns/credentials/v2"],
  "type": ["VerifiablePresentation"]
}
graph LR 69("VerifiablePresentation")
+sd-jwt does not support algorithm none.
Example 3: The minimal secured verifiable presentation
{
  "@context": ["https://www.w3.org/ns/credentials/v2"],
  "type": ["VerifiablePresentation"]
}
graph LR 70("VerifiablePresentation")
---------------- Issuer Claims ----------------
"@context":
  - https://www.w3.org/ns/credentials/v2
!sd type:
  - VerifiablePresentation
---------------- Holder Disclosure ----------------
id: True
type: True
holder:
  id: True
---------------- Decoded Protected Header ----------------
{
  "alg": "ES384"
}
---------------- Decoded Protected Claimset ----------------
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2"
  ],
  "iss": "did:web:issuer.example",
  "iat": 1695246052,
  "exp": 1726868452,
  "cnf": {
    "jwk": {
      "kty": "EC",
      "crv": "P-384",
      "alg": "ES384",
      "x": "q7Qy9pfNpM7MAFeVjQkAVab0WTZaAQ0wOpkF2ekoZmsbGDYDozIYmo-KtnuSh0Gm",
      "y": "c_ciVbux9r6k9o0sgDfaD8G022W269qTKWQICAIzCWf0xu40WFdGP4hxB87Effy0"
    }
  },
  "type": [
    "VerifiablePresentation"
  ]
}
---------------- Compact Encoded Selective Disclosure JSON Web Token ----------------
eyJhbGciOiJFUzM4NCJ9.eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiXSwiX3NkIjpbInBlZGxkX29BMlMyRkEyV1ZfcnZHS3Q4bVZscEhXZmFJdzN2UjZUdmllcTQiXSwiX3NkX2FsZyI6InNoYS0yNTYiLCJpc3MiOiJkaWQ6d2ViOmlzc3Vlci5leGFtcGxlIiwiaWF0IjoxNjk1MjQ2MDUyLCJleHAiOjE3MjY4Njg0NTIsImNuZiI6eyJqd2siOnsia3R5IjoiRUMiLCJjcnYiOiJQLTM4NCIsImFsZyI6IkVTMzg0IiwieCI6InE3UXk5cGZOcE03TUFGZVZqUWtBVmFiMFdUWmFBUTB3T3BrRjJla29abXNiR0RZRG96SVltby1LdG51U2gwR20iLCJ5IjoiY19jaVZidXg5cjZrOW8wc2dEZmFEOEcwMjJXMjY5cVRLV1FJQ0FJekNXZjB4dTQwV0ZkR1A0aHhCODdFZmZ5MCJ9fX0.Q2Op8exdbVTl_4iEKQ6nsHX9hxtwGPCznAkveHSrNs6f3r9VwcIEy5saLwq2CA0QoOvmsmvaLqQa6vd2kQRV2P71AzYRa2o20Lixqo3FeKohPEV2B9Y4H2T4XqgtZSDc~WyJhWlFpZVhZYjNQbzFLaTg0a05jeVhnIiwgInR5cGUiLCBbIlZlcmlmaWFibGVQcmVzZW50YXRpb24iXV0~eyJhbGciOiJFUzM4NCIsInR5cCI6ImtiK2p3dCJ9.eyJub25jZSI6Ino0dHI4MzVXWll2ZkdPeFhFSVA2OXciLCJhdWQiOiJkaWQ6d2ViOnZlcmlmaWVyLmV4YW1wbGUiLCJpYXQiOjE2OTUyNDYwNTJ9.jPhSGaFOeo1lq57LUb5Zp49tegMi6-qZ4WKUixZ2UroL8LYX23o70KeTxUYyJMOUF8N3MsZ--Xsz_73jRXqY-Sh7_kKkve3IX9dXxqpvuKKDKBmjkD0lQEdDJDzDC299
Example 4: A secured verifiable presentation with a holder identifier
{
  "@context": ["https://www.w3.org/ns/credentials/v2",
    "https://www.w3.org/ns/credentials/examples/v2"
  ],
  "type": ["VerifiablePresentation"],
  "holder": "urn:ietf:params:oauth:jwk-thumbprint:sha-256:NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs"
}
graph LR 71("VerifiablePresentation") 72("holder") 73("urn:ietf:params:oauth:jwk-thumbprint:sha-256:NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs") 71 --- 72 72 --- 73
---------------- Issuer Claims ----------------
"@context":
  - https://www.w3.org/ns/credentials/v2
  - https://www.w3.org/ns/credentials/examples/v2
!sd type:
  - VerifiablePresentation
holder: urn:ietf:params:oauth:jwk-thumbprint:sha-256:NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs
---------------- Holder Disclosure ----------------
id: True
type: True
holder:
  id: True
---------------- Decoded Protected Header ----------------
{
  "alg": "ES384"
}
---------------- Decoded Protected Claimset ----------------
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://www.w3.org/ns/credentials/examples/v2"
  ],
  "holder": "urn:ietf:params:oauth:jwk-thumbprint:sha-256:NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs",
  "iss": "did:web:issuer.example",
  "iat": 1695246052,
  "exp": 1726868452,
  "cnf": {
    "jwk": {
      "kty": "EC",
      "crv": "P-384",
      "alg": "ES384",
      "x": "i7-KtqQkRpNDk7SDkgMw_MjG85LA57KKmQb7exlu10k8tWXIEth_yigTC4Cx0A10",
      "y": "AtbstV1ii-xgK9GIdgX6Ijg034rV20vjFQZvN_sVbTdkEL-JextwNCM4y-dBhwvE"
    }
  },
  "type": [
    "VerifiablePresentation"
  ]
}
---------------- Compact Encoded Selective Disclosure JSON Web Token ----------------
eyJhbGciOiJFUzM4NCJ9.eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiLCJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvZXhhbXBsZXMvdjIiXSwiaG9sZGVyIjoidXJuOmlldGY6cGFyYW1zOm9hdXRoOmp3ay10aHVtYnByaW50OnNoYS0yNTY6TnpiTHNYaDh1RENjZC02TU53WEY0V183bm9XWEZaQWZIa3hac1JHQzlYcyIsIl9zZCI6WyJYcWpvRElsV2ZsbXNwZDRYWDhFaWpMRVhYa1NDanE5Wnk1QmhYdnFjQkZNIl0sIl9zZF9hbGciOiJzaGEtMjU2IiwiaXNzIjoiZGlkOndlYjppc3N1ZXIuZXhhbXBsZSIsImlhdCI6MTY5NTI0NjA1MiwiZXhwIjoxNzI2ODY4NDUyLCJjbmYiOnsiandrIjp7Imt0eSI6IkVDIiwiY3J2IjoiUC0zODQiLCJhbGciOiJFUzM4NCIsIngiOiJpNy1LdHFRa1JwTkRrN1NEa2dNd19Nakc4NUxBNTdLS21RYjdleGx1MTBrOHRXWElFdGhfeWlnVEM0Q3gwQTEwIiwieSI6IkF0YnN0VjFpaS14Z0s5R0lkZ1g2SWpnMDM0clYyMHZqRlFadk5fc1ZiVGRrRUwtSmV4dHdOQ000eS1kQmh3dkUifX19.y9b7Q7Zxh9nhAfR0BZx5OcdBaO7JiMv6LMUVDTCwuBfYx4d5fVEldsHrx7cT15dyioBFUnlNeWeSoez28op5g2pKlcgGAQ906Qgo-ODQuhEcig4v63Mdmjtwmzlu8ugL~WyI2V2hmbS0yMWFLbVI2c05hZUdBWldRIiwgInR5cGUiLCBbIlZlcmlmaWFibGVQcmVzZW50YXRpb24iXV0~eyJhbGciOiJFUzM4NCIsInR5cCI6ImtiK2p3dCJ9.eyJub25jZSI6ImhFQjYtYzIzVjJOVkNVYWdkb2hfQlEiLCJhdWQiOiJkaWQ6d2ViOnZlcmlmaWVyLmV4YW1wbGUiLCJpYXQiOjE2OTUyNDYwNTJ9.ID75qDdCgKjMzaGoV9PTyeEpCEdeqBMUTmzLpgEtdgrXpqcWXpcghwE7T8j7ozDthomontGRavQTU6SgXqyA3aA2sxQLmHWfRvZNDUvnIBOo5APKH_FGodkXntjsOsZZ
Example 5: A secured verifiable presentation with a holder graph node
{
  "@context": ["https://www.w3.org/ns/credentials/v2"],
  "type": ["VerifiablePresentation"],
  "holder": {
    "id": "urn:ietf:params:oauth:jwk-thumbprint:sha-256:NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs",
    "type": "Organization",
    "name": "Contoso"
  }
}
graph LR 74("VerifiablePresentation") 75("holder") 76{{"id"}} 77("urn:ietf:params:oauth:jwk-thumbprint:sha-256:NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs") 78(("type")) 79("Organization") 80("name") 81("Contoso") 74 --- 75 75 --- 76 76 --- 77 75 --- 78 78 --- 79 75 --- 80 80 --- 81
---------------- Issuer Claims ----------------
"@context":
  - https://www.w3.org/ns/credentials/v2
!sd type:
  - VerifiablePresentation
holder:
  !sd id: urn:ietf:params:oauth:jwk-thumbprint:sha-256:NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs
  !sd type: Organization
  name: Contoso
---------------- Holder Disclosure ----------------
id: True
type: True
holder:
  id: True
---------------- Decoded Protected Header ----------------
{
  "alg": "ES384"
}
---------------- Decoded Protected Claimset ----------------
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2"
  ],
  "holder": {
    "name": "Contoso",
    "id": "urn:ietf:params:oauth:jwk-thumbprint:sha-256:NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs"
  },
  "iss": "did:web:issuer.example",
  "iat": 1695246052,
  "exp": 1726868452,
  "cnf": {
    "jwk": {
      "kty": "EC",
      "crv": "P-384",
      "alg": "ES384",
      "x": "CPK1d2L7Pdmb5dmFc9Mf5NZ78bVMPCHlGc2oM5-trOGj6Db_7vwXrSTA3CAg-MIC",
      "y": "UoKO4lNs4TT9-HTTKwE4soOeL2LJI5Z7Gj8nvp7efV-0bVpaRBcIZ8805x9heNkK"
    }
  },
  "type": [
    "VerifiablePresentation"
  ]
}
---------------- Compact Encoded Selective Disclosure JSON Web Token ----------------
eyJhbGciOiJFUzM4NCJ9.eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiXSwiaG9sZGVyIjp7Im5hbWUiOiJDb250b3NvIiwiX3NkIjpbIi1uVTZSUi0xQ0QyRk9icTlsVVpEVEtScXNlVDM5MmQ0VHF3QzVqaXhaUXciLCJpQ3dJS0lESXdZYWNTQWZ0MEtGdVRYZktkMGFhQkdiN0NxWThpVGVLUV93Il19LCJfc2QiOlsiZjlVajEyZUFOcGh3MFJYdk1YSnZfTUVHcjBvMFdHcjhmSjhqUWNRUm1UQSJdLCJfc2RfYWxnIjoic2hhLTI1NiIsImlzcyI6ImRpZDp3ZWI6aXNzdWVyLmV4YW1wbGUiLCJpYXQiOjE2OTUyNDYwNTIsImV4cCI6MTcyNjg2ODQ1MiwiY25mIjp7Imp3ayI6eyJrdHkiOiJFQyIsImNydiI6IlAtMzg0IiwiYWxnIjoiRVMzODQiLCJ4IjoiQ1BLMWQyTDdQZG1iNWRtRmM5TWY1Tlo3OGJWTVBDSGxHYzJvTTUtdHJPR2o2RGJfN3Z3WHJTVEEzQ0FnLU1JQyIsInkiOiJVb0tPNGxOczRUVDktSFRUS3dFNHNvT2VMMkxKSTVaN0dqOG52cDdlZlYtMGJWcGFSQmNJWjg4MDV4OWhlTmtLIn19fQ.JCZwgG0B46WzfQD6u2uvwRyRAQWyHwNBEl2iJJYqzDAd5dYbiH9ROM2_WqfERtEyj-wS2w1-hEZteAyXDz9iZcFt3va5jRdDPXkBnomRfsTdJMtyY1mb1Xdmm3sucHqv~WyJad1ZlTVZIdXhIb1VZRkU1cVpsUUV3IiwgImlkIiwgInVybjppZXRmOnBhcmFtczpvYXV0aDpqd2stdGh1bWJwcmludDpzaGEtMjU2Ok56YkxzWGg4dURDY2QtNk1Od1hGNFdfN25vV1hGWkFmSGt4WnNSR0M5WHMiXQ~WyJBbUFGN0xhS1cxMldxZ0lwaUZCRURBIiwgInR5cGUiLCBbIlZlcmlmaWFibGVQcmVzZW50YXRpb24iXV0~eyJhbGciOiJFUzM4NCIsInR5cCI6ImtiK2p3dCJ9.eyJub25jZSI6IngtdnNIdHl3SGdneDBpazh0bS03NGciLCJhdWQiOiJkaWQ6d2ViOnZlcmlmaWVyLmV4YW1wbGUiLCJpYXQiOjE2OTUyNDYwNTJ9.jbGLEspt40-nKY23GZad5F93-ohpi4zmJ-vXXRqb_btQVUs8w7A_2u9I2ATq33azESMvTtYgltrHM9GZqQ_cslk8ba1qbcrW-tYqH_na_TaiIDLQniobe_dtANio8fJW

2.2 With COSE

COSE [rfc9052] is a common approach to encoding and securing information using CBOR [rfc8949]. Verifiable credentials MAY be secured using COSE [rfc9052] and SHOULD be identified through use of content types as outlined in this section.

2.2.1 Securing JSON-LD VCs with COSE

This section details how to secure data with the type application/vc+ld+json with COSE.

[rfc9052] MAY be used to secure this media type.

When using this approach, the typ SHOULD be vc+ld+json+cose. See I-D.ietf-cose-typ-header-parameter for the COSE "typ" (type) header parameter.

When using this approach, the content type (3) SHOULD be application/vc+ld+json

See Common COSE Header Parameters for additional details.

See Concise Binary Object Representation (CBOR) Tags for additional details.

3. Wallets

This section is non-normative.

Issuers, holders and verifiers might rely on clients, as defined in RFC4949. Such clients are often referred to as wallets or digital credential wallets, when they support storing and presenting digital credentials.

In order to meet verifier requirements, some issuers might need to assess the quality of a wallet used by a holder, prior to issuing and delivering credentials to a holder.

For example, some verifiers might require that cryptographic material associated with a holder, be protected at specific assurance levels. (See NIST 800-63-3: Authenticator Assurance Levels.)

Note

Also see OAuth 2.0 Attestation-Based Client Authentication .

4. Key Discovery

Issue

The working group is still discussing how to close many related issues.

Issue 117: how is `kid` to be `useful to distinguish the specific key used`? has-prbefore-CR

Originally posted by @TallTed in #111 (comment)

line 377 says (and another line says the same) --

If <code>kid</code> is also present, it is expected to be useful to distinguish the specific key used.

-- in response to which I ask --

how is kid to be useful to distinguish the specific key used? This cries out for an example, or a fair amount of additional prose.

Issue 106: Explain relationship between controller documents and JOSE headers has-prbefore-CR
          Just read that section, and I have to say that it's not intuitive at all. I think it would be worth either: adding an example that refers to this controller document, pointing to the spec you mentioned, or explicitly stating the relationship between controller docs and  `iss` & `kid`.

Originally posted by @andresuribe87 in #104 (comment)

Issue 31: About the optionality of the "kid" field in JWT-formatted VCs/VPs has-prbefore-CR

https://www.w3.org/TR/vc-data-model/#jwt-encoding shows:

kid MAY be used if there are multiple keys associated with the issuer of the JWT. The key discovery is out of the scope of this specification. For example, the kid can refer to a key in a DID document, or can be the identifier of a key inside a JWKS.

I'd like some clarification on the optionality of the "kid" field. My guess is that VCs/VPs are trying to be generic regarding issuers/holders, allowing for URIs, which precludes the possibility of giving any more details about how the "kid" field should be used. Is that right?

I'm coming from a DID-centric ecosystem, and in that scenario it seems that there's no reason not to set the "kid" field on a JWT-formatted VC/VP to the DID fragment URL of the specific key used to sign. From w3c/vc-data-model#914 I understand that it would still be necessary to tie the "kid" to the "iss" field, but that seems fine.

As far as I can tell, if the "kid" field is missing, and assuming we're working with DIDs here, the process to resolve the signing key has to be:

To me, this seems sloppy, involving unnecessary complexity and computation, and making detecting errors in implementations harder. It also wouldn't scale if for whatever reason a DID had very many keys (inefficient at best, possible DoS at worst). Maybe I'm missing something here. Can anyone comment on this? Thanks.

Issue 30: Accept or Dismiss the guidance provided by DIF on `kid` / `iss` discusshas-prbefore-CR

See https://github.com/decentralized-identity/did-jose-extensions/blob/master/options.md

^ this guidance is ancient, I believe we can do better.

cc @tplooker @selfissued @Sakurann @dwaite

Issue 15: Describe why core data model members are translated to JWT claims pending-close

Can we add an explanation why do these members need to be translated to the equivalents of the JWT claims?
iss, nbf, all of them are optional in RFC 7519 itself. They only become required when the JWT is used for a specific purpose, and the only place I can think of right now is an ID Token.

See: #11 (comment)

In order to complete the verification process, a verifier needs to obtain the cryptographic keys used to secure the credential.

There are several different ways to discover the verification keys of the issuers and holders.

4.1 Registered Claim Names

When found in the Protected Header, or the Protected Claimset, members present in IANA Assignments for JSON Web Token (JWT) and IANA Assignments for JSON Object Signing and Encryption (JOSE) are to be interpreted according to the associated specifications referenced by IANA.

Registered claims that are present in either the Protected Header or the Claimset can be used to help verifiers discover verification keys.

4.1.1 kid

If kid is present in the Protected Header, a verifier can use this parameter as a hint indicating which key was used to secure the verifiable credential, when performing a verification process as defined in RFC7515.

kid MUST be present when the key of the issuer or subject is expressed as a DID URL.

4.1.2 iss

If iss is present in the Protected Header or the JWT Claims , a verifier can use this parameter to obtain a JSON Web Key to use in the verification process.

The value of the issuer property can be either a string or an object. When issuer value is a string, iss value, if present, MUST match issuer value. When issuer value is an object with an id value, iss value, if present, MUST match issuer.id value.

If kid is also present in the Protected Header, it is expected to be useful to distinguish the specific key used.

Issue 31: About the optionality of the "kid" field in JWT-formatted VCs/VPs has-prbefore-CR

There are a few issues related to clarification of optionality and behavior of registered claims.

4.1.3 cnf

If cnf is present in the Protected Header or the JWT Claims , a verifier MAY use this parameter to identify a proof-of-possesion key in the manner described in [rfc7800] for use in the verification process.

4.2 Well Known URIs

Issue

The working group is currently exploring how Defining Well-Known Uniform Resource Identifiers (URIs) could be leveraged to assist a verifier in discovering verification keys for issuers and holders.

4.2.1 JWT Issuer

When the issuer value is a URL using the HTTPS scheme, issuer metadata including the issuer's public keys can be retrieved using the mechanism defined in SD-JWT-based Verifiable Credentials (SD-JWT VC).

5. Protected Header Parameters

The normative statements in Registered Header Parameter Names apply to securing credentials and presentations.

The normative statements in JOSE Header apply to securing credentials and presentations.

The data model for the protected header is JSON (application/json), not JSON-LD (application/ld+json).

The normative statements in Replicating Claims as Header Parameters apply to securing claims about a credential subject.

When replicating claims from the claimset to the header, it is RECOMMENDED to use [RFC7519], IANA Assignments for Header Parameters, and IANA Assignments for JSON Web Token (JWT) to identify any reserved claims that might be confused with members of the [[VC-DATA-MODEL]. This includes but is not limited to: iss, kid, alg, iat, exp and cnf.

When the iat and/or exp JWT claims are present, they represent the issuance and expiration time of the signature, respectively. Note that these are different from the validFrom and validUntil properties defined in Validity Period that represent the validity of the data that is being secured.

The registered claim names vc and vp MUST NOT be present as header parameters.

When present, members of the header are to be interpreted and processed according to IANA Assignments for JSON Web Token (JWT) and IANA Assignments for JSON Object Signing and Encryption (JOSE).

Additional members may be present, if they are not understood, they MUST be ignored.

6. Conformance

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The key words MAY, MUST, MUST NOT, RECOMMENDED, and SHOULD in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

6.1 Securing Verifiable Credentials

The Verifiable Credentials Data Model v1.1 describes the approach taken by JSON Web Tokens to secure claimsets as applying an external proof.

The normative statements in Securing Verifiable Credentials apply to securing application/vc+ld+json and application/vp+ld+json as application/vc+ld+json+sd-jwt and application/vp+ld+json+sd-jwt.

For clarity, these requirements are repeated here:

The type VerifiableCredential and VerifiablePresentation are RDF Classes.

The presence of the word "Verifiable" does not convey a cryptographic verification capability exists.

The presence of the JSON proof member does not convey a cryptographic verification capability exists.

The presence of the JSON proof member is optional in both VerifiableCredential and VerifiablePresentation.

The presence of the JSON proof member is optional in both application/vc+ld+json and application/vp+ld+json.

JSON Web Token implementers are advised to review Implementation Requirements.

Accordingly, Issuers, Holders and Verifiers MUST understand the JSON Web Token header parameter "alg": "none" when securing the [VC-DATA-MODEL] with JSON Web Tokens.

When content types from the [VC-DATA-MODEL] are secured using JSON Web Tokens, the header parameter "alg": "none", MUST be used to communicate that a claimset (a Verifiable Credential or a Verifiable Presentation) has no integrity protection.

When a JSON Web Token claimset (a Verifiable Credential or a Verifiable Presentation) contains proof, and the JSON Web Token header contains "alg": "none", the claimset MUST be considered to have no integrity protection.

Verifiable Credentials and Verifiable Presenatations are not required to be secured or integrity protected or to contain a proof member.

Issuers, Holders and Verifiers MUST ignore all claimsets that have no integrity protection.

7. IANA Considerations

7.1 Media Types

7.1.1 application/vc+ld+json+sd-jwt

This specification registers the application/vc+ld+json+sd-jwt Media Type specifically for identifying a Selective Disclosure for JWTs (SD-JWT) conforming to the Verifiable Credential Data Model.

Type name: application
Subtype name: vc+ld+json+sd-jwt
Required parameters: None
Encoding considerations: binary; application/sd-jwt values are a series of base64url-encoded values (some of which may be the empty string) separated by period ('.') or tilde ('~') characters.
Security considerations:

As defined in this specification. See also the security considerations in Selective Disclosure for JWTs (SD-JWT).

Contact: W3C Verifiable Credentials Working Group public-vc-wg@w3.org

7.1.2 application/vp+ld+json+sd-jwt

This specification registers the application/vp+ld+json+sd-jwt Media Type specifically for identifying a Selective Disclosure for JWTs (SD-JWT) conforming to the Verifiable Presentations.

Type name: application
Subtype name: vp+ld+json+sd-jwt
Required parameters: None
Encoding considerations: binary; application/sd-jwt values are a series of base64url-encoded values (some of which may be the empty string) separated by period ('.') or tilde ('~') characters.
Security considerations:

As defined in this specification. See also the security considerations in Selective Disclosure for JWTs (SD-JWT).

Contact: W3C Verifiable Credentials Working Group public-vc-wg@w3.org

7.2 Registered Claims

This section retains deprecated registered claim names that were previously submitted to the Internet Engineering Steering Group (IESG) for review, approval, and registration with IANA in the "JSON Web Token Claims Registry".

Issue 119: Deprecate `vc` & `vp` ?

These are registered claims at:

As it says, the change controller is IESG, but it references v1.0 of the data model, specifically:

In v2, we removed these from the core data model, and we removed them from this specification.

Should we tell the IESG to update the registry in any way?

7.2.1 vc

Claim Name: "vc"
Claim Description: Verifiable Credential
Change Controller: W3C
Specification Document(s): Section 6.3.1.2: JSON Web Token Extensions of Verifiable Credentials Data Model 1.0

7.2.2 vp

Claim Name: "vp"
Claim Description: Verifiable Presentation
Change Controller: W3C
Specification Document(s): Section 6.3.1.2: JSON Web Token Extensions of Verifiable Credentials Data Model 1.0

8. Other Considerations

8.1 Privacy Considerations

Verifiable Credentials often contain sensitive information that needs to be protected to ensure the privacy and security of organizations and individuals. This section outlines some privacy considerations relevant to implementers and users.

Implementers are advised to note and abide by all privacy considerations called out in the [VC-DATA-MODEL].

Implementers are additionally advised to reference the Privacy Consideration section of the JWT specification for privacy guidance.

In addition to the privacy recommendations in the [VC-DATA-MODEL], the following considerations are given:

These considerations are not exhaustive, and implementers and users are advised to consult additional privacy resources and best practices to ensure the privacy and security of Verifiable Credentials implemented using VC-JWT.

8.2 Security Considerations

This section outlines security considerations for implementers and users of this specification. It is important to carefully consider these factors to ensure the security and integrity of Verifiable Credentials when implemented using JWTs.

When implementing VC-JWTs, it is essential to address all security issues relevant to broad cryptographic applications. This especially includes protecting the user's asymmetric private and symmetric secret keys, as well as employing countermeasures against various attacks. Failure to adequately address these issues could compromise the security and integrity of Verifiable Credentials, potentially leading to unauthorized access, modification, or disclosure of sensitive information.

Implementers are advised to follow best practices and established cryptographic standards to ensure the secure handling of keys and other sensitive data. Additionally, conduct regular security assessments and audits to identify and address any vulnerabilities or threats.

Follow all security considerations outlined in [rfc7515] and [rfc7519].

When utilizing JSON-LD, take special care around remote retrieval of contexts and follow the additional security considerations noted in [json-ld11].

As noted in [rfc7515] when utilizing JSON [rfc7159], strict validation is a security requirement. If malformed JSON is received, it may be impossible to reliably interpret the producer's intent, potentially leading to ambiguous or exploitable situations. To prevent these risks, it is essential to use a JSON parser that strictly validates the syntax of all input data. It is essential that any JSON inputs that do not conform to the JSON-text syntax defined in [rfc7159] be rejected in their entirety by JSON parsers. Failure to reject invalid input could compromise the security and integrity of Verifiable Credentials.

8.3 Accessibility

This section is non-normative.

When implementing this specification, it is crucial for technical implementers to consider various accessibility factors. Ignoring accessibility concerns renders the information unusable for a significant portion of the population. To ensure equal access for all individuals, regardless of their abilities, it is vital to adhere to accessibility guidelines and standards, such as the Web Content Accessibility Guidelines (WCAG 2.1) [WCAG21]. This becomes even more critical when establishing systems that involve cryptography, as they have historically posed challenges for assistive technologies.

Implementers are advised to note and abide by all accessibility considerations called out in the [VC-DATA-MODEL].

8.4 Internationalization

This section is non-normative.

Implementers should take into account several internationalization considerations when publishing data described in this specification. Disregarding internationalization hampers the production and consumption of data across diverse languages and societies, thereby restricting the applicability and significantly reducing the value of the specification as a standard.

Implementers are advised to note and abide by all internationalization considerations called out in the [VC-DATA-MODEL], see also i18n, URL Standard

9. Appendix

This section is non-normative.

9.1 Controllers

Example 6: A verifiable credential controller document
{
  "@context": ["https://www.w3.org/ns/did/v1", {
    "@vocab": "https://vendor.example#"
  }],
  "id": "did:web:vendor.example",
  "alsoKnownAs": ["https://vendor.example",
    "did:jwk:eyJraWQiOiJ1cm46aWV0ZjpwYXJhbXM6b2F1dGg6andrLXRodW1icHJpbnQ6c2hhLTI1NjpGZk1iek9qTW1RNGVmVDZrdndUSUpqZWxUcWpsMHhqRUlXUTJxb2JzUk1NIiwia3R5IjoiT0tQIiwiY3J2IjoiRWQyNTUxOSIsImFsZyI6IkVkRFNBIiwieCI6IkFOUmpIX3p4Y0tCeHNqUlBVdHpSYnA3RlNWTEtKWFE5QVBYOU1QMWo3azQifQ"
  ],
  "verificationMethod": [{
    "id": "#urn:ietf:params:oauth:jwk-thumbprint:sha-256:NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs",
    "type": "JsonWebKey",
    "controller": "did:web:vendor.example",
    "publicKeyJwk": {
      "kty": "EC",
      "crv": "P-521",
      "alg": "ES512",
      "x": "AFTyMw-fIYJNg6fBVJvOPOsLxmnNj8HgqMChyRL0swLaefVAc7wrWZ8okQJqMmvv03JRUp277meQZM3JcvXFkH1v",
      "y": "ALn96CrD88b4TClmkl1sk0xk2FgAIda97ZF8TUOjbeWSzbKnN2KB6pqlpbuJ2xIRXvsn5BWQVlAT2JGpGwDNMyV1"
    }
  }, {
    "id": "#z6MkhEdpG12jyQegrr62ACRmNY8gc531W2j9Xo39cHphuCEH",
    "type": "JsonWebKey2020",
    "controller": "https://vendor.example",
    "publicKeyJwk": {
      "kid": "urn:ietf:params:oauth:jwk-thumbprint:sha-256:FfMbzOjMmQ4efT6kvwTIJjelTqjl0xjEIWQ2qobsRMM",
      "kty": "OKP",
      "crv": "Ed25519",
      "alg": "EdDSA",
      "x": "ANRjH_zxcKBxsjRPUtzRbp7FSVLKJXQ9APX9MP1j7k4"
    }
  }, {
    "id": "#subject-authenticaton",
    "type": "JsonWebKey",
    "controller": "did:web:vendor.example",
    "publicKeyJwk": {
      "kty": "EC",
      "crv": "P-384",
      "alg": "ES384",
      "x": "PxgAmVYOQvSNcMYL2tOzoLwSWn4Ta3tIMPEUKR8pxeb-gmR11-DyKHBoIiY-2LhM",
      "y": "BZEBTkImVdpwvxR9THIRw16eblnj5-tZa7m-ww5uVd4kyPJNRoWUn2aT9ZuarAe-"
    }
  }, {
    "id": "#credential-issuance",
    "type": "JsonWebKey",
    "controller": "did:web:vendor.example",
    "publicKeyJwk": {
      "kty": "EC",
      "crv": "P-256",
      "alg": "ES256",
      "x": "MYvnaI87pfrn3FpTqW-yNiFcF1K7fedJiqapm20_q7c",
      "y": "9YEbT6Tyuc7xp9yRvhOUVKK_NIHkn5HpK9ZMgvK5pVw"
    }
  }, {
    "id": "#key-agreement",
    "type": "JsonWebKey",
    "controller": "did:web:vendor.example",
    "publicKeyJwk": {
      "kty": "OKP",
      "crv": "X25519",
      "alg": "ECDH-ES+A128KW",
      "x": "qLZkSTbstvMWPTivmiQglEFWG2Ff7gNDVoVisdZTr1I"
    }
  }],
  "authentication": ["#subject-authenticaton"],
  "assertionMethod": ["#credential-issuance"],
  "keyAgreement": ["#key-agreement"]
}

9.2 Credentials

Example 7: A revocable credential with multiple subjects
{
  "@context": ["https://www.w3.org/ns/credentials/v2",
    "https://www.w3.org/ns/credentials/examples/v2"
  ],
  "id": "https://contoso.example/credentials/23894672394",
  "type": ["VerifiableCredential", "K9UnitCredential"],
  "issuer": {
    "id": "https://contoso.example"
  },
  "validFrom": "2015-04-16T05:11:32.432Z",
  "credentialStatus": {
    "id": "https://contoso.example/credentials/status/4#273762",
    "type": "StatusList2021Entry",
    "statusPurpose": "revocation",
    "statusListIndex": "273762",
    "statusListCredential": "https://contoso.example/credentials/status/4"
  },
  "credentialSubject": [{
    "id": "did:example:1312387641",
    "type": "Person"
  }, {
    "id": "did:example:63888231",
    "type": "Dog"
  }]
}
graph LR 17("VerifiableCredential") 18{{"id"}} 19("https://contoso.example/credentials/23894672394") 20(("type")) 21("K9UnitCredential") 22("issuer") 23{{"id"}} 24("https://contoso.example") 25("validFrom") 26("2015-04-16T05:11:32.432Z") 27("credentialStatus") 28{{"id"}} 29("https://contoso.example/credentials/status/4#273762") 30(("type")) 31("StatusList2021Entry") 32("statusPurpose") 33("revocation") 34("statusListIndex") 35("273762") 36("statusListCredential") 37("https://contoso.example/credentials/status/4") 38("credentialSubject") 39{{"id"}} 40("did:example:1312387641") 41(("type")) 42("Person") 43("credentialSubject") 44{{"id"}} 45("did:example:63888231") 46(("type")) 47("Dog") 17 --- 18 18 --- 19 17 --- 20 20 --- 21 17 --- 22 22 --- 23 23 --- 24 17 --- 25 25 --- 26 17 --- 27 27 --- 28 28 --- 29 27 --- 30 30 --- 31 27 --- 32 32 --- 33 27 --- 34 34 --- 35 27 --- 36 36 --- 37 17 --- 38 38 --- 39 39 --- 40 38 --- 41 41 --- 42 17 --- 43 43 --- 44 44 --- 45 43 --- 46 46 --- 47
---------------- Issuer Claims ----------------
"@context":
  - https://www.w3.org/ns/credentials/v2
  - https://www.w3.org/ns/credentials/examples/v2
!sd id: https://contoso.example/credentials/23894672394
!sd type:
  - VerifiableCredential
  - K9UnitCredential
issuer:
  !sd id: https://contoso.example
validFrom: 2015-04-16T05:11:32.432Z
credentialStatus:
  !sd id: https://contoso.example/credentials/status/4#273762
  !sd type: StatusList2021Entry
  statusPurpose: revocation
  statusListIndex: "273762"
  statusListCredential: https://contoso.example/credentials/status/4
credentialSubject:
  - !sd id: did:example:1312387641
    !sd type: Person
  - !sd id: did:example:63888231
    !sd type: Dog
---------------- Holder Disclosure ----------------
id: False
type: True
issuer:
  id: True
credentialStatus:
  id: True
---------------- Decoded Protected Header ----------------
{
  "alg": "ES256",
  "typ": "vc+ld+json+sd-jwt",
  "cty": "vc+ld+json"
}
---------------- Decoded Protected Claimset ----------------
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://www.w3.org/ns/credentials/examples/v2"
  ],
  "issuer": {
    "id": "https://contoso.example"
  },
  "validFrom": "2015-04-16T05:11:32.432Z",
  "credentialStatus": {
    "statusPurpose": "revocation",
    "statusListIndex": "273762",
    "statusListCredential": "https://contoso.example/credentials/status/4",
    "id": "https://contoso.example/credentials/status/4#273762"
  },
  "credentialSubject": [
    {},
    {}
  ],
  "iss": "did:web:issuer.example",
  "iat": 1695246052,
  "exp": 1726868452,
  "cnf": {
    "jwk": {
      "kty": "EC",
      "crv": "P-256",
      "alg": "ES256",
      "x": "6D3E1J0oYUU2MTIqmDCRjZhpmnkBOs0PCUUJ4rq6L0E",
      "y": "t6EkGRmMrTJ8oo7_AyWAfqWRu9RK4-GDeDxfrrG5vUU"
    }
  },
  "type": [
    "VerifiableCredential",
    "K9UnitCredential"
  ]
}
---------------- Compact Encoded Selective Disclosure JSON Web Token ----------------
eyJhbGciOiJFUzI1NiIsInR5cCI6InZjK2xkK2pzb24rc2Qtand0IiwiY3R5IjoidmMrbGQranNvbiJ9.eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiLCJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvZXhhbXBsZXMvdjIiXSwiaXNzdWVyIjp7Il9zZCI6WyIycHN0RklGd0UzUU9NWHJibkJZZlVSaUd3X0hrWlhyc1Ewdkl5XzZKcEhJIl19LCJ2YWxpZEZyb20iOiIyMDE1LTA0LTE2VDA1OjExOjMyLjQzMloiLCJjcmVkZW50aWFsU3RhdHVzIjp7InN0YXR1c1B1cnBvc2UiOiJyZXZvY2F0aW9uIiwic3RhdHVzTGlzdEluZGV4IjoiMjczNzYyIiwic3RhdHVzTGlzdENyZWRlbnRpYWwiOiJodHRwczovL2NvbnRvc28uZXhhbXBsZS9jcmVkZW50aWFscy9zdGF0dXMvNCIsIl9zZCI6WyJHNjhmY3pZZlc0TDZMV0pSUlpfNEdCQWd2LTRzeFhMS2V6ellfSUpfRzM4IiwiV0VXSGdxLVdrOGdhVFJLb0M0V2t2TU8wXzVaNmRrSWxnU3M5VFdfaVNKOCJdfSwiY3JlZGVudGlhbFN1YmplY3QiOlt7Il9zZCI6WyJMRzFPQ09aTFlGQTl5bXQ2a1o1MmhaVWQ5eXRNRWgxTk1EUlFBUmFTNTNzIiwiYWw2SW9TZ1phU0QtTW4wS0tsenRFZ2V0aUJpb2RiSkY1bk9RUm9xTHJ0USJdfSx7Il9zZCI6WyI1V2ZOUXdpZjV4MGZTZ3BFdkxab0g0MmM4NlE3U29sWG9fLWNoR1M0RU8wIiwidWFaQUFhdEczYzdzWEkxRW1NbXV0UW1FbmttSUtfYTRqRXdtZ2JtOEN0cyJdfV0sIl9zZCI6WyJFd1FPU01tRk9tMzY0eDlWOFZGNkdVQ2VHczFiT1E1ZGNZcnNZZndLVmhjIiwiZHY3aXo1QldnYnNvMFdDU2RDbFFReFFCMGtCdUtidDlOS3g0aHYyTWEwOCJdLCJfc2RfYWxnIjoic2hhLTI1NiIsImlzcyI6ImRpZDp3ZWI6aXNzdWVyLmV4YW1wbGUiLCJpYXQiOjE2OTUyNDYwNTIsImV4cCI6MTcyNjg2ODQ1MiwiY25mIjp7Imp3ayI6eyJrdHkiOiJFQyIsImNydiI6IlAtMjU2IiwiYWxnIjoiRVMyNTYiLCJ4IjoiNkQzRTFKMG9ZVVUyTVRJcW1EQ1JqWmhwbW5rQk9zMFBDVVVKNHJxNkwwRSIsInkiOiJ0NkVrR1JtTXJUSjhvbzdfQXlXQWZxV1J1OVJLNC1HRGVEeGZyckc1dlVVIn19fQ.TavBRJCR5TQphTmMtQavaaXK56n1YXcikAGA1CSQKQMT9rtaIE-bOukDabp4bDKmIzKCLCT25hbjLZ9zHBJI8w~WyJvRHpyWUY1NmVORXFNc3JwLUU3VnZRIiwgImlkIiwgImh0dHBzOi8vY29udG9zby5leGFtcGxlIl0~WyJVYUNXdk5lT0pGNzZSdmlnYnIzN1JnIiwgImlkIiwgImh0dHBzOi8vY29udG9zby5leGFtcGxlL2NyZWRlbnRpYWxzL3N0YXR1cy80IzI3Mzc2MiJd~WyJZVFZSQjJJYnYwVlVCUlVZaURnVVRnIiwgInR5cGUiLCBbIlZlcmlmaWFibGVDcmVkZW50aWFsIiwgIks5VW5pdENyZWRlbnRpYWwiXV0~eyJhbGciOiJFUzI1NiIsInR5cCI6ImtiK2p3dCJ9.eyJub25jZSI6IkZhRVBpRjd1LUdnaDZyeFNNZ0x4VkEiLCJhdWQiOiJkaWQ6d2ViOnZlcmlmaWVyLmV4YW1wbGUiLCJpYXQiOjE2OTUyNDYwNTJ9.2-iELnqB2WXoDCcDvBFc2CQmluX9yY2zofw5pwJrwPx4L52G9DtCgMtm068gtnOMN6iv54hMcro-UWscTSTsvA
Example 8: A credential with a schema
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://www.w3.org/ns/credentials/examples/v2"
  ],
  "id": "https://contoso.example/credentials/35327255",
  "type": ["VerifiableCredential", "KYCExample"],
  "issuer": "did:web:contoso.example",
  "validFrom": "2019-05-25T03:10:16.992Z",
  "validUntil": "2027-05-25T03:10:16.992Z",
  "credentialSchema": {
    "id": "https://contoso.example/bafybeigdyr...lqabf3oclgtqy55fbzdi",
    "type": "JsonSchema"
  },
  "credentialSubject": {
    "id": "did:example:1231588",
    "type": "Person"
  }
}
graph LR 48("VerifiableCredential") 49{{"id"}} 50("https://contoso.example/credentials/35327255") 51(("type")) 52("KYCExample") 53("issuer") 54("did:web:contoso.example") 55("validFrom") 56("2019-05-25T03:10:16.992Z") 57("validUntil") 58("2027-05-25T03:10:16.992Z") 59("credentialSchema") 60{{"id"}} 61("https://contoso.example/bafybeigdyr...lqabf3oclgtqy55fbzdi") 62(("type")) 63("JsonSchema") 64("credentialSubject") 65{{"id"}} 66("did:example:1231588") 67(("type")) 68("Person") 48 --- 49 49 --- 50 48 --- 51 51 --- 52 48 --- 53 53 --- 54 48 --- 55 55 --- 56 48 --- 57 57 --- 58 48 --- 59 59 --- 60 60 --- 61 59 --- 62 62 --- 63 48 --- 64 64 --- 65 65 --- 66 64 --- 67 67 --- 68
---------------- Issuer Claims ----------------
"@context":
  - https://www.w3.org/ns/credentials/v2
  - https://www.w3.org/ns/credentials/examples/v2
!sd id: https://contoso.example/credentials/35327255
!sd type:
  - VerifiableCredential
  - KYCExample
issuer: did:web:contoso.example
validFrom: 2019-05-25T03:10:16.992Z
validUntil: 2027-05-25T03:10:16.992Z
credentialSchema:
  !sd id: https://contoso.example/bafybeigdyr...lqabf3oclgtqy55fbzdi
  !sd type: JsonSchema
credentialSubject:
  !sd id: did:example:1231588
  !sd type: Person
---------------- Holder Disclosure ----------------
issuer:
  id: True
credentialStatus:
  id: True
credentialSubject:
  id: True
  type: False
---------------- Decoded Protected Header ----------------
{
  "alg": "ES384"
}
---------------- Decoded Protected Claimset ----------------
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://www.w3.org/ns/credentials/examples/v2"
  ],
  "issuer": "did:web:contoso.example",
  "validFrom": "2019-05-25T03:10:16.992Z",
  "validUntil": "2027-05-25T03:10:16.992Z",
  "credentialSchema": {},
  "credentialSubject": {
    "id": "did:example:1231588"
  },
  "iss": "did:web:issuer.example",
  "iat": 1695246052,
  "exp": 1726868452,
  "cnf": {
    "jwk": {
      "kty": "EC",
      "crv": "P-384",
      "alg": "ES384",
      "x": "Lo9dPpOuPyKFCn5KnFcdZcHqtluIYnc1j4dZaF2U8S-uY0Zp2xLR70T5D5YzD6Us",
      "y": "lwuw6Zlu1jubks4B-qXdGhHf-yTWaTKfLXNrZP8SUpY6qaWbF1ZsHlPKYmcsgUf4"
    }
  }
}
---------------- Compact Encoded Selective Disclosure JSON Web Token ----------------
eyJhbGciOiJFUzM4NCJ9.eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiLCJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvZXhhbXBsZXMvdjIiXSwiaXNzdWVyIjoiZGlkOndlYjpjb250b3NvLmV4YW1wbGUiLCJ2YWxpZEZyb20iOiIyMDE5LTA1LTI1VDAzOjEwOjE2Ljk5MloiLCJ2YWxpZFVudGlsIjoiMjAyNy0wNS0yNVQwMzoxMDoxNi45OTJaIiwiY3JlZGVudGlhbFNjaGVtYSI6eyJfc2QiOlsiM1U4RWhXVE5TTVl4WTZDc1pSZ2ZzRnFEWUJRbzV4SGc2RDZ1SUtFaDBycyIsIk9ZVXpVNWlSdWVxVWljTkIxenFQZFRMUzhOMGFiNWM4QlJNcnVuN1hRa3ciXX0sImNyZWRlbnRpYWxTdWJqZWN0Ijp7Il9zZCI6WyJCTjNZSWh1cUQ1Ylc1QnlSVW9QOTJwYVJ2RUQ0NWZqOTlkRzZMUW5yWmpJIiwiY1ZqaVJSejM3dEd2Sld3VURPc25SRnR4TE5wUXdXQlFXQ09uLTU5X2VNUSJdfSwiX3NkIjpbIlRxOHF5cUZnQjN0MFZNYVc2cFRIalZZR05UbU1oSkxwR1hTQlB2aHI0X2MiLCJ2dmRvWGk4TnU1V0NQOC1ZQmZhNnNEd09VV1Bac1otOU1LX1JGaE9Fc0JnIl0sIl9zZF9hbGciOiJzaGEtMjU2IiwiaXNzIjoiZGlkOndlYjppc3N1ZXIuZXhhbXBsZSIsImlhdCI6MTY5NTI0NjA1MiwiZXhwIjoxNzI2ODY4NDUyLCJjbmYiOnsiandrIjp7Imt0eSI6IkVDIiwiY3J2IjoiUC0zODQiLCJhbGciOiJFUzM4NCIsIngiOiJMbzlkUHBPdVB5S0ZDbjVLbkZjZFpjSHF0bHVJWW5jMWo0ZFphRjJVOFMtdVkwWnAyeExSNzBUNUQ1WXpENlVzIiwieSI6Imx3dXc2Wmx1MWp1YmtzNEItcVhkR2hIZi15VFdhVEtmTFhOclpQOFNVcFk2cWFXYkYxWnNIbFBLWW1jc2dVZjQifX19.eo2dZtUYZbeYdpxGk7Y7gTYioyOBy9Hoe8XcOVkzdbWuSZVthNwgJ6wCIG5bqmXgtja6J4tuoYA8ct4fDrN32xOCN3P_vo38MoHHVXhlJpFvK_94aQC4PWI9pvYQT59O~WyIzbm9pVHVMeDdlRE4wZ1NBSGdlQjNBIiwgImlkIiwgImRpZDpleGFtcGxlOjEyMzE1ODgiXQ~eyJhbGciOiJFUzM4NCIsInR5cCI6ImtiK2p3dCJ9.eyJub25jZSI6Ik0weTN3VlFIR2V6Skl2OUF3TW9HckEiLCJhdWQiOiJkaWQ6d2ViOnZlcmlmaWVyLmV4YW1wbGUiLCJpYXQiOjE2OTUyNDYwNTJ9.aBfGPVBOZ8-REbyhMzemcBmXCf1-zA9Neid-llR7G_hfFQOhpLbDOggnDtB3L8x2tJSeMT9u1ij-_dTPUX9PCNja1QwWW3f4FqRy0oiUGsv_UQW_AQ5lybVFI_qu3ov_

9.3 Presentations

Example 9: Presentation
{
  "@context": ["https://www.w3.org/ns/credentials/v2"],
  "type": ["VerifiablePresentation"],
  "holder": "urn:ietf:params:oauth:jwk-thumbprint:sha-256:_Fpfe27AuGmEljZE9s2lw2UH-qrZLRFNrWbJrWIe4SI",
  "verifiableCredential": [{
      "@context": [
        "https://www.w3.org/ns/credentials/v2"
      ],
      "type": [
        "VerifiableCredential"
      ],
      "issuer": "https://issuer.example/issuers/68",
      "validFrom": "2023-06-07T21:14:14.148Z",
      "credentialSubject": {
        "id": "https://subject.vendor.example"
      }
    },
    "https://vendor.example/credentials/42", 
    "did:example:123",
    "urn:uuid:01ec9426-c175-4e39-a006-d30050e28214",
    "urn:ietf:params:oauth:jwk-thumbprint:sha-256:_Fpfe27AuGmEljZE9s2lw2UH-qrZLRFNrWbJrWIe4SI",
    "data:application/vc+ld+json;base64,eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiXSwidHlwZSI6WyJWZXJpZmlhYmxlQ3JlZGVudGlhbCJdLCJpc3N1ZXIiOiJkaWQ6andrOmV5SnJhV1FpT2lKMWNtNDZhV1YwWmpwd1lYSmhiWE02YjJGMWRHZzZhbmRyTFhSb2RXMWljSEpwYm5RNmMyaGhMVEkxTmpwdlFtUm1kbVpET1hoNk1GOUJVWFpSTjNZMU1YbERXbDl6ZUdwNU56VkNUSEpJZWsxT1Jqa3lPV1U0SWl3aWEzUjVJam9pVDB0UUlpd2lZM0oySWpvaVJXUXlOVFV4T1NJc0ltRnNaeUk2SWtWa1JGTkJJaXdpZUNJNklqTmljbU5zYjBJNGFEUk5XbFZJYms5UVVHbGtTbXd0U2pkdVVsRkpXSFJUYUZwM1oyNW1jbHAxVDI4aWZRIiwidmFsaWRGcm9tIjoiMjAyMy0wNi0wN1QyMToxNDoxNC4xNDhaIiwiY3JlZGVudGlhbFN1YmplY3QiOnsiaWQiOiJodHRwczovL3N1YmplY3QudmVuZG9yLmV4YW1wbGUifX0="
  ]
}
graph LR 82("VerifiablePresentation") 83("holder") 84("urn:ietf:params:oauth:jwk-thumbprint:sha-256:_Fpfe27AuGmEljZE9s2lw2UH-qrZLRFNrWbJrWIe4SI") 85("verifiableCredential") 86("issuer") 87("https://issuer.example/issuers/68") 88("validFrom") 89("2023-06-07T21:14:14.148Z") 90("credentialSubject") 91{{"id"}} 92("https://subject.vendor.example") 93("verifiableCredential") 94("https://vendor.example/credentials/42") 95("verifiableCredential") 96("did:example:123") 97("verifiableCredential") 98("urn:uuid:01ec9426-c175-4e39-a006-d30050e28214") 99("verifiableCredential") 100("urn:ietf:params:oauth:jwk-thumbprint:sha-256:_Fpfe27AuGmEljZE9s2lw2UH-qrZLRFNrWbJrWIe4SI") 101("verifiableCredential") 102("data:application/vc+ld+json;base64,eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiXSwidHlwZSI6WyJWZXJpZmlhYmxlQ3JlZGVudGlhbCJdLCJpc3N1ZXIiOiJkaWQ6andrOmV5SnJhV1FpT2lKMWNtNDZhV1YwWmpwd1lYSmhiWE02YjJGMWRHZzZhbmRyTFhSb2RXMWljSEpwYm5RNmMyaGhMVEkxTmpwdlFtUm1kbVpET1hoNk1GOUJVWFpSTjNZMU1YbERXbDl6ZUdwNU56VkNUSEpJZWsxT1Jqa3lPV1U0SWl3aWEzUjVJam9pVDB0UUlpd2lZM0oySWpvaVJXUXlOVFV4T1NJc0ltRnNaeUk2SWtWa1JGTkJJaXdpZUNJNklqTmljbU5zYjBJNGFEUk5XbFZJYms5UVVHbGtTbXd0U2pkdVVsRkpXSFJUYUZwM1oyNW1jbHAxVDI4aWZRIiwidmFsaWRGcm9tIjoiMjAyMy0wNi0wN1QyMToxNDoxNC4xNDhaIiwiY3JlZGVudGlhbFN1YmplY3QiOnsiaWQiOiJodHRwczovL3N1YmplY3QudmVuZG9yLmV4YW1wbGUifX0=") 82 --- 83 83 --- 84 82 --- 85 85 --- 86 86 --- 87 85 --- 88 88 --- 89 85 --- 90 90 --- 91 91 --- 92 82 --- 93 93 --- 94 82 --- 95 95 --- 96 82 --- 97 97 --- 98 82 --- 99 99 --- 100 82 --- 101 101 --- 102
---------------- Issuer Claims ----------------
"@context":
  - https://www.w3.org/ns/credentials/v2
!sd type:
  - VerifiablePresentation
holder: urn:ietf:params:oauth:jwk-thumbprint:sha-256:_Fpfe27AuGmEljZE9s2lw2UH-qrZLRFNrWbJrWIe4SI
verifiableCredential:
  - "@context":
      - https://www.w3.org/ns/credentials/v2
    !sd type:
      - VerifiableCredential
    issuer: https://issuer.example/issuers/68
    validFrom: 2023-06-07T21:14:14.148Z
    credentialSubject:
      !sd id: https://subject.vendor.example
  - https://vendor.example/credentials/42
  - did:example:123
  - urn:uuid:01ec9426-c175-4e39-a006-d30050e28214
  - urn:ietf:params:oauth:jwk-thumbprint:sha-256:_Fpfe27AuGmEljZE9s2lw2UH-qrZLRFNrWbJrWIe4SI
  - data:application/vc+ld+json;base64,eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiXSwidHlwZSI6WyJWZXJpZmlhYmxlQ3JlZGVudGlhbCJdLCJpc3N1ZXIiOiJkaWQ6andrOmV5SnJhV1FpT2lKMWNtNDZhV1YwWmpwd1lYSmhiWE02YjJGMWRHZzZhbmRyTFhSb2RXMWljSEpwYm5RNmMyaGhMVEkxTmpwdlFtUm1kbVpET1hoNk1GOUJVWFpSTjNZMU1YbERXbDl6ZUdwNU56VkNUSEpJZWsxT1Jqa3lPV1U0SWl3aWEzUjVJam9pVDB0UUlpd2lZM0oySWpvaVJXUXlOVFV4T1NJc0ltRnNaeUk2SWtWa1JGTkJJaXdpZUNJNklqTmljbU5zYjBJNGFEUk5XbFZJYms5UVVHbGtTbXd0U2pkdVVsRkpXSFJUYUZwM1oyNW1jbHAxVDI4aWZRIiwidmFsaWRGcm9tIjoiMjAyMy0wNi0wN1QyMToxNDoxNC4xNDhaIiwiY3JlZGVudGlhbFN1YmplY3QiOnsiaWQiOiJodHRwczovL3N1YmplY3QudmVuZG9yLmV4YW1wbGUifX0=
---------------- Holder Disclosure ----------------
id: True
type: True
holder:
  id: True
---------------- Decoded Protected Header ----------------
{
  "alg": "ES256",
  "typ": "vp+ld+json+sd-jwt",
  "cty": "vp+ld+json"
}
---------------- Decoded Protected Claimset ----------------
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2"
  ],
  "holder": "urn:ietf:params:oauth:jwk-thumbprint:sha-256:_Fpfe27AuGmEljZE9s2lw2UH-qrZLRFNrWbJrWIe4SI",
  "verifiableCredential": [
    {
      "@context": [
        "https://www.w3.org/ns/credentials/v2"
      ],
      "issuer": "https://issuer.example/issuers/68",
      "validFrom": "2023-06-07T21:14:14.148Z",
      "credentialSubject": {}
    },
    "https://vendor.example/credentials/42",
    "did:example:123",
    "urn:uuid:01ec9426-c175-4e39-a006-d30050e28214",
    "urn:ietf:params:oauth:jwk-thumbprint:sha-256:_Fpfe27AuGmEljZE9s2lw2UH-qrZLRFNrWbJrWIe4SI",
    "data:application/vc+ld+json;base64,eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiXSwidHlwZSI6WyJWZXJpZmlhYmxlQ3JlZGVudGlhbCJdLCJpc3N1ZXIiOiJkaWQ6andrOmV5SnJhV1FpT2lKMWNtNDZhV1YwWmpwd1lYSmhiWE02YjJGMWRHZzZhbmRyTFhSb2RXMWljSEpwYm5RNmMyaGhMVEkxTmpwdlFtUm1kbVpET1hoNk1GOUJVWFpSTjNZMU1YbERXbDl6ZUdwNU56VkNUSEpJZWsxT1Jqa3lPV1U0SWl3aWEzUjVJam9pVDB0UUlpd2lZM0oySWpvaVJXUXlOVFV4T1NJc0ltRnNaeUk2SWtWa1JGTkJJaXdpZUNJNklqTmljbU5zYjBJNGFEUk5XbFZJYms5UVVHbGtTbXd0U2pkdVVsRkpXSFJUYUZwM1oyNW1jbHAxVDI4aWZRIiwidmFsaWRGcm9tIjoiMjAyMy0wNi0wN1QyMToxNDoxNC4xNDhaIiwiY3JlZGVudGlhbFN1YmplY3QiOnsiaWQiOiJodHRwczovL3N1YmplY3QudmVuZG9yLmV4YW1wbGUifX0="
  ],
  "iss": "did:web:issuer.example",
  "iat": 1695246052,
  "exp": 1726868452,
  "cnf": {
    "jwk": {
      "kty": "EC",
      "crv": "P-256",
      "alg": "ES256",
      "x": "-FEgujN3fgjt-IMcMwfPDYpbXvffyZXtxS_pWVjGbm8",
      "y": "MDhAy2dzgYdhoioGJajNl0reWy_kaoylcYX_0KRlSQc"
    }
  },
  "type": [
    "VerifiablePresentation"
  ]
}
---------------- Compact Encoded Selective Disclosure JSON Web Token ----------------
eyJhbGciOiJFUzI1NiIsInR5cCI6InZwK2xkK2pzb24rc2Qtand0IiwiY3R5IjoidnArbGQranNvbiJ9.eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiXSwiaG9sZGVyIjoidXJuOmlldGY6cGFyYW1zOm9hdXRoOmp3ay10aHVtYnByaW50OnNoYS0yNTY6X0ZwZmUyN0F1R21FbGpaRTlzMmx3MlVILXFyWkxSRk5yV2JKcldJZTRTSSIsInZlcmlmaWFibGVDcmVkZW50aWFsIjpbeyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiXSwiaXNzdWVyIjoiaHR0cHM6Ly9pc3N1ZXIuZXhhbXBsZS9pc3N1ZXJzLzY4IiwidmFsaWRGcm9tIjoiMjAyMy0wNi0wN1QyMToxNDoxNC4xNDhaIiwiY3JlZGVudGlhbFN1YmplY3QiOnsiX3NkIjpbIkVNT0VKLVMyWW9SVW1xYzRpMURublV4MUdkWGptSndOMDJTY1dBRmhPMjAiXX0sIl9zZCI6WyJJbXllVENvS2pWdlR0UzZVUFF2NnFjaUZreDVyUTNVWkR3NzlhLUhkeU5NIl19LCJodHRwczovL3ZlbmRvci5leGFtcGxlL2NyZWRlbnRpYWxzLzQyIiwiZGlkOmV4YW1wbGU6MTIzIiwidXJuOnV1aWQ6MDFlYzk0MjYtYzE3NS00ZTM5LWEwMDYtZDMwMDUwZTI4MjE0IiwidXJuOmlldGY6cGFyYW1zOm9hdXRoOmp3ay10aHVtYnByaW50OnNoYS0yNTY6X0ZwZmUyN0F1R21FbGpaRTlzMmx3MlVILXFyWkxSRk5yV2JKcldJZTRTSSIsImRhdGE6YXBwbGljYXRpb24vdmMrbGQranNvbjtiYXNlNjQsZXlKQVkyOXVkR1Y0ZENJNld5Sm9kSFJ3Y3pvdkwzZDNkeTUzTXk1dmNtY3Zibk12WTNKbFpHVnVkR2xoYkhNdmRqSWlYU3dpZEhsd1pTSTZXeUpXWlhKcFptbGhZbXhsUTNKbFpHVnVkR2xoYkNKZExDSnBjM04xWlhJaU9pSmthV1E2YW5kck9tVjVTbkpoVjFGcFQybEtNV050TkRaaFYxWXdXbXB3ZDFsWVNtaGlXRTAyWWpKR01XUkhaelpoYm1SeVRGaFNiMlJYTVdsalNFcHdZbTVSTm1NeWFHaE1WRWt4VG1wd2RsRnRVbTFrYlZwRVQxaG9OazFHT1VKVldGcFNUak5aTVUxWWJFUlhiRGw2WlVkd05VNTZWa05VU0VwSlpXc3hUMUpxYTNsUFYxVTBTV2wzYVdFelVqVkphbTlwVkRCMFVVbHBkMmxaTTBveVNXcHZhVkpYVVhsT1ZGVjRUMU5KYzBsdFJuTmFlVWsyU1d0V2ExSkdUa0pKYVhkcFpVTkpOa2xxVG1samJVNXpZakJKTkdGRVVrNVhiRlpKWW1zNVVWVkhiR3RUYlhkMFUycGtkVlZzUmtwWFNGSlVZVVp3TTFveU5XMWpiSEF4VkRJNGFXWlJJaXdpZG1Gc2FXUkdjbTl0SWpvaU1qQXlNeTB3Tmkwd04xUXlNVG94TkRveE5DNHhORGhhSWl3aVkzSmxaR1Z1ZEdsaGJGTjFZbXBsWTNRaU9uc2lhV1FpT2lKb2RIUndjem92TDNOMVltcGxZM1F1ZG1WdVpHOXlMbVY0WVcxd2JHVWlmWDA9Il0sIl9zZCI6WyJ4di03THZlWkRkOFBvWks4dXlrVk52MHprWXhBbFJmTnBKeVQ5aC1vc09RIl0sIl9zZF9hbGciOiJzaGEtMjU2IiwiaXNzIjoiZGlkOndlYjppc3N1ZXIuZXhhbXBsZSIsImlhdCI6MTY5NTI0NjA1MiwiZXhwIjoxNzI2ODY4NDUyLCJjbmYiOnsiandrIjp7Imt0eSI6IkVDIiwiY3J2IjoiUC0yNTYiLCJhbGciOiJFUzI1NiIsIngiOiItRkVndWpOM2ZnanQtSU1jTXdmUERZcGJYdmZmeVpYdHhTX3BXVmpHYm04IiwieSI6Ik1EaEF5MmR6Z1lkaG9pb0dKYWpObDByZVd5X2thb3lsY1lYXzBLUmxTUWMifX19.rkcgldocQB16JSsIaJ7Xhpx9wT9sXUASfwdIVuEpdgFOqqwosynNXska5DN5fAB0Dt-lnGTuZ7-y1DviMAJxzw~WyJpR1NfdGZGVHlqTXJoOUtDMzB0UDV3IiwgInR5cGUiLCBbIlZlcmlmaWFibGVQcmVzZW50YXRpb24iXV0~eyJhbGciOiJFUzI1NiIsInR5cCI6ImtiK2p3dCJ9.eyJub25jZSI6InlrQm1WOWNEOENqWE9lMGJPUWxJNFEiLCJhdWQiOiJkaWQ6d2ViOnZlcmlmaWVyLmV4YW1wbGUiLCJpYXQiOjE2OTUyNDYwNTJ9.xy-BEoQekxX8LZ55b4fHMwDORdpzCzjbtM9-D0IbHkKco9N0Mfw2BTZEuQhTyc4GExRiBRt2AeP1tkInpPTTqA

9.4 Data URIs

Example 10: JSON-LD Verifiable Credential
data:application/vc+ld+json;base64,eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiXSwidHlwZSI6WyJWZXJpZmlhYmxlQ3JlZGVudGlhbCJdLCJpc3N1ZXIiOiJkaWQ6andrOmV5SnJhV1FpT2lKMWNtNDZhV1YwWmpwd1lYSmhiWE02YjJGMWRHZzZhbmRyTFhSb2RXMWljSEpwYm5RNmMyaGhMVEkxTmpwdlFtUm1kbVpET1hoNk1GOUJVWFpSTjNZMU1YbERXbDl6ZUdwNU56VkNUSEpJZWsxT1Jqa3lPV1U0SWl3aWEzUjVJam9pVDB0UUlpd2lZM0oySWpvaVJXUXlOVFV4T1NJc0ltRnNaeUk2SWtWa1JGTkJJaXdpZUNJNklqTmljbU5zYjBJNGFEUk5XbFZJYms5UVVHbGtTbXd0U2pkdVVsRkpXSFJUYUZwM1oyNW1jbHAxVDI4aWZRIiwidmFsaWRGcm9tIjoiMjAyMy0wNi0wN1QyMToxNDoxNC4xNDhaIiwiY3JlZGVudGlhbFN1YmplY3QiOnsiaWQiOiJodHRwczovL3N1YmplY3QudmVuZG9yLmV4YW1wbGUifX0=
Example 11: JSON-LD Verifiable Presentation
data:application/vp+ld+json+json;base64,eyJAY29udGV4dCI6WyJodHRwczovL3d3dy53My5vcmcvbnMvY3JlZGVudGlhbHMvdjIiXSwidHlwZSI6WyJWZXJpZmlhYmxlQ3JlZGVudGlhbCJdLCJpc3N1ZXIiOiJkaWQ6andrOmV5SnJhV1FpT2lKMWNtNDZhV1YwWmpwd1lYSmhiWE02YjJGMWRHZzZhbmRyTFhSb2RXMWljSEpwYm5RNmMyaGhMVEkxTmpwdlFtUm1kbVpET1hoNk1GOUJVWFpSTjNZMU1YbERXbDl6ZUdwNU56VkNUSEpJZWsxT1Jqa3lPV1U0SWl3aWEzUjVJam9pVDB0UUlpd2lZM0oySWpvaVJXUXlOVFV4T1NJc0ltRnNaeUk2SWtWa1JGTkJJaXdpZUNJNklqTmljbU5zYjBJNGFEUk5XbFZJYms5UVVHbGtTbXd0U2pkdVVsRkpXSFJUYUZwM1oyNW1jbHAxVDI4aWZRIiwidmFsaWRGcm9tIjoiMjAyMy0wNi0wN1QyMToxNDoxNC4xNDhaIiwiY3JlZGVudGlhbFN1YmplY3QiOnsiaWQiOiJodHRwczovL3N1YmplY3QudmVuZG9yLmV4YW1wbGUifX0=

9.5 Detached Payload

Issue

TODO add COSE Sign1 detached payload examples

A. References

A.1 Normative references

[json-ld11]
JSON-LD 1.1. Gregg Kellogg; Pierre-Antoine Champin; Dave Longley. W3C. 16 July 2020. W3C Recommendation. URL: https://www.w3.org/TR/json-ld11/
[MULTIPLE-SUFFIXES]
Media Types with Multiple Suffixes. Manu Sporny; Amy Guy. IETF. Internet-Draft. URL: https://datatracker.ietf.org/doc/draft-ietf-mediaman-suffixes/
[RFC2119]
Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc2119
[RFC6838]
Media Type Specifications and Registration Procedures. N. Freed; J. Klensin; T. Hansen. IETF. January 2013. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc6838
[rfc7159]
The JavaScript Object Notation (JSON) Data Interchange Format. T. Bray, Ed.. IETF. March 2014. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc7159
[rfc7515]
JSON Web Signature (JWS). M. Jones; J. Bradley; N. Sakimura. IETF. May 2015. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc7515
[RFC7517]
JSON Web Key (JWK). M. Jones. IETF. May 2015. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc7517
[RFC7519]
JSON Web Token (JWT). M. Jones; J. Bradley; N. Sakimura. IETF. May 2015. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc7519
[rfc7800]
Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs). M. Jones; J. Bradley; H. Tschofenig. IETF. April 2016. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc7800
[RFC8174]
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc8174
[rfc8949]
Concise Binary Object Representation (CBOR). C. Bormann; P. Hoffman. IETF. December 2020. Internet Standard. URL: https://www.rfc-editor.org/rfc/rfc8949
[RFC9052]
CBOR Object Signing and Encryption (COSE): Structures and Process. J. Schaad. IETF. August 2022. Internet Standard. URL: https://www.rfc-editor.org/rfc/rfc9052
[SD-JWT]
Selective Disclosure for JWTs (SD-JWT). Daniel Fett; Kristina Yasuda; Brian Campbell. IETF. Internet-Draft. URL: https://datatracker.ietf.org/doc/html/draft-ietf-oauth-selective-disclosure-jwt-05
[SD-JWT-VC]
SD-JWT-based Verifiable Credentials (SD-JWT VC). Oliver Terbu; Daniel Fett. IETF. Internet-Draft. URL: https://datatracker.ietf.org/doc/html/draft-ietf-oauth-sd-jwt-vc-00
[VC-DATA-MODEL]
Verifiable Credentials Data Model v1.1. Manu Sporny; Grant Noble; Dave Longley; Daniel Burnett; Brent Zundel; Kyle Den Hartog. W3C. 3 March 2022. W3C Recommendation. URL: https://www.w3.org/TR/vc-data-model/

A.2 Informative references

[RFC5785]
Defining Well-Known Uniform Resource Identifiers (URIs). M. Nottingham; E. Hammer-Lahav. IETF. April 2010. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc5785
[WCAG21]
Web Content Accessibility Guidelines (WCAG) 2.1. Andrew Kirkpatrick; Joshue O'Connor; Alastair Campbell; Michael Cooper. W3C. 5 June 2018. W3C Recommendation. URL: https://www.w3.org/TR/WCAG21/