Kristina
Kristina
currently, HAIP is silent on c_nonce. Probably makes sense to mandate it.
for interoperability. if we can have only one option in OpenID4VP is better. for mdoc, preference seems to be AKI
at least in the short-mid term, support for Batch Issuance is crucial for verifier-verifier unlinkability. also minimum batch size needs to be defined. suggestion would be `10`.
like in FAPI https://openid.net/specs/fapi-2_0-security-profile-ID2.html#section-5.3
discussed in the WG. QES probably out of scope since it is eIDAS construct. payments is global. would be worth calling payment type explicitly. will open an issue to discuss...
I am sorry if this is a duplicate - I think there was an issue somewhere, but can't find it right away. Is there a plan to handle a situation...
Multiple non-final specifications are referenced in HAIP. we should add a note about their versions. Precedent in VP and VCI: - VP: https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-wg-draft.html#section-13.4 - VCI: https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html#section-14.7 related issues: https://github.com/openid/OpenID4VCI/issues/456 https://github.com/openid/OpenID4VP/issues/409
As per @Sakurann's comment we'll discuss whether to move some of this to the VP spec and will separately handled the discussion about origin vs url in #629, so please...
The intent of having both attestation and jwt proof types was the following: A. jwt proof type: `key_attestation` in the jwt proof header can be pre-generated (attested keys in the...
Building up on the problem described in https://github.com/w3c-fedid/digital-credentials/issues/382. We had a discussion at IIW, and integration for the following option 3 into VCI seems to be preferred by the DCP...