Joseph Heenan

> The fact that the removal is currently being discussed means that someone in the past proposed adding CWT Key Proof to the OID4VCI specification. It would be better to...

Kristina sent an email to the working group on 23rd July too asking for feedback on removing this: https://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/Week-of-Mon-20240722/000406.html (and no feedback received so far other than above comments on...

> the issuer MUST expose their public encryption key in the jwks metadata parameter. I don't understand how this is related to response encryption. Did you mean "the wallet MUST...

> While polling is easy to implement, it will only work when the app is in foreground. So a push notification mechanism is the preferred way from an iOS or...

I'm interested to know what the advantage of building our own mechanism is instead of relying on the shared signals framework?

Discussed (briefly) on today's WG call: There have been some arguments made that this is a non-breaking change and that we don't have any implementation experience yet, so it would...

Disccsed on 1st May WG call: Moving to 1.1 seems okay. It is important but it is just additive (no breaking changes so doesn't need to be in 1.0) and...

> @jogu I am simply trying to resolve issue #201, because the issue rightly pointed out that HTTP GET and redirect is not what most implementers use - QR code...

> > I think it is implying that the endpoint URL is treated as the empty string and hence the qr code would contain start with '?' but this isn't...

I believe this has been superseded by https://github.com/openid/OpenID4VCI/pull/380 - closing on that basis to keep the PR list to items we're actively working on, please feel free to reopen if...