Future of identities in dataspaces (DAPS, DCP with DIDs and VCs)

[casemsee]

Recently, there has been significant progress in identity in dataspaces , focusing on trust and decentralised identity management.

As we consistently work on dataspaces projects, we are quite curious to know about the future of DAPs (Dynamic Attribute Provising Service. Will it be replaced by the Decentralised Claims Protocol (DCP) with verified credentials, an identity hub in EDC, and wallets? Regarding the latter, they are quite complex to implement with limited use cases, such as the Catena-X or Manufacturing X project.

What is the current maturity level of DCP? Is it implemented on operational dataspaces?

[jimmarino]

A few initial:

• DAPS is not a standard or affiliated with any Dataspace-related specifications at the Eclipse Foundation (DSP, DCP).
• DAPS and DCP address completely different use cases and architectures, one centralized, another decentralized.
• I don't know what your requirements or use cases are, so I can't comment about whether DSP, DCP, or any other technology is appropriate for your scenario (and the EDC committers generally won't do that anyway). You'll need to decide for yourself.

That said, what is so complex about DCP and Identity Hub? The DCP presentation flow is two REST endpoints and I would claim it is a lot simpler than other related protocols.

[casemsee]

Thanks, Jim.

Our requirement is to have unified trsut mechanisms across dataspaces. For instance, some of our participants are using IDS DAPs as their identity provider in their implementation, and some are EDC identity hub with DIDs and VCs. While testing a technical interoperability between different participants (data exchange), we realised that the identity authentication/verifications mechanisms are different across two. Hence not interoperable