Kristina

to Paul's point, right now, only display properties at the leaf nodes are supported, so the example you are providing is not defined by the specification right now. The issue...

since POTENTIAL LSP mandated `cwt` proof type, i think it would be wise to wait for their implementation feedback before we make a decision to remove or keep `cwt` proof...

@bc-pi from your emojis, you seem to be very excited at the potential of removing `cwt` proof type. > The way it's defined doesn't seem like it could possibly be...

agreed to remove on the wg call

if a mechanism to better issue multiple copies of the same credential dataset is added to credential endpoint in a backward compatible manner, I am ok having only one endpoint...

We should add in this PR, credential issuer metadata parameter that the issuer uses to indicate how many credential copies it expects.

WG call: tobias, Giuseppe, Christian (maybe Brian) to re-review. will merge once there are 4 approvals - hopefully within the next 1-2 days.

will continue the discussion on merging batch/credential endpoints in this issue: https://github.com/openid/OpenID4VCI/issues/18

> I would rather suggest to have another example (pair) for request for encrypted response and encrypted response. > > Should we then leave this PR as is and create...

reads like the issue author agrees there is no action here? closing in a week unless objections.