Make OpenID4VP over the Digital Credentials API more generic
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
The OpenID4VP over the Digital Credentials API section currently has some wording that makes assumptions about how native App Platform DC API equivalents in operating systems are implemented.
Since there are very few of these currently in existence and it is not clear that they will all work the same way, we should try to make the text more generic.
In particular:
- There is some text talking about how the origin of the verifier is "transported", but some platforms might just generate origins directly at each end.
- The text about use of platform-specific application origins introduced in #761 should be made more generic if possible
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
Start with the OpenID4VP over the Digital Credentials API section and review the platform-specific application-origin wording introduced in #761. Generalize references to transported origins and platform implementations without assuming identical behavior, while preserving the intended protocol requirements.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100