be explicit that bound credentials are not returned in the same order as the proofs were passed
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
When a batch of credential is required, there's nothing in https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-8.3-6.1.1 that says the credentials must be returned in the same order the proofs were passed, so the issuer can use any keys from the list in any order so longer as it never uses one more than once.
It would probably be good to explicitly say this is the case so no wallet assumes the ordering is preserved.
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 section 8.3-6.1.1 of the OpenID4VCI specification linked in the issue. Clarify that bound credentials need not be returned in the order of the supplied proofs, while each key may be used no more than once. Done means the specification explicitly communicates this ordering behavior to wallet implementers.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 82/100