The non normative example in the token request (c.f. https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-1_1-wg-draft.html#section-7.1-10 same for https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-6.1-10) contains `client_assertion`, but as far as I can see it is never mentioned or referenced from this specification directly. In fact, the recommended way (https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-13.2-3.1) is to use https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-wallet-attestations-in-jwt- that follows https://datatracker.ietf.org/doc/html/draft-ietf-oauth-attestation-based-client-auth-07 which in the changelog contains ``` remove usage of RFC7521 and the usage of client_assertion ``` (https://datatracker.ietf.org/doc/html/draft-ietf-oauth-attestation-based-client-auth-07#appendix-A-10.1.1). So it might be a reasonable editorial change, to remove the `client_assertion` from the example.
The non normative example in the token request (c.f. https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-1_1-wg-draft.html#section-7.1-10 same for https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-6.1-10) contains
client_assertion, but as far as I can see it is never mentioned or referenced from this specification directly.In fact, the recommended way (https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-13.2-3.1) is to use https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-wallet-attestations-in-jwt- that follows https://datatracker.ietf.org/doc/html/draft-ietf-oauth-attestation-based-client-auth-07 which in the changelog contains
(https://datatracker.ietf.org/doc/html/draft-ietf-oauth-attestation-based-client-auth-07#appendix-A-10.1.1).
So it might be a reasonable editorial change, to remove the
client_assertionfrom the example.