Fix #2

docs/did/spec.md

@@ -66,23 +66,21 @@ did:mydata:zJ53MfXX934iYwx6hdQRKonWkVj22t9NczBmwe7To2Yh2sTnS7W32ocTYgvwtQRB3K
 
 ## Operations
 
-Each DID registry service will be exposing a DIDComm agent. CRUD operations on DID can then be performed using available DIDComm messages. A new DIDComm protocol ([https://didcomm.org/mydata-did/2.0](https://didcomm.org/mydata-did/2.0)) is specified below for performing CRUD operations. The DID registry service itself will be allocated a DID and an associated DID document will be publicly available at a well-known DID configuration endpoint (`"/.well-known/did-configuration.json"`) of the web server. The audience of this document is expected to be familiar with DIDComm message specification [4] and it’s extensions.
+Each DID registry service will be exposing a DIDComm agent. CRUD operations on DID can then be performed using available DIDComm messages. A new DIDComm protocol (URI: did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/mydata-did/2.0/) is specified below for performing CRUD operations. The DID registry service itself will be allocated a DID and an associated DID document will be publicly available at a well-known DID configuration endpoint (`"/.well-known/did-configuration.json"`) of the web server. The audience of this document is expected to be familiar with DIDComm message specification [4] and it’s extensions.
 
 ### Create
 
-The did:mydata identifier corresponds to an artefact in MyData ecosystem. Support artefacts are:
+The did:mydata identifier corresponds to an artefact in any data ecosystem served by any data intermediation service such as iGrant.io. Supported artefacts are:
 
-- Agreements - Records the conditions under which 2 parties have come to agreement. Meaning both parties are getting “informed” about the terms.
-    - [Data Disclosure Agreement (DDA)](https://github.com/decentralised-dataexchange/data-exchange-agreements/blob/main/interface-specs/data-disclosure-agreement-schema/data-disclosure-agreement-schema-context.jsonld)
-    - Data Agreement (DA)
+- Agreements - Records the conditions under which two parties have come to agreement. Meaning both parties are getting “informed” about the terms.
+    - [Data Disclosure Agreement (DDA)](https://github.com/decentralised-dataexchange/data-exchange-agreements/blob/4cd82dac0926da89fa3cb180bbe89bd397170bbd/interface-specs/jsonld/contexts/dexa-context.jsonld#L176-L291)
+    - [Data Agreement (DA)](https://github.com/decentralised-dataexchange/data-exchange-agreements/blob/4cd82dac0926da89fa3cb180bbe89bd397170bbd/interface-specs/jsonld/contexts/dexa-context.jsonld#L7-L175)
 - Consents - Records the granular “consent” for personal data described in the data agreement.
 
 Each artefact must conform to a JSONLD context. For e.g. a Data Disclosure Agreement (DDA) must conform to JSONLD context defined [here](https://github.com/decentralised-dataexchange/data-exchange-agreements/blob/main/interface-specs/data-disclosure-agreement-schema/data-disclosure-agreement-schema-context.jsonld). A genesis artefact must be created and did:mydata identifier is generated by embedding artefact as payload in the DID document. Each artefact will have cryptographic material associated to it. Cryptographic material represented as decentralised identifiers will be listed in the controllers property of the DID document. Controllers can make changes to the underlying artefact. Artefact should contains proofs that CONFORMS to  W3C [Data Integrity Model](https://w3c.github.io/vc-data-integrity/) and number of proofs should match the number of controllers. Creation of did:mydata identifiers occurs as result of [DDA protocols](https://dda.igrant.io/protocol/#smart-contracts) (To be elaborated further).
 
 An example DID document is given below.
 
-
-
 ```json
 {
   "@context": [
@@ -384,4 +382,4 @@ If a problem arises while handling the `deactivate-did` message, DID registry se
 7. Aries RFC 0019: Encryption Envelope: [https://github.com/hyperledger/aries-rfcs/tree/master/features/0019-encryption-envelope](https://github.com/hyperledger/aries-rfcs/tree/master/features/0019-encryption-envelope)
 8. IETF RFC 7516 - JSON Web Encryption: [https://datatracker.ietf.org/doc/html/rfc7516](https://datatracker.ietf.org/doc/html/rfc7516) 
 9. Aries RFC 0035 - Report Problem Protocol 1.0: [https://github.com/hyperledger/aries-rfcs/tree/master/features/0035-report-problem](https://github.com/hyperledger/aries-rfcs/tree/master/features/0035-report-problem)
-10. [Data Agreement Specification](https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/data-agreement-specification.md), ADA Project, eSSIF-Lab Infrastructure 
+10. [Data Agreement Specification](https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/data-agreement-specification.md), ADA Project, eSSIF-Lab Infrastructure