Joseph Heenan

There's a divergence arising because we need to be more precise in the language; "claims" is ambiguous, we need to be clear if we mean claim names or claim values...

It might be sensible to treat the 'New credential updates endpoint' part as a separate issue that we tackle after we've solved versioning in general. (I think we discussed in...

@paulbastian > I would not differentiate between B and C, or at least I think there is not enough value to justify the efforts. Having the distinction between the remaining...

@tplooker > > (I think we discussed in a call somewhere that some issuers won't be happy with having an oauth protected API that's frequently called by wallets, and there...

> I would imagine it is the issuer who dictates the number of copies, but I have also seen an implementation in ISO mDL world where the user can choose...

> > most recent ideas for Credential Request > > multiple proofs ask for multiple instances of the same credential? Correct.

> Can you elaborate on the usecase here? When using an endpoint that allows the wallet to request many copies of a credential at the same time, it's really helpful...

> I guess I'm trying to understand why an issuer would want to cap this number and communicate this cap to a wallet, for example why does an authorization server...

> @tplooker's alternative perspective that the credential endpoint can be used to issue multiple copies of a credential by simply making multiple requests resonates. I definitely appreciate the simplicity of...

> Agreed there are tradeoffs here but as I said above conversely batch endpoints aren't without issue too, for example what if I requested 10 credentials and the 8th fails...