Update spec.md

Signed-off-by: George J Padayatti <[email protected]>

docs/did/spec.md

@@ -79,14 +79,6 @@ The did:mydata identifier corresponds to an artefact in MyData ecosystem. Suppor
 
 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).
 
-~~Creation of the identifier assumes that through an out-of-band/didcomm interaction actors involved in the agreement has arrived at terms, i.e both (if 2 actors are involved) parties holds an agreement document with a proof chain ([Data Integrity Model](https://w3c.github.io/vc-data-integrity/)) in it~~. 
-
-***~~The approach propose the creation of the did:mydata identifier after the negotiation, that doesn’t make sense considering, the document will have constant updates. Therefore the controller can create the Genesis Agreement and generate the identifier out of it. Subject can then propose changes.~~***
-
-~~The agreement document must conform to JSONLD context matching the agreement type, for e.g.~~
-
-~~Specification also assumes the parties involved in the agreement has created the cryptographic material to sign the agreement. The cryptographic material represented as decentralised identifiers based on the DID method chosen by the party. These DIDs then act as the controller for the DID document associated with did:mydata identifier. The DID document associated with the did:mydata identifier contains the agreement as payload.~~ 
-
 An example DID document is given below.