Kristina

not in scope for 1.0. will re-open if needed in 1.1

I have heard a similar feedback before. Basically, the question it, "the wallet needs to display information about the RP (terms of services, logo, etc.) From where should the RP...

Is it possible to add description to the PR what this PR does and which issues it touches upon? thank you

discussed on a WG call: - option 1: key attestation is pre-generated, there is no nonce in key attestation, in which case freshness and replay prevention is proven by proof...

also worth clarifying that since nonce is mandatory in key attestation, without nonce endpoint, wallets cannot use key attestation proof type.

from https://github.com/openid/OpenID4VCI/pull/389#issuecomment-2405477640 > use 1 jwt proof type and key attestation with 10 keys I think we should decide explicitly what should be the behavior in this case: A) Issuer...

discussion during the WG direction: - proceed with this PR - keep discussing platform native attestations in a separate issue ( @leecam will open an issue); - please open an...

I think we need to wait for a resolution on https://github.com/w3c/vc-data-model/issues/914 before we merge this PR. FWIW, I agree with Tobias, it should be relative or absolute, not either. and...

breaking change for the wallet, if we make this change, the header must change.

WG discussion as documented here: https://github.com/openid/OpenID4VP/issues/561#issuecomment-2877718053 also add a generic text that applies to all client identifier schemes that clarifies the behavior.