From b46042cd8f1484763e92f7bce86dc397ac9ab3a6 Mon Sep 17 00:00:00 2001 From: Lal Chandran Date: Fri, 4 Jun 2021 22:19:22 +0200 Subject: [PATCH] Version 1.0 - Released to W3C --- docs/did-spec.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/did-spec.md b/docs/did-spec.md index f5f4f8f..3d832a2 100644 --- a/docs/did-spec.md +++ b/docs/did-spec.md @@ -100,7 +100,6 @@ Example of MyData/iGrant.io DID document: } ``` - The property `service` is optional. The service defined with type `DIDComm` describes an agent that supports DIDComm capabilities which may or may not be iGrant.io specific DIDComm protocols. For e.g. A Data Subject could trigger a `revoke-notification` DIDComm message to inform a Data Using Service’s service endpoint that a Data Agreement is added to the revocation list. ## 4. DID Operation Definitions @@ -214,9 +213,9 @@ To resolve a DID and fetch the associated DID document from the DID registry, a } ``` -The **did attribute in the message body represents the DID that will be resolved. +The did attribute in the message body represents the DID that will be resolved. -The above example requests ADA service to resolve `did:mydata:0:z6MkfiSdYhnLnS6jfwSf2yS2CiwwjZGmFUFL5QbyL2Xu8z2E` Notice the message json+ld doesn’t contain a **from key, since the read operation can be performed without owning a DID. The packing algorithm used for constructing the DIDComm encryption envelope should be anoncrypt. +The above example requests ADA service to resolve `did:mydata:0:z6MkfiSdYhnLnS6jfwSf2yS2CiwwjZGmFUFL5QbyL2Xu8z2E` Notice the message json+ld doesn’t contain a from key, since the read operation can be performed without owning a DID. The packing algorithm used for constructing the DIDComm encryption envelope should be anoncrypt. The ADA service will respond to the above DIDComm message with an encryption envelope (JWE) which when unpacked will contain a DIDComm plaintext message of type - [https://didcomm.org/mydata-did/1.0/read-did-response](https://didcomm.org/mydata-did/1.0/create-did-response). An example is given below: @@ -286,7 +285,7 @@ In the current version of this specification, delete is relevant only when trigg } ``` -The **did attribute in the message body represents the DID that will be marked as revoked. +The did attribute in the message body represents the DID that will be marked as revoked. The packing algorithm used for constructing the DIDComm encryption envelope should be authcrypt.