Define how other specifications define profiles of OID4VP for other credential formats
Open
Nobody has claimed this yet.
lower-priority
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
The specification does not describe how other specifications would define profiles of OID4VP for other credential formats. We should explain at a minimum things like PE/query and encoding of the credential in the presentation, and how they would handover things like nonce and client_id/client_id_scheme to do proper audience binding.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the OID4VP specification and related credential-format specifications first. Document how profiles define PE/query, credential encoding, and hand over nonce, client_id, and client_id_scheme for audience binding; done when these minimum integration points are specified.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100