Daniel Fett

Here is a draft how the [syntax designed for Transformed Claims](https://openid.bitbucket.io/ekyc/openid-connect-advanced-syntax-for-claims.html#name-defining-transformed-claims) could be integrated into this proposal to enable more complex matching: ```yaml { "expect_credentials": [ { "group": "pid", "format":...

> Just to make clear I understand the proposal correctly. In order to request the following info: (portrait AND (zip code OR (city AND state), from an ISO mdl, I...

Discussed on the call: We'll remove the alg-related matching for now.

Most important open topics: * Change 'sets' syntax to objects? https://github.com/openid/OpenID4VP/pull/266#discussion_r1791909481 * Keep value and values? https://github.com/openid/OpenID4VP/pull/266#pullrequestreview-2349523429 * Potentially add the modifier `??` to the already existing `?` to enable...

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

We could use `‽` :-)

> 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...

After quite a bit of back and forth, I made changes to this PR that hopefully find a good compromise between all proposed solutions. Based on Tobias' latest proposals, this...

At least we need to be precise about what it means when the claims description object is not present.

Hi Alen, We discussed this among the editors and came to the conclusion that introducing this kind of namespacing right now probably doesn't add value. We don't know yet how...