From 2c7495b4a3b4e061ae9d467cc25aaeef4c3948f1 Mon Sep 17 00:00:00 2001 From: Kristina Yasuda Date: Wed, 22 Jan 2025 12:10:47 +0100 Subject: [PATCH 1/2] update changelog --- openid-4-verifiable-credential-issuance-1_0.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/openid-4-verifiable-credential-issuance-1_0.md b/openid-4-verifiable-credential-issuance-1_0.md index 0d196744..a67ab65d 100644 --- a/openid-4-verifiable-credential-issuance-1_0.md +++ b/openid-4-verifiable-credential-issuance-1_0.md @@ -2769,13 +2769,15 @@ The technology described in this specification was made available from contribut * deferred credential response always returns an array (same as credential response) * notification_id is now used for an issuance flow that can contain more than one credential * Fixed #375: Enabled non-breaking extensibility - * removes `c_nonce` and `c_nonce_expires_in` from the Credential Error Response + * removes `c_nonce` and `c_nonce_expires_in` from the Credential Response * Fixed #239: Completed IANA Considerations section * add key attestation as additional information in a proof of possession and new proof type * Change the syntax of credential metadata to use claims path queries * change credential format identifier `vc+sd-jwt` to `dc+sd-jwt` to align with the media type in draft -06 of [@I-D.ietf-oauth-sd-jwt-vc] and update `typ` accordingly in examples * use claims path pointer for mdoc based credentials - * removes `c_nonce_expires_in` from Nonce Endpoint + * removed `c_nonce_expires_in` from Nonce Endpoint + * removed `c_nonce` and `c_nonce_expires_in` from the token endpoint response + * added a Nonce Endpoint where a Client can acquire a fresh c_nonce value without the overhead of a full Credential Request -14 @@ -2792,8 +2794,6 @@ The technology described in this specification was made available from contribut * Define Credential Dataset as a term * Define Credential Configuration as a term * remove use of the `authorization_pending` and `slow_down` error codes - * removed `c_nonce` and `c_nonce_expires_in` from the token endpoint response - * added a Nonce Endpoint where a Client can acquire a fresh c_nonce value without the overhead of a full Credential Request -13 From 9a9d09175bb3d587a88b011af4880440c0714df0 Mon Sep 17 00:00:00 2001 From: Kristina Yasuda Date: Thu, 23 Jan 2025 10:25:02 +0100 Subject: [PATCH 2/2] fix rendering --- openid-4-verifiable-credential-issuance-1_0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/openid-4-verifiable-credential-issuance-1_0.md b/openid-4-verifiable-credential-issuance-1_0.md index a67ab65d..0e0f54ad 100644 --- a/openid-4-verifiable-credential-issuance-1_0.md +++ b/openid-4-verifiable-credential-issuance-1_0.md @@ -2284,7 +2284,7 @@ be used): `false`, the claim is not required to be included in the Credential. If the `mandatory` parameter is omitted, the default value is `false`. -The rules defined in (##claims-description-processing) apply. +The rules defined in (#claims-description-processing) apply. ## Claims Description for Issuer Metadata {#claims-description-issuer-metadata} @@ -2311,7 +2311,7 @@ following keys can be used to describe the claim or claims: represented as language tag values defined in BCP47 [@!RFC5646]. There MUST be only one object for each language identifier. -The rules defined in (##claims-description-processing) apply. +The rules defined in (#claims-description-processing) apply. ## Processing Rules for Claims Description Objects {#claims-description-processing}