Kristina

need to confirm that this can be done in a backward compatible manner, but since this feature is not likely be mandatory, tackling it post 1.0 should be acceptable.

> We would need to change to: > > > Cryptographic algorithm names used in the credential_signing_alg_values_supported parameter SHOULD be one of those defined in [[ISO.18013-5](https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html#ISO.18013-5)] represented as JOSE algorithm...

ping @davidz25 @GarethCOliver @hlozi

WG discussion - VP and VCI should have a similar mechanism for this - match what we did in https://github.com/openid/OpenID4VP/pull/553

we discussed this internally with Microsoft engineers. We do not currently have use-cases with the claims that have nested structure and array-based solution is too big of a breaking change....

suggesting @jogu to do a non-normative PR explaining what does not work in the current structure, before PR #278 gets merged. ideally before March 18th to get into ID-1

@danielfett can you please change the issue name from "is broken" to something like "needs improvement"? Implementation feedback showed that the current structure works for majority of the current use-cases,...

we brushed-up Paul's original proposals in the in-person WG: 1a: make credential_identifiers mandatory in credential request for RAR (can still use format/credential_config_id in authorization req) 1b: make credential_identifiers mandatory in...

(personally agree to all the above)

Paul to do a PR on points 1-3 and on point 4, discussed in a WG, there is rough consensus that it is a good idea to use credential_configuration_id in...