Merge branch 'main' of github.com:decentralised-dataexchange/automate…

…d-data-agreements
fredriklinden · Dec 3, 2021 · 06ff728 · 06ff728
2 parents 2bd2bc1 + f238e56
commit 06ff728
Show file tree

Hide file tree

Showing 3 changed files with 28 additions and 10 deletions.
diff --git a/README.md b/README.md
@@ -1,5 +1,5 @@
 <h1 align="center">
-    Automated Data Agreements Project (NGI eSSIF-Lab)
+    Data Agreements for enabling auditable personal data exchange
 </h1>
 
 <p align="center">
@@ -29,8 +29,8 @@ The key deliverables of the project are as given. The table summarises the relea
 | Milestone    	| Date             	| Deliverables                                                                                                                                	|
 |:--------------	|:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------	|
 | Milestone 01 	| 15 May 2021      	| 1. [Functional specification](https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/functional_specification.md)<br>2. [Interface specification](https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/interface_specification.md) <br>3. [Envisioned interoperability (eSSIF-Lab gitlab)](https://gitlab.grnet.gr/essif-lab/infrastructure_2/igrantio/deliverables/-/blob/master/envisioned_interoperability_with_others.md)                            	|
-| Milestone 02 	| 15 November 2021 	| 1. Interim demo<br>2. [Data Agreement specification](https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/data-agreement-specification.md)<br>3. [Data Agreement DID method specficication](https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/did-spec.md)<br>4. [Data Agreement DIDComm protocol specification](https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/didcomm-protocol-spec.md)<br>5. [Data Agreement APIs Rel. 1.0.1](https://app.swaggerhub.com/apis/iGrant.io/ADA/1.0.1)	|
-| Milestone 03 	| 15 December 2021 	| 1. Feasibility plan<br>2. Project report                                                                                                    	|
+| Milestone 02 	| 15 December 2021 	| 1. Interim demo<br>2. [Data Agreement specification](https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/data-agreement-specification.md)<br>3. [Data Agreement DID method specficication](https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/did-spec.md)<br>4. [Data Agreement DIDComm protocol specification](https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/didcomm-protocol-spec.md)<br>5. [Data Agreement APIs Rel. 1.0.1](https://app.swaggerhub.com/apis/iGrant.io/ADA/1.0.1)	|
+| Milestone 03 	| 15 January 2022 	| 1. Feasibility plan<br>2. Project report                                                                                                    	|
 
 ## Contributing
 

diff --git a/docs/data-agreement-specification.md b/docs/data-agreement-specification.md
@@ -120,7 +120,7 @@ The focus of this specification is on the Data Agreement, how it is defined, pre
 
 There can be two forms of agreements between two organisations. 
 
-The first form of agreement is between organisations where one organisation acts as a Data Source and the other as Data Using Service. In this case, both organisations share the role as data controller and are responsible for managing their compliance requirements. They may have made their own privacy risk assessment, documented in a data protection impact assessment (DPIA) report, and concluded whether any additional mitigation effort was required. This agreement is referred to as **Data Disclosure Agreement**, which, though not yet standardised, captures the agreement between two organisations on how data is shared and what obligation each party has. This can be realised as a contract or in terms of use. The individual (data subject) is engaged with both organisations. For each organisation, there exists a **Data Agreement **with an associated privacy policy that explains the purpose of processing personal data, what personal data is collected, data subject rights, etc.
+The first form of agreement is between organisations where one organisation acts as a Data Source and the other as Data Using Service. In this case, both organisations share the role as data controller and are responsible for managing their compliance requirements. They may have made their own privacy risk assessment, documented in a data protection impact assessment (DPIA) report, and concluded whether any additional mitigation effort was required. This agreement is referred to as **Data Disclosure Agreement**, which, though not yet standardised, captures the agreement between two organisations on how data is shared and what obligation each party has. This can be realised as a contract or in terms of use. The individual (data subject) is engaged with both organisations. For each organisation, there exists a **Data Agreement** with an associated privacy policy that explains the purpose of processing personal data, what personal data is collected, data subject rights, etc.
 
 ![](images/data-agreements-ds-dus-2.png) 
 

diff --git a/interface-specs/data-agreement-schema/v1/data-agreement-schema.json b/interface-specs/data-agreement-schema/v1/data-agreement-schema.json
@@ -38,16 +38,34 @@
   },
   "event": [
     {
+      "id": "did:mydata:z6MkiTBz1ymuepAQ4HEHYSF1H8quG5GLVVQR3djdX3mDooWp#1",
       "time-stamp": "2021-05-08T08:41:59+0000",
-      "principle-did": "did:mydata:1:<sender_did_value>",
-      "state": "<Definition/Prepration/Capture>",
-      "authenticity": "<signature>"
+      "principle-did": "did:mydata:z6MkiTBz1ymuepAQ4HEHYSF1H8quG5GLVVQR3djdX3mDooWp",
+      "state": "<Definition/Prepration/Capture>"
     },
     {
+      "id": "did:mydata:z6MkGskxnGjLrk3gKS2mesDpuwRBokeWcmrgHxUXfnncxiZP#2",
       "time-stamp": "2021-05-08T08:41:59+0000",
-      "principle-did": "did:mydata:1:<sender_did_value>",
-      "state": "<Definition/Prepration/Capture>",
-      "authenticity": "<signature>"
+      "principle-did": "did:mydata:z6MkGskxnGjLrk3gKS2mesDpuwRBokeWcmrgHxUXfnncxiZP",
+      "state": "<Definition/Prepration/Capture>"
+    }
+  ],
+  "proofChain":[
+    {
+      "id": "did:mydata:z6MkiTBz1ymuepAQ4HEHYSF1H8quG5GLVVQR3djdX3mDooWp#1",
+      "type": "Ed25519Signature2020",
+      "created": "2021-05-08T08:41:59+0000",
+      "verificationMethod": "did:mydata:z6MkiTBz1ymuepAQ4HEHYSF1H8quG5GLVVQR3djdX3mDooWp",
+      "proofPurpose": "contractAgreement",
+      "proofValue": "z6MkwW6aqMnjgrhJXFUko3NnZPGzVpkNzhYK7yEhnsibmLwLz6MkwW6aqMnjgrhJXFUko3NnZPGzVpkNzhYK7yEhnsibmLwL"
+    },
+    {
+      "id": "did:mydata:z6MkGskxnGjLrk3gKS2mesDpuwRBokeWcmrgHxUXfnncxiZP#2",
+      "type": "Ed25519Signature2020",
+      "created": "2021-05-08T08:41:59+0000",
+      "verificationMethod": "did:mydata:z6MkGskxnGjLrk3gKS2mesDpuwRBokeWcmrgHxUXfnncxiZP",
+      "proofPurpose": "contractAgreement",
+      "proofValue": "z6MkGskxnGjLrk3gKS2mesDpuwRBokeWcmrgHxUXfnncxiZPz6MkGskxnGjLrk3gKS2mesDpuwRBokeWcmrgHxUXfnncxiZP"
     }
   ]
 }