Support rendering of compound linked credentials
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9
- Forks
- 8
- Avg merge
- 14d 42m
- Merged PRs (30d)
- 2
Description
There's several examples of complex compound credentials (LER-RS resumes, CLRv2, etc) that embed many VCs in an "outer" container credential. Example of an app that produces a compound LER-RS credential: https://resume.allskillscount.org/
BUT, a complementary, and possibly preferable, approach (brought up by @paulfdietrich and the DB folks) is to model compound credential as an outer container credential with LINKS (secured by digest hash) to other VCs in a presentation.
This issue is -- how to indicate that a renderMethod template is intended to include these linked credentials? So, for example, if you have an LER-RS credential, which includes 3 VCs (linked to them, with digest hash), do we need any special affordances in the renderMethod section that says "also include those linked VCs when rendering this template?"
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
Review the LER-RS and CLRv2 examples, the linked-VC presentation approach, and the renderMethod section described in the issue. Done means deciding and documenting whether renderMethod needs an explicit way to include linked credentials when rendering a compound credential.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100