Joseph Heenan

Thanks for your thoughts Judith! > Isn't a "credential instance" what people commonly refer to as "a credential"? If not, how do they differ? It probably depends who you mean...

Thanks Paul. There actually may be a small subtly that makes 'credential instance' a useful term even when using non-sd or zkp credentials, and I've perhaps not captured this in...

I'm slightly reluctant to ever use the term 'credential' standalone in the specification, but it's definitely an option if we clearly define it. I guess the problem isn't just the...

I feel there are potential concerns we should discuss before removing it. The claims parameter allows the wallet to avoid being exposed to PII that it does not wish to...

Just because there is a feature in the spec that allows a confusing UX doesn't mean that wallets have to implement a confusing UX. The important question is whether there...

> I am not a GDPR expert, but if the only motivation to keep this feature is to satisfy these kinds of regulations, then I believe these regulations can be...

@cobward > Maybe I have a different definition of wallet. In my understanding, a wallet is not an application built for the sole purpose of storing and presenting particular credential...

@paulbastian did you have a look at the video I mentioned in one of my previous comments, https://www.youtube.com/watch?v=2wrNN0twlL4 ? > If an issuer is interested in doing such a thing,...

> @jogu Are you saying the wallet can decide what fields should be provisioned into the credential, regardless of user consent? The user wishes to receive a credential that contains...

@paulbastian > I have the feeling that the mandatory flag seems unclear then. Agreed, based on above I think we should try to more fully define the mandatory flag.