remove credential offer part from credential profiles

examples/credential_offer_multiple_credentials.json

@@ -5,9 +5,6 @@
       "org.iso.18013.5.1.mDL"
    ],
    "grants": {
-      "authorization_code": {
-         "issuer_state": "eyJhbGciOiJSU0Et...FYUaBy"
-      },
       "urn:ietf:params:oauth:grant-type:pre-authorized_code": {
          "pre-authorized_code": "oaKazRN8I0IbtZ0C7JuMn5",
          "tx_code" : {

openid-4-verifiable-credential-issuance-1_0.md

@@ -331,34 +331,22 @@ The following values are defined by this specification:
   * `interval`: OPTIONAL. The minimum amount of time in seconds that the Wallet SHOULD wait between polling requests to the token endpoint (in case the Authorization Server responds with error code `authorization_pending` - see (#token_error_response)). If no value is provided, Wallets MUST use `5` as the default.
   * `authorization_server`: OPTIONAL string that the Wallet can use to identify the Authorization Server to use with this grant type when `authorization_servers` parameter in the Credential Issuer metadata has multiple entries. MUST NOT be used otherwise. The value of this parameter MUST match with one of the values in the `authorization_servers` array obtained from the Credential Issuer metadata.
 
-The following non-normative example shows a Credential Offer object where the Credential Issuer can offer the issuance of two Credentials of different formats, one as a string ("UniversityDegree_JWT") and the other one as an object:
+The following non-normative example shows a Credential Offer object where the Credential Issuer can offer the issuance of two different Credentials (which may be even of different formats):
 
 <{{examples/credential_offer_multiple_credentials.json}}
 
-Note: The examples throughout the specification use Credential Format specific parameters defined in the Credential Format Profiles that can be found in (#format_profiles).
-
 ### Sending Credential Offer by Value Using `credential_offer` Parameter
 
 Below is a non-normative example of a Credential Offer passed by value:
 
 ```
-  GET /credential_offer?credential_offer=%7B%22credential_issuer%22:%22
-  https://credential-issuer.example.com%22,%22credentials%22:%5B%22UniversityDegree_JWT
-  %22,%7B%22format%22:%22mso_mdoc%22,%22doctype%22:%22org.iso.18013.5.1.mDL%22%7D%5D,%22
-  grants%22:%7B%22authorization_code%22:%7B%22issuer_state%22:%22eyJhbGciOiJSU0Et...FYUaBy
-  %22%7D,%22urn:ietf:params:oauth:grant-type:pre-authorized_code%22:%7B%22
-  pre-authorized_code%22:%22adhjhdjajkdkhjhdj%22,%22tx_code%22:%7B%7D%7D%7D%7D
+  GET /credential_offer?credential_offer=%7B%22credential_issuer%22:%22https://credential-issuer.example.com%22,%22credentials%22:%5B%22UniversityDegree_JWT%22,%22org.iso.18013.5.1.mDL%22%5D,%22grants%22:%7B%22urn:ietf:params:oauth:grant-type:pre-authorized_code%22:%7B%22pre-authorized_code%22:%22oaKazRN8I0IbtZ0C7JuMn5%22,%22tx_code%22:%7B%7D%7D%7D%7D
 ```
 
 The following is a non-normative example of a Credential Offer that can be included in a QR code or a link used to invoke a Wallet deployed as a native app:
 
 ```
-openid-credential-offer://?credential_offer=%7B%22credential_issuer%22:%22
-  https://credential-issuer.example.com%22,%22credentials%22:%5B%22UniversityDegree_JWT
-  %22,%7B%22format%22:%22mso_mdoc%22,%22doctype%22:%22org.iso.18013.5.1.mDL%22%7D%5D,%22
-  grants%22:%7B%22authorization_code%22:%7B%22issuer_state%22:%22eyJhbGciOiJSU0Et...FYUaBy
-  %22%7D,%22urn:ietf:params:oauth:grant-type:pre-authorized_code%22:%7B%22
-  pre-authorized_code%22:%22adhjhdjajkdkhjhdj%22,%22tx_code%22:%7B%7D%7D%7D%7D
+openid-credential-offer://?credential_offer=%7B%22credential_issuer%22:%22https://credential-issuer.example.com%22,%22credentials%22:%5B%22org.iso.18013.5.1.mDL%22%5D,%22grants%22:%7B%22urn:ietf:params:oauth:grant-type:pre-authorized_code%22:%7B%22pre-authorized_code%22:%22oaKazRN8I0IbtZ0C7JuMn5%22,%22tx_code%22:%7B%22input_mode%22:%22text%22,%22description%22:%22Please%20enter%20the%20serial%20number%20of%20your%20physical%20drivers%20license%22%7D%7D%7D%7D
 ```
 
 ### Sending Credential Offer by Reference Using `credential_offer_uri` Parameter
@@ -1846,13 +1834,6 @@ The following is a non-normative example of an object comprising `credentials_su
 
 <{{examples/credential_metadata_jwt_vc_json.json}}
 
-#### Credential Offer
-
-The following is a non-normative example of a Credential Offer of Credential format `jwt_vc_json`:
-
-
-<{{examples/credential_offer_jwt_vc_json.json}}
-
 #### Authorization Details {#authorization_jwt_vc_json}
 
 The following additional claims are defined for authorization details of type `openid_credential` and this Credential format.
@@ -1918,13 +1899,6 @@ The following is a non-normative example of an object comprising `credentials_su
 
 <{{examples/credential_metadata_ldp_vc.json}}
 
-#### Credential Offer {#issuer_initiated_issuance_ldp_vc}
-
-The following is a non-normative example of a Credential Offer of Credential format `ldp_vc`:
-
-<{{examples/credential_offer_ldp_vc.json}}
-
-
 #### Authorization Details {#authorization_ldp_vc}
 
 The following additional claims are defined for authorization details of type `openid_credential` and this Credential format.  
@@ -1977,13 +1951,9 @@ When the `format` value is `jwt_vc_json-ld`, entire Credential Offer, Authorizat
 
 The definitions in (#server_metadata_ldp_vc) apply for metadata of Credentials of this type as well. 
 
-#### Credential Offer
-
-The definitions in (#issuer_initiated_issuance_ldp_vc) apply for Credentials of this type as well. 
-
 #### Authorization Details
 
-The definitions in (#issuer_initiated_issuance_ldp_vc) apply for Credentials of this type as well.
+The definitions in (#authorization_ldp_vc) apply for credentials of this type as well.
 
 #### Credential Request
 
@@ -2018,12 +1988,6 @@ The following is a non-normative example of an object comprising `credentials_su
 
 <{{examples/credential_metadata_mso_mdoc.json}}
 
-### Credential Offer
-
-The following is a non-normative example of a Credential Offer of Credential format `mso_mdoc`:
-
-<{{examples/credential_offer_mso_doc.json}}
-
 ### Authorization Details
 
 The following additional claims are defined for authorization details of type `openid_credential` and this Credential format.
@@ -2057,6 +2021,7 @@ The value of the `credential` claim in the Credential Response MUST be a string
    -13
 
    * replaced `user_pin_required` in Credential Offer with a `tx_code` object that also now contains `description` and `length`
+   * removed Credential Offer examples from Credential format profiles
 
    -12