From 9667767bd1b1d1ee7f9bc17ddc2d50bbc7f8c335 Mon Sep 17 00:00:00 2001 From: gabe Date: Thu, 10 Oct 2024 15:30:51 -0700 Subject: [PATCH 1/4] Merge in main. --- index.html | 48 ++++++++++++++++++++++++++---------------------- 1 file changed, 26 insertions(+), 22 deletions(-) diff --git a/index.html b/index.html index f8bfbfe..acec499 100644 --- a/index.html +++ b/index.html @@ -434,10 +434,11 @@

Securing JSON-LD Verifiable Credentials

The typ header parameter SHOULD be vc+jwt. When present, the cty header parameter SHOULD be - vc. See - Registered Header Parameter Names - for additional details regarding usage of typ and - cty. + vc. + The cty header parameter value can be used to differentiate + between secured content of different types when using vc+jwt. + See Registered Header Parameter Names + for additional details regarding usage of typ and cty.

A [=conforming JWS verifier implementation=] MUST use [[RFC7515]] to @@ -497,10 +498,11 @@

Securing JSON-LD

The typ header parameter SHOULD be vp+jwt. When present, the cty header parameter SHOULD be - vp. See - Registered Header Parameter Names - for additional details regarding usage of typ and - cty. + vp. + The cty header parameter value can be used to differentiate + between secured content of different types when using vp+jwt. + See Registered Header Parameter Names + for additional details regarding usage of typ and cty.

A [=conforming JWS verifier implementation=] MUST use [[RFC7515]] to @@ -664,9 +666,10 @@

Securing JSON-LD Verifiable Credentials with SD-JW

The typ header parameter SHOULD be vc+sd-jwt. When present, the cty header parameter SHOULD be vc. + The cty header parameter value can be used to differentiate + between secured content of different types when using vc+sd-jwt. See Registered Header Parameter Names - for additional details regarding usage of typ and - cty. + for additional details regarding usage of typ and cty.

A [=conforming SD-JWT verifier implementation=] MUST use [[SD-JWT]] @@ -735,8 +738,9 @@

Securing JSON-LD Verifiable Presentations with SD-J

The typ header parameter SHOULD be vp+sd-jwt. When present, the cty header parameter SHOULD be vp. - See - Registered Header Parameter Names + The cty header parameter value can be used to differentiate + between secured content of different types when using vp+sd-jwt. + See Registered Header Parameter Names for additional details regarding usage of typ and cty.

@@ -845,10 +849,12 @@

Securing JSON-LD The typ header parameter, as described in COSE "typ" (type) Header Parameter, SHOULD be application/vc+cose. + The content type (3) header parameter value can be used + to differentiate between secured content of different types when using + application/vc+cose. When present, the content type (3) header parameter SHOULD be application/vc. - See - Common COSE Header Parameters + See Common COSE Header Parameters for additional details.

@@ -912,12 +918,11 @@

Securing JSON-LD Verifiable Presentations with C The unsecured [=verifiable presentation=] is the unencoded COSE_Sign1 payload.

- The typ header parameter SHOULD be - application/vp+cose. - When present, the content type (3) header parameter - SHOULD be application/vp. - See - Common COSE Header Parameters + The typ header parameter SHOULD be application/vp+cose. + The content type (3) header parameter value can be used to differentiate + between secured content of different types when using application/vp+cose. + When present, the content type (3) header parameter SHOULD be application/vp. + See Common COSE Header Parameters for additional details.

@@ -1307,8 +1312,7 @@

Verifying a Credential or Presentation Secured with JOSE

-

Verifying a Credential or Presentation Secured - with [[SD-JWT]]

+

Verifying a Credential or Presentation Secured with SD-JWT

The inputs for this algorithm are:

From 16098418379309c68cdf962f168d8420e4f75e50 Mon Sep 17 00:00:00 2001 From: Gabe <7622243+decentralgabe@users.noreply.github.com> Date: Thu, 10 Oct 2024 15:33:15 -0700 Subject: [PATCH 2/4] Update index.html --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index acec499..7148a5f 100644 --- a/index.html +++ b/index.html @@ -849,11 +849,11 @@

Securing JSON-LD The typ header parameter, as described in COSE "typ" (type) Header Parameter, SHOULD be application/vc+cose. + When present, the content type (3) header parameter + SHOULD be application/vc. The content type (3) header parameter value can be used to differentiate between secured content of different types when using application/vc+cose. - When present, the content type (3) header parameter - SHOULD be application/vc. See Common COSE Header Parameters for additional details.

From 81a6b69f8106e086f101bfb6a022998ad2a0c0b6 Mon Sep 17 00:00:00 2001 From: Gabe <7622243+decentralgabe@users.noreply.github.com> Date: Thu, 10 Oct 2024 15:34:17 -0700 Subject: [PATCH 3/4] Update index.html --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 7148a5f..1fa582f 100644 --- a/index.html +++ b/index.html @@ -919,9 +919,9 @@

Securing JSON-LD Verifiable Presentations with C

The typ header parameter SHOULD be application/vp+cose. + When present, the content type (3) header parameter SHOULD be application/vp. The content type (3) header parameter value can be used to differentiate between secured content of different types when using application/vp+cose. - When present, the content type (3) header parameter SHOULD be application/vp. See Common COSE Header Parameters for additional details.

From db0a0589b406cfa46cee0d01b756f04b88624764 Mon Sep 17 00:00:00 2001 From: Gabe <7622243+decentralgabe@users.noreply.github.com> Date: Thu, 10 Oct 2024 15:34:50 -0700 Subject: [PATCH 4/4] Update index.html --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 1fa582f..92b0d11 100644 --- a/index.html +++ b/index.html @@ -919,7 +919,7 @@

Securing JSON-LD Verifiable Presentations with C

The typ header parameter SHOULD be application/vp+cose. - When present, the content type (3) header parameter SHOULD be application/vp. + When present, the content type (3) header parameter SHOULD be application/vp. The content type (3) header parameter value can be used to differentiate between secured content of different types when using application/vp+cose. See Common COSE Header Parameters