The Eclipse Dataspace Decentralized Claims Protocol (DCP) defines an interoperable overlay to the Dataspace Protocol (DSP) Specifications for conveying organizational identities and establishing trust in a way that preserves privacy and limits the possibility of network disruption.
The scope of Eclipse DCP specification includes:
- Specifying a format for self-issued identity tokens
- Defining a protocol for storing and presenting Verifiable Credentials and other identity-related resources
- Defining a protocol for parties to request credentials from a credential issuer
Eclipse DCP supports multiple trust anchors and allow participants to manage and verify presentations without needing third-party systems outside their control. Note that it is not a requirement for Eclipse DCP to specify a decentralized or "self-sovereign" identity protocol, but it may be based on it.
The following are out-of-scope for Eclipse DCP:
- The definition of verifiable credentials types and schemas. This work should be done by other expert groups aligned with industry and use-case-specific requirements.
- The definition of semantic models for trust. The creation of semantic trust models should be done by other expert groups and aligned with DCP through the *W3C Verifiable Credential Data Model*.
- The definition of specific ODRL policy vocabularies. This work should be done by other expert groups aligned with industry and use-case-specific requirements.
Name | Date |
---|
Name | Date |
---|---|
Creation Review | 2024-06-05 |
For more information about the patent licenses, view the Eclipse IP Policy page.