Incomplete mdoc non-normative example
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
According to the spec:
proof_types_supported: OPTIONAL. Object that describes specifics of the key proof(s) that the Credential Issuer supports. It MUST be present if cryptographic_binding_methods_supported is present, and omitted otherwise.
But the example in section A2.2 include the cryptographic_binding_methods_supported, but not the proof_types_supported. All other examples for e.g. sd-jwt-vc do.
Either cryptographic_binding_methods_supported gets removed or proof_types_supported will be added. I would suggest to add it to be aligned with the other examples.
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
Open section A2.2 of the linked OpenID4VCI specification and compare its credential issuer metadata example with the stated requirement for proof_types_supported. Update the example by either adding proof_types_supported or removing cryptographic_binding_methods_supported, then verify it remains consistent with the specification and the other examples.
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
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100