Christian Bormann

We would need to add IANA registration requests for both parameters in their respective registries I assume?

Would it make sense to define a "profile" name for the current/default behaviour?

> @Sakurann Adding the type parameter later on will be a breaking change. Adding it now will ensure extensibility in a non-breaking way for 1.1, 2, 2.1, 3 etc ad...

We should probably also adjust these lines: 244 > The Verifier articulates requirements of the Credential(s) that are requested using `presentation_definition` and `presentation_definition_uri` parameters that contain a Presentation Definition JSON...

I've been wondering since this was brought up: Do you think there will some form of generally applicable rule that fits all of those use-cases which part would be encrypted...

A bit off-topic, but somewhat related thing that I noticed when reading the Annex specifying the format specific parts: We have a Section in VCI [VC signed as a JWT,...

I started working on this and have a clarifying question: Within `credential_configurations_supported`, there are currently a these paramters: - format - scope - cryptographic_binding_methods_supported - credential_signing_alg_values_supported - proof_types_supported - display...

How exactly is data being provided without informed user consent in OpenID4VP? The Wallet receives an Authorization Request (which might also be signed and linked to a trust ecosystem to...

> we tried to document the problem - here is part of the text from the EU - The purpose is designed to meet the desires of the verifier which...

As discussed on the WG call today, I'd propose to initially add a small note in the JARM section that clarifies the different options from JOSE and explicitly points to...