Clarification on DCQL type inheritance
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#appendix-B.3.5-2.2 specifies that for SDJWT-VC a wallet MAY return credentials that are derived according to SDJWT-VC. There is no specific mention of how this should happen for mdoc (or other format for that reason).
For interoperability purposes I think it would make sense to give more hints or examples on how to actually do it. For certain infrastructure providers it seems to be a very pressing requirement, and leaving it unspecified leads to providers implementing proprietary versions of type inheritance.
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 Appendix B.3.5-2.2 of the OpenID4VP specification and the linked SD-JWT VC section on extending type metadata. Compare the documented SD-JWT-VC behavior with the unspecified mdoc case, then determine what interoperable guidance or examples are needed. Done means the specification clearly explains type inheritance across relevant credential formats.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100