contents of wallet_metadata not clearly defined
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
As per https://gitlab.com/openid/conformance-suite/-/work_items/1938 the certification team received a query.
I don't think the spec is clear about the contents of wallet_metadata.
The particular query is whether response_types_supported (and issuer) needs to be present, as RFC8414 requires.
OID4VP says:
wallet_metadata: OPTIONAL. A string containing a JSON object containing metadata parameters as defined in Section 10.
and then section 10 ( https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-1_0-wg-draft.html#section-10.1 ) doesn't really make clear what exactly 'containing metadata parameters as defined in Section 10' means - it does reference RFC8414 and define entries in RFC8414's IANA registry.
None of the wallet_metadata examples in the specification included response_types_supported or issuer.
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
Read the wallet_metadata definition and Section 10.1 of OID4VP, then compare them with the cited RFC8414 requirements and the existing wallet_metadata examples. Done means the specification clearly states whether issuer and response_types_supported are required and its examples reflect that decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100