Brian Campbell

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

> In practice this does complicate the spec (which is complicated enough even without this part), and worse it was mentioned on today's working group call that some wallet implementors...

I guess it's not entirely consistent but the structure seems like just a semi-convention so maybe it's fine?

> Do we need a whole section in VCI on how to encrypt credential response without signing the whole payload again? That's what is already there as far as I...

Perhaps the `wallet_issuer` and `user_hint` parameters should be removed along with the note? They have honestly never made sense to me and still don't.

#473 is related in so far as I can tell

> I support removing batch credential endpoint given that we merge #293 and credential endpoint has possiblities [sic] to issue multiple Credential instances for the same Credential Dataset. I support...

> > I'm also in favour of removing the batch credential endpoint for all the reasons already highlighted. > I'm also in favor of removing the batch credential endpoint for...

> Open: use different parameter name for passing the ephm encryption key? Leaning towards changing the name. Note that the existing section on using JARM will need to be updated...

I'll go on record here as being not a fan of PE.