Kristina

how much do we need to actually expand given that we have pretty extensive security considerations sections in VP and VCI?

also, don't we need a text that kid, jwk and x5c are mutually exclusive?

could we use the same syntax for mdocs and sd-jwt for path? so that it is path: [, ] as opposed to { namespace : "", data_element: ""}?

please make it clear that > ? - I need this, so don’t return the response if you don’t have it > ?? - this is nice to have, send...

> As also mentioned in this comment: https://github.com/openid/OpenID4VP/pull/266/files#r1775413078 optionality should not exist for data elements or credentials but only on a use-case basis. Within satisfying a certain use case, optionality...

char hat on. re-requesting review from everyone who had previously commented/reviewed, including those who already approved, since a lot has been changed. **This is a version we are looking to...

the use of `self-issued.me/v2` should be used only when static SIOP metadata is used. that static metadata is bound to the usage of a custom url scheme `openid:`. https://openid.net/specs/openid-connect-self-issued-v2-1_0-ID1.html#section-8.1 because...

Text in this PR does not sufficiently decouple openid4vp text and still makes it susceptible to any future breaking changes in the credentials API. "Put openid4vp request parameters in an...

I think what is meant is "in places where the referenced specification says "optional", this interop profile will mandate one of the options for the sake of interoperability, and if...

Microsoft uses types in presentation definition for the verifier to request certain credentials and the wallet to filter a requested credential. The rationale was - we do not use JSON-LD,...