From 34e39f28e6ac3219e996a54fe5a8c1e2ede7c885 Mon Sep 17 00:00:00 2001 From: gabe Date: Wed, 23 Oct 2024 18:56:02 -0700 Subject: [PATCH 1/5] update cose typ language --- index.html | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index 7438d70..f43df9a 100644 --- a/index.html +++ b/index.html @@ -437,6 +437,7 @@

Securing JSON-LD Verifiable Credentials vc. The cty header parameter value can be used to differentiate between secured content of different types when using vc+jwt. + Other more specific media types MAY be used, if they are available. See Registered Header Parameter Names for additional details regarding usage of typ and cty.

@@ -501,6 +502,7 @@

Securing JSON-LD vp. The cty header parameter value can be used to differentiate between secured content of different types when using vp+jwt. + Other more specific media types MAY be used, if they are available. See Registered Header Parameter Names for additional details regarding usage of typ and cty.

@@ -668,6 +670,7 @@

Securing JSON-LD Verifiable Credentials with SD-JW 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. + Other more specific media types MAY be used, if they are available. See Registered Header Parameter Names for additional details regarding usage of typ and cty.

@@ -740,6 +743,7 @@

Securing JSON-LD Verifiable Presentations with SD-J When present, the cty header parameter SHOULD be vp. The cty header parameter value can be used to differentiate between secured content of different types when using vp+sd-jwt. + Other more specific media types MAY be used, if they are available. See Registered Header Parameter Names for additional details regarding usage of typ and cty.

@@ -849,11 +853,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 type (16) 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. + Other more specific media types MAY be used, if they are available. See Common COSE Header Parameters for additional details.

@@ -919,9 +923,10 @@

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 type (16) 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. + Other more specific media types MAY be used, if they are available. See Common COSE Header Parameters for additional details.

From 91decca6b1d8003da4e6ba7b7980fd8df70e260f Mon Sep 17 00:00:00 2001 From: gabe Date: Wed, 23 Oct 2024 19:32:11 -0700 Subject: [PATCH 2/5] fix --- index.html | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index f43df9a..3544a58 100644 --- a/index.html +++ b/index.html @@ -850,11 +850,11 @@

Securing JSON-LD The unsecured [=verifiable credential=] is the unencoded COSE_Sign1 payload.

- The typ header parameter, as described in + The typ (16) header parameter, as described in COSE "typ" (type) Header Parameter, SHOULD be application/vc+cose. - The type (16) header parameter SHOULD be application/vc. - The content type (3) header parameter value can be used + The content type (3) header parameter SHOULD be application/vc. + The content type header parameter value can be used to differentiate between secured content of different types when using application/vc+cose. Other more specific media types MAY be used, if they are available. @@ -922,10 +922,13 @@

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. - The type (16) 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. + The typ (16) header parameter, as described in + COSE "typ" (type) Header Parameter, + SHOULD be application/vp+cose. + The content type (3) header parameter SHOULD be application/vp. + The content type header parameter value can be used + to differentiate between secured content of different types when using + application/vp+cose. Other more specific media types MAY be used, if they are available. See Common COSE Header Parameters for additional details. From 93c27d962233beb6c08774563116218baf6680df Mon Sep 17 00:00:00 2001 From: gabe Date: Wed, 23 Oct 2024 19:54:43 -0700 Subject: [PATCH 3/5] update language --- index.html | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/index.html b/index.html index 3544a58..f1ee1fc 100644 --- a/index.html +++ b/index.html @@ -437,7 +437,8 @@

Securing JSON-LD Verifiable Credentials vc. The cty header parameter value can be used to differentiate between secured content of different types when using vc+jwt. - Other more specific media types MAY be used, if they are available. + The content type header parameter is optional, and can be used + to express a more specific media type than application/vc when one is available. See Registered Header Parameter Names for additional details regarding usage of typ and cty.

@@ -502,7 +503,8 @@

Securing JSON-LD vp. The cty header parameter value can be used to differentiate between secured content of different types when using vp+jwt. - Other more specific media types MAY be used, if they are available. + The content type header parameter is optional, and can be used + to express a more specific media type than application/vc when one is available. See Registered Header Parameter Names for additional details regarding usage of typ and cty.

@@ -670,7 +672,8 @@

Securing JSON-LD Verifiable Credentials with SD-JW 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. - Other more specific media types MAY be used, if they are available. + The content type header parameter is optional, and can be used + to express a more specific media type than application/vc when one is available. See Registered Header Parameter Names for additional details regarding usage of typ and cty.

@@ -743,7 +746,8 @@

Securing JSON-LD Verifiable Presentations with SD-J When present, the cty header parameter SHOULD be vp. The cty header parameter value can be used to differentiate between secured content of different types when using vp+sd-jwt. - Other more specific media types MAY be used, if they are available. + The content type header parameter is optional, and can be used + to express a more specific media type than application/vc when one is available. See Registered Header Parameter Names for additional details regarding usage of typ and cty.

@@ -854,10 +858,8 @@

Securing JSON-LD COSE "typ" (type) Header Parameter, SHOULD be application/vc+cose. The content type (3) header parameter SHOULD be application/vc. - The content type header parameter value can be used - to differentiate between secured content of different types when using - application/vc+cose. - Other more specific media types MAY be used, if they are available. + The content type header parameter is optional, and can be used + to express a more specific media type than application/vc when one is available. See Common COSE Header Parameters for additional details.

@@ -929,7 +931,8 @@

Securing JSON-LD Verifiable Presentations with C The content type header parameter value can be used to differentiate between secured content of different types when using application/vp+cose. - Other more specific media types MAY be used, if they are available. + The content type header parameter is optional, and can be used + to express a more specific media type than application/vc when one is available. See Common COSE Header Parameters for additional details.

From fc616ca54b135b94114a2f278aeb4f238117df74 Mon Sep 17 00:00:00 2001 From: Gabe <7622243+decentralgabe@users.noreply.github.com> Date: Wed, 23 Oct 2024 21:00:09 -0700 Subject: [PATCH 4/5] Update index.html Co-authored-by: Michael B. Jones --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index f1ee1fc..dad4b13 100644 --- a/index.html +++ b/index.html @@ -858,7 +858,7 @@

Securing JSON-LD COSE "typ" (type) Header Parameter, SHOULD be application/vc+cose. The content type (3) header parameter SHOULD be application/vc. - The content type header parameter is optional, and can be used + The content type (3) header parameter is optional, and can be used to express a more specific media type than application/vc when one is available. See Common COSE Header Parameters for additional details. From 1f816f435bf91e9739a2b342fcdd9eaa2151d07c Mon Sep 17 00:00:00 2001 From: Gabe <7622243+decentralgabe@users.noreply.github.com> Date: Wed, 23 Oct 2024 21:00:21 -0700 Subject: [PATCH 5/5] Update index.html Co-authored-by: Michael B. Jones --- index.html | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/index.html b/index.html index dad4b13..66766d5 100644 --- a/index.html +++ b/index.html @@ -928,11 +928,8 @@

Securing JSON-LD Verifiable Presentations with C COSE "typ" (type) Header Parameter, SHOULD be application/vp+cose. The content type (3) header parameter SHOULD be application/vp. - The content type header parameter value can be used - to differentiate between secured content of different types when using - application/vp+cose. - The content type header parameter is optional, and can be used - to express a more specific media type than application/vc when one is available. + The content type (3) header parameter is optional, and can be used + to express a more specific media type than application/vp when one is available. See Common COSE Header Parameters for additional details.