From 6de2aec0bcab36b7f5352f86a31406a29d0f3f7a Mon Sep 17 00:00:00 2001 From: Stephen Curran Date: Thu, 11 Apr 2024 09:19:49 -0700 Subject: [PATCH] Clarification for did:peer:2 about the use of the short string dm for DIDComm V1 Signed-off-by: Stephen Curran --- spec/core.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/spec/core.md b/spec/core.md index 97a2cb2..3a0aa39 100644 --- a/spec/core.md +++ b/spec/core.md @@ -149,6 +149,22 @@ To encode a service: } } ``` + +::: warning +Do not use the `dm` common string as the service type for DIDComm v1 `did:peer:2` DIDs. +Instead, use the full DIDComm v1 service type, `did-communication`. +::: + +> The `dm` common string is the service type for the DIDComm v2 DID service. It +should **NOT** be used for a DIDComm v1 DID service. If you are defining a +`did:peer:2` DID Doc to be used with [DIDComm v1], make sure you use a [DIDComm +v1 service], and **DO NOT** use the `dm` common string, but rather use the +proper DIDComm v1 service type of `did-communication`. There is no common string +defined for `did-communication` so it **MUST** be spelled out in full. + +[DIDComm v1]: https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0005-didcomm +[DIDComm v1 service]: https://github.com/hyperledger/aries-rfcs/blob/main/features/0067-didcomm-diddoc-conventions/README.md#service-conventions + * Convert to string, and remove unnecessary whitespace, such as spaces and newlines. For the above input, this will result in: ``` {"t":"dm","s":{"uri":"http://example.com/didcomm","a":["didcomm/v2"],"r":["did:example:123456789abcdefghi#key-1"]}}