Skip to content

Commit e5a590e

Browse files
authored
update protocol denominations to the acronyms defined in the summary section
1 parent cc93318 commit e5a590e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

DCPvsOID/DCPvsOID.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,9 @@ Policies, which define the rules and expectations within the dataspace, serve as
1313
At last, Evidences bring additional information to support one or more claims and facilitate the risk-assessment made by the participating entities.
1414

1515
Those policies, claims and evidences can be securely stored using Verifiable Credentials which ensure among other things, traceability and content-integrity.
16-
There are different types of Verifiable Credentials (W3C VC v1/v2, IETF SD-JWT, ISO mdoc/mDL, AnonCreds, ...) and both Eclipse DCP and OpenID4VC can be used to issue and present W3C Verifiable Credentials.
16+
There are different types of Verifiable Credentials (W3C VC v1/v2, IETF SD-JWT, ISO mdoc/mDL, AnonCreds, ...) and both DCP and OpenID4VC can be used to issue and present W3C Verifiable Credentials.
1717

18-
The reconciliation process begins with verifying claims and evidence against established policies. Leveraging credential exchange protocols such as the Eclipse DCP or OpenID4VC, facilitate the secure presentation of policies, claims and evidence for reconciliation. These protocols enable cryptographic assurances, ensuring that policies, claims and evidences are tamper-proof and verifiable without exposing sensitive underlying data. By validating these claims and evidence in compliance with the dataspace's overarching policies, participating entities can confirm their adherence to shared norms, fostering mutual trustworthiness.
18+
The reconciliation process begins with verifying claims and evidence against established policies. Leveraging credential exchange protocols such as DCP and OID4VC, facilitate the secure presentation of policies, claims and evidence for reconciliation. These protocols enable cryptographic assurances, ensuring that policies, claims and evidences are tamper-proof and verifiable without exposing sensitive underlying data. By validating these claims and evidence in compliance with the dataspace's overarching policies, participating entities can confirm their adherence to shared norms, fostering mutual trustworthiness.
1919

2020
Moreover, this iterative process of reconciliation is dynamic, allowing the dataspace to adapt as policies evolve or as new participants join and new data sharing contracts are being offered. It creates an environment where trust is not a static agreement but an ongoing commitment, harmonized through transparency, accountability, and technological safeguards.
2121

0 commit comments

Comments
 (0)