[S2S]: Define common list of VerificationData Types
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Current specification does not define any VerificationData types. Defining a common set of known ones would be useful. The highest value ones are likely:
- Credential Presentation
- auth_on_web
Known wallet-collected data useages
- US/Other DL ( Photo front/back of DL, QR code, liveness/selfie)
- Passport
- PID
- OTP
Potentially bucketed in here:
- preauth/device migration
Part of what we should decide is what has enough value for us to publish vs allowing ecosystems to define their own.
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 by reviewing the current OpenID4VCI specification and how VerificationData is currently referenced, since the issue states that no types are defined. Compare the proposed credential presentation, auth_on_web, wallet-collected data, and migration categories, then establish which common types should be published versus left to ecosystems; done means that scope and the common list are agreed and specified.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100