Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces
DPG
General Information
Solution name
Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces
Aliases (if any)
DEXA,PS-SDA, DATASPACE, EHDS
Solution category
Open Software
Short description
DEXA protocol is key for developing and deploying trustworthy, human-centric decentralised data applications (dApps) across domains using data intermediation services within dataspaces.
Website
https://ontochain.ngi.eu/content/ps-sda
Where is your main solution’s source hosted?
https://github.com/decentralised-dataexchange/data-exchange-agreements , https://github.com/decentralised-dataexchange/dexa-protocol , https://github.com/decentralised-dataexchange/dexa-sdk , https://github.com/decentralised-dataexchange/dexa-smartcontracts
Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces
Aliases (if any)
DEXA,PS-SDA, DATASPACE, EHDS
Solution category
Open Software
Short description
DEXA protocol is key for developing and deploying trustworthy, human-centric decentralised data applications (dApps) across domains using data intermediation services within dataspaces.
Website
https://ontochain.ngi.eu/content/ps-sda
Where is your main solution’s source hosted?
https://github.com/decentralised-dataexchange/data-exchange-agreements , https://github.com/decentralised-dataexchange/dexa-protocol , https://github.com/decentralised-dataexchange/dexa-sdk , https://github.com/decentralised-dataexchange/dexa-smartcontracts
1. SDG Relevance
Which SDG/s is your solution relevant to?
SDG9: Industry¸ Innovation and Infrastructure,SDG11: Sustainable Cities and Communities
How is your solution relevant to each SDG you’ve selected above?
The DEXA protocol facilitates sustainable personal exchange for organisations, ensuring that all data transactions are lawful, scalable and verifiable. An organisation can be a Data Source or a Data Using Service. The DEXA protocol brings in the requisite trust and governance to establish a ubiquitous data exchange marketplace while empowering individuals to control their data. All organisations need to ensure that they are on the right side of the law (e.g. the GDPR) when consuming personal data (risk management) and to establish the digital trust needed for individuals to say yes to sharing their data.
SDG9: Industry¸ Innovation and Infrastructure,SDG11: Sustainable Cities and Communities
How is your solution relevant to each SDG you’ve selected above?
The DEXA protocol facilitates sustainable personal exchange for organisations, ensuring that all data transactions are lawful, scalable and verifiable. An organisation can be a Data Source or a Data Using Service. The DEXA protocol brings in the requisite trust and governance to establish a ubiquitous data exchange marketplace while empowering individuals to control their data. All organisations need to ensure that they are on the right side of the law (e.g. the GDPR) when consuming personal data (risk management) and to establish the digital trust needed for individuals to say yes to sharing their data.
2. Open Licensing
Which open license(s) is/are used by your solution?
Apache-2.0
Provide evidence of use of the selected open license(s).
https://github.com/decentralised-dataexchange/dexa-protocol/blob/main/LICENSE
Apache-2.0
Provide evidence of use of the selected open license(s).
https://github.com/decentralised-dataexchange/dexa-protocol/blob/main/LICENSE
3. Clear Ownership
Who owns this digital solution?
iGrant.io, Sweden (LCubed AB)
Provide evidence(s) of ownership.
https://github.com/decentralised-dataexchange/dexa-protocol/blob/main/LICENSE
iGrant.io, Sweden (LCubed AB)
Provide evidence(s) of ownership.
https://github.com/decentralised-dataexchange/dexa-protocol/blob/main/LICENSE
4. Platform Independence
Does this solution use any closed components that create proprietary dependency?
No
No
5. Documentation
Where is your solution’s documentation?
https://github.com/decentralised-dataexchange/dexa-protocol
https://github.com/decentralised-dataexchange/dexa-protocol
6. Mechanism for Extracting Data
Does your solution collects or uses non-PII data and/or content?
No
No
7. Privacy & Applicable Laws
Provide a list of relevant privacy, domestic and other applicable international laws your solution complies with.
GDPR Uses Data Protection Impact Assessment (DPIA) as the basis for creation of any Data Agreement. DPIA is owned by organisations that are part of the ecosystem. This is an open-source code for anyone to use and be part of a data exchange ecosystem.,https://igrant.io/privacy.html#privacy
Provide evidence(s) of adherence with the laws mentioned above.
The solution is based on a DPIA (Data Protection Impact Assessment), which is the first step in the process flow. This is the responsibility of the organisation adopting the SW component.
GDPR Uses Data Protection Impact Assessment (DPIA) as the basis for creation of any Data Agreement. DPIA is owned by organisations that are part of the ecosystem. This is an open-source code for anyone to use and be part of a data exchange ecosystem.,https://igrant.io/privacy.html#privacy
Provide evidence(s) of adherence with the laws mentioned above.
The solution is based on a DPIA (Data Protection Impact Assessment), which is the first step in the process flow. This is the responsibility of the organisation adopting the SW component.
8. Standards & Best Practices
Provide a list of the open standards your solution adheres to and demonstrate adherence.
Security - HTTPS, SSL, SSH, RS256, ED2556, AnonCreds, Supported Authentication & Authorization - OAuth 2, OID4VC, OID4VP, OIDC and JWT (JSON Web Tokens), Data exchange supported formats - JSON References: - https://github.com/decentralised-dataexchange/dexa-protocol - https://digitalprinciples.org/principle/use-open-standards-open-data-open-source-and-open-innovation/
Provide a list of best practices & principles your solution adheres to and demonstrate adherence.
We follow agile development as a company: https://www.ntaskmanager.com/blog/agile-best-practices/ It also follows open source standard practices.
Security - HTTPS, SSL, SSH, RS256, ED2556, AnonCreds, Supported Authentication & Authorization - OAuth 2, OID4VC, OID4VP, OIDC and JWT (JSON Web Tokens), Data exchange supported formats - JSON References: - https://github.com/decentralised-dataexchange/dexa-protocol - https://digitalprinciples.org/principle/use-open-standards-open-data-open-source-and-open-innovation/
Provide a list of best practices & principles your solution adheres to and demonstrate adherence.
We follow agile development as a company: https://www.ntaskmanager.com/blog/agile-best-practices/ It also follows open source standard practices.
9A. Data Privacy & Security
Does your solution allow the collection / storage / distribution of PII data?
PII data is NOT collected NOT stored and NOT distributed.
How can your solution ensure data privacy & security?
Uses Data Protection Impact Assessment as the basis for creation of any Data Agreement https://igrant.io/privacy.html#privacy
PII data is NOT collected NOT stored and NOT distributed.
How can your solution ensure data privacy & security?
Uses Data Protection Impact Assessment as the basis for creation of any Data Agreement https://igrant.io/privacy.html#privacy
9B. Inappropriate & Illegal Content
Does your solution allow the collection / storage / distribution of content?
Content is NOT collected NOT stored and NOT distributed.
Content is NOT collected NOT stored and NOT distributed.
9C. Protection from Harassment
Does your solution facilitate or enables interactions with or between users and/or contributors?
Yes
How does your solution enables users and contributors to protect themselves from harassment.
It follows code of conduct relevant for open source project and community driven knowledge sharing. Based on code or conduct as stated at: https://github.com/decentralised-dataexchange/data-exchange-agreements/blob/main/CODE-OF-CONDUCT.md
Yes
How does your solution enables users and contributors to protect themselves from harassment.
It follows code of conduct relevant for open source project and community driven knowledge sharing. Based on code or conduct as stated at: https://github.com/decentralised-dataexchange/data-exchange-agreements/blob/main/CODE-OF-CONDUCT.md
Scale of Solution
Where was this solution developed?
India,Sweden
Where is this solution actively deployed? (optional)
India,Sweden
Are there any multi-lateral organisations using your solution?
International Telecommunication Union
Who is using your solution? (optional)
Part of the European Wallet Consortium (EWC) and various public sector initiatives in Sweden and Europe.
Who else is using your solution?
Apart from our customers, the solution is live in production.
Has your solution received any awards and/or recognition in the last one year?
IEEE now accepts a related paper. It's available at: https://igrant.io/whitepaper.html
India,Sweden
Where is this solution actively deployed? (optional)
India,Sweden
Are there any multi-lateral organisations using your solution?
International Telecommunication Union
Who is using your solution? (optional)
Part of the European Wallet Consortium (EWC) and various public sector initiatives in Sweden and Europe.
Who else is using your solution?
Apart from our customers, the solution is live in production.
Has your solution received any awards and/or recognition in the last one year?
IEEE now accepts a related paper. It's available at: https://igrant.io/whitepaper.html
Application Details
| DPG ID | GID0090210 |
| Application ID | 10962 |
| Parent Application ID | 10243 |
| Status | DPG |
| Date Created | 29-09-2023 06:23 AM UTC |
| Date Submitted | 29-09-2023 06:37 AM UTC |
| Date Reviewed | 15-10-2023 09:53 PM UTC |
| Date of Expiry | 21-01-2025 12:00 AM UTC |
Application Log Details
| Timestamp | Activity |
|---|---|
| 22-11-2024 11:15 PM UTC | System created a refresher application for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) (B) |
| 15-10-2023 09:53 PM UTC | Ricardo Torres (L2 Reviewer) submitted their review of Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (152) and found it to be a DPG |
| 15-10-2023 09:53 PM UTC | System unmarked Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) as a nominee |
| 15-10-2023 09:53 PM UTC | Ricardo Torres (L2 Reviewer) passed Scale of Solution for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:53 PM UTC | Ricardo Torres (L2 Reviewer) passed 9C. Protection from Harassment for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:53 PM UTC | Ricardo Torres (L2 Reviewer) passed 9B. Inappropriate & Illegal Content for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:53 PM UTC | Ricardo Torres (L2 Reviewer) passed 9A. Data Privacy & Security for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:53 PM UTC | Ricardo Torres (L2 Reviewer) passed 8. Open Standards & Best Practices for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:52 PM UTC | Ricardo Torres (L2 Reviewer) passed 7. Privacy & Applicable Laws for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:51 PM UTC | Ricardo Torres (L2 Reviewer) passed 6. Non-PII Data Extraction for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:51 PM UTC | Ricardo Torres (L2 Reviewer) passed 5. Documentation for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:51 PM UTC | Ricardo Torres (L2 Reviewer) passed 4. Platform Independence for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:51 PM UTC | Ricardo Torres (L2 Reviewer) passed 3. Clear Ownership for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:50 PM UTC | Ricardo Torres (L2 Reviewer) passed 2. Open Licensing for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:50 PM UTC | Ricardo Torres (L2 Reviewer) passed 1. SDG Relevance for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:50 PM UTC | Ricardo Torres (L2 Reviewer) passed General Information for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 15-10-2023 09:48 PM UTC | Ricardo Torres (L2 Reviewer) pulled Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) under review |
| 30-09-2023 03:14 PM UTC | L1 Reviewer (L1 Reviewer) submitted their review of Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 30-09-2023 03:14 PM UTC | System remove tag Late from Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 30-09-2023 03:11 PM UTC | L1 Reviewer (L1 Reviewer) passed Scale of Solution for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 30-09-2023 03:11 PM UTC | L1 Reviewer (L1 Reviewer) passed 9C. Protection from Harassment for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 30-09-2023 03:10 PM UTC | L1 Reviewer (L1 Reviewer) passed 9B. Inappropriate & Illegal Content for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 30-09-2023 03:10 PM UTC | L1 Reviewer (L1 Reviewer) passed 9A. Data Privacy & Security for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 30-09-2023 03:10 PM UTC | L1 Reviewer (L1 Reviewer) passed 8. Open Standards & Best Practices for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 30-09-2023 03:08 PM UTC | L1 Reviewer (L1 Reviewer) passed 7. Privacy & Applicable Laws for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 30-09-2023 03:08 PM UTC | L1 Reviewer (L1 Reviewer) passed 6. Non-PII Data Extraction for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 30-09-2023 08:21 AM UTC | L1 Reviewer (L1 Reviewer) passed 5. Documentation for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 29-09-2023 10:00 PM UTC | System add new tag Late to Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 29-09-2023 08:51 PM UTC | L1 Reviewer (L1 Reviewer) passed 4. Platform Independence for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 29-09-2023 08:22 PM UTC | L1 Reviewer (L1 Reviewer) passed 3. Clear Ownership for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 29-09-2023 08:21 PM UTC | L1 Reviewer (L1 Reviewer) passed 2. Open Licensing for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 29-09-2023 08:20 PM UTC | L1 Reviewer (L1 Reviewer) passed 1. SDG Relevance for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 29-09-2023 08:20 PM UTC | L1 Reviewer (L1 Reviewer) passed General Information for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 29-09-2023 01:26 PM UTC | L1 Reviewer (L1 Reviewer) edited General Information for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 29-09-2023 01:25 PM UTC | L1 Reviewer (L1 Reviewer) edited General Information for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) |
| 29-09-2023 01:22 PM UTC | L1 Reviewer (L1 Reviewer) pulled Data exchange agreement protocol suit for auditable, privacy-preserving data transactions in dataspaces (10962) under review |
| 29-09-2023 06:37 AM UTC | Lal Chandran (Applicant) submitted application for Data exchange agreement protocol suit for auditable, privacy-preserving data transactions using dataspaces (10962) |
