You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an implicit understanding that parameters such as nonce, client_id and client_id_scheme are used in VPs but we don't have explicit language how this is done for specific format identifiers.
I propose to add language that define that profiles must describe how. For profiles defined by OID4VP, this language should be added to the credential format sections.
The text was updated successfully, but these errors were encountered:
I missed the notes in the credential profiles section that says how this is done. I guess I got confused because the text is below an example and included in a note. I'm wondering whether normative language would make sense similar to what we did for SD-JWT VC and verifier metadata: https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-wg-draft.html#appendix-A.4.2. It would certainly help interoperability. Thoughts?
awoie
changed the title
Define how OID4VP parameters are carried over to VPs
Define how OID4VP parameters are carried over to VPs normatively
May 16, 2024
There is an implicit understanding that parameters such as
nonce
,client_id
andclient_id_scheme
are used in VPs but we don't have explicit language how this is done for specific format identifiers.I propose to add language that define that profiles must describe how. For profiles defined by OID4VP, this language should be added to the credential format sections.
The text was updated successfully, but these errors were encountered: