You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
How should DID, WebID, OIDC and VC be compared?
Identify the layer each occupies before comparing combinations.
These names all concern identity, but answer different questions. Consider one workflow: entering a workshop.
| Mechanism | Main question | Still needed |
|---|---|---|
| DID | How is a subject named and verification information resolved under a method? | Who made this request and what may they do? |
| WebID | Which HTTP URI and profile describe the subject? | Authentication and resource access control |
| OpenID Connect | How does an app obtain and validate an identity provider’s authentication result? | Whether the user qualifies for the workshop |
| VC | Who made which verifiable claims about a subject? | Issuer trust and applicability to this operation |
Applications can combine mechanisms through specified protocols and implementations. Conceptual compatibility does not establish automatic interoperability. A useful comparison states versions, verification boundaries and the integrations actually demonstrated.
Sources and further reading
Check your understanding
Must a site using both OIDC and VC have a conceptual conflict?
No. One can handle login while the other supplies claims needed by the service; integration still requires explicit verification rules.
Continue along a learning path
- Compare the layers of identity mechanismsStep 5 of 5