Support `did` as trusted authorities for DCQL
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
Based on a comment I initially added to #479:
One issue i see for w3c VCs is that issuer based matching with DCQl can become quite complex, as you don't know whether to query ['issuer'] or ['issuer', 'id'].
So if you would use claim sets, you'd have to duplicate all claim sets. I know the WG decided against adding did as a trusted authority mechanism, but it would make issuer matching a lot easier IMO.
A similar limitation is there for AnonCreds credentials, as there is not really an issuer_did property to query on.
I think adding support for DIDs to trusted authorities would make querying for DID based issuers a lot easier across credential formats that support DIDs.
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 the linked context in #479 and review the DCQL trusted-authority discussion. Trace how issuer matching is represented for W3C VCs and AnonCreds, then define the semantics needed for DID-based trusted authorities. Done means the behavior is specified consistently across credential formats without requiring duplicated claim sets.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100