Kristina

add transaction_data

13

resolves #174 resolves #173 resolves #172 - [x] need to clarify how the hashing function is communicated - [x] add changelog - [x] clarify that transaction data type might require...

ensuring consecutive openid4vp requests are opened in the same wallet

5

I think it is related to a PR 175 and especially a discussion [here](https://github.com/openid/OpenID4VP/pull/175/files#diff-3118c9756a1d7b361bb53af8bd9d65666476a27cfeeced56c47a5dccc38eac55R1836) QES use-case in LSP POTENTIAL has a use-case where they want to do two consecutive requests...

Omission of the presentation_definition_uri is the Browser API extension

8

> The omission of the presentation_definition_uri is understandable in that the platform needs to know which credentials are being requested in order to choose suitable wallets, and using PDURI instead...

co-existence of multiple query languages

4

I think we should have an idea how the co-existence of or transition between two query languages in OpenID4Vp will happen: PE v2 and a new one. Is one or...

add more information on the binding to the origin in browser API

1

Given that binding to the origin is an important security feature, it is important to give more context on how the origin is used. This means we need to cover...

basically profiling annex A of openid4vp

what is revocation/status management mechanism

1

- the Token Status List draft RFC: https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/ . - another proposal: https://c2bo.github.io/draft-bormann-identifier-list/draft-bormann-identifier-list.html

add an option to use credential_configuration_id in credential request

23

Closes one remaining item from PR #294 as agreed on[ May 29th 2024 call](https://github.com/openid/OpenID4VCI/issues/132#issuecomment-2137991476). Closes #132. enables to use credential_configuration_id in the credential request. I am increasingly in favor of...

define where in mdoc presentation to include transaction data

4

for sd-jwt vc, it is in key binding jwt. for mdoc, is it session_transcript?

I think at some point we had a requirement in the document to pass a prefer-header `JWT-interop-profile-0.0.1` when the wallet obtains authorization request object. but I can't find it in...