From b30e004b00585ed10a6af53e5d7bc3e8d7a4bed8 Mon Sep 17 00:00:00 2001 From: Andor Kesselman Date: Fri, 6 Oct 2023 07:19:14 +0530 Subject: [PATCH 1/5] added checksum field in did document specification --- spec.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/spec.md b/spec.md index 8514a09..4e4885d 100644 --- a/spec.md +++ b/spec.md @@ -70,6 +70,7 @@ document. Adherence to the subsequent guidelines is mandatory: - `profile`: A JSON Profile document that can be resolved through HTTPS. Further requisites are detailed in the "Profile Document" section. - `definition`: If provided, this signifies the resolvable URI attribute enmeshed within the DID document. The corresponding definition is required to comply with the specifications delineated in the subsequent profile document section. + - An `checksum` MAY be added as an aid in integrity protection and verification of the Profile document. An array of structs is not valid. @@ -89,7 +90,8 @@ This following is an portion from the DID Document. "type": "TrustRegistry", "serviceEndpoint": { "profile": "https://trustoverip.org/profiles/trp/v2", - "uri": "https://my-tr-service/" + "uri": "https://my-tr-service/", + "checksum: "ec54f8019b869d5511b42678ea859b9dc185f487bf1776cb079fda0930331689", } }] } @@ -285,7 +287,6 @@ The following describes a sample profile document. } ``` - ### Future Work **Service Descriptors and Capability Declarations** We intentionally excluded a From d0e75fca48833e253188150d7f8b8f7acf19f556 Mon Sep 17 00:00:00 2001 From: Andor Kesselman Date: Fri, 6 Oct 2023 12:04:51 +0530 Subject: [PATCH 2/5] Update spec.md --- spec.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/spec.md b/spec.md index 4e4885d..fabeb34 100644 --- a/spec.md +++ b/spec.md @@ -70,7 +70,7 @@ document. Adherence to the subsequent guidelines is mandatory: - `profile`: A JSON Profile document that can be resolved through HTTPS. Further requisites are detailed in the "Profile Document" section. - `definition`: If provided, this signifies the resolvable URI attribute enmeshed within the DID document. The corresponding definition is required to comply with the specifications delineated in the subsequent profile document section. - - An `checksum` MAY be added as an aid in integrity protection and verification of the Profile document. + - An `integrity` property MAY be added as an aid in integrity protection and verification of the Profile document. It MUST be in the format of a subresource integrity field (SRI) as defined by [REC-SRI-20160623]([REC-SRI-20160623](https://www.w3.org/TR/2016/REC-SRI-20160623/). An array of structs is not valid. @@ -91,7 +91,7 @@ This following is an portion from the DID Document. "serviceEndpoint": { "profile": "https://trustoverip.org/profiles/trp/v2", "uri": "https://my-tr-service/", - "checksum: "ec54f8019b869d5511b42678ea859b9dc185f487bf1776cb079fda0930331689", + "integrity: "sha384-Li9vy3DqF8tnTXuiaAJuML3ky+er10rcgNR/VqsVpcw+ThHmYcwiB1pbOxEbzJr7", } }] } @@ -304,3 +304,4 @@ provides clarity on the profile's purpose and its role within the DID ecosystem. - DID Core: https://www.w3.org/TR/did-core/ - Referenced mainly the DID Core spec. - DIDComm Messaging: https://identity.foundation/didcomm-messaging/spec/ - used for understanding how to update the service endpoint of the DID Document. +- [Subresource Integrity](https://www.w3.org/TR/SRI/) From f158b4981f8be166c94f65d53da4981c9297b19d Mon Sep 17 00:00:00 2001 From: Andor Kesselman Date: Thu, 14 Dec 2023 07:38:00 -0800 Subject: [PATCH 3/5] Update spec.md --- spec.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec.md b/spec.md index fabeb34..a3bcde7 100644 --- a/spec.md +++ b/spec.md @@ -70,7 +70,7 @@ document. Adherence to the subsequent guidelines is mandatory: - `profile`: A JSON Profile document that can be resolved through HTTPS. Further requisites are detailed in the "Profile Document" section. - `definition`: If provided, this signifies the resolvable URI attribute enmeshed within the DID document. The corresponding definition is required to comply with the specifications delineated in the subsequent profile document section. - - An `integrity` property MAY be added as an aid in integrity protection and verification of the Profile document. It MUST be in the format of a subresource integrity field (SRI) as defined by [REC-SRI-20160623]([REC-SRI-20160623](https://www.w3.org/TR/2016/REC-SRI-20160623/). + - An `integrity` property MAY be added as an aid in integrity protection and verification of the Profile document. It MUST be in the format of a MultiHash, ``, as defined here [Multiformat]([https://multiformats.io/multihash/]). An array of structs is not valid. @@ -91,7 +91,7 @@ This following is an portion from the DID Document. "serviceEndpoint": { "profile": "https://trustoverip.org/profiles/trp/v2", "uri": "https://my-tr-service/", - "integrity: "sha384-Li9vy3DqF8tnTXuiaAJuML3ky+er10rcgNR/VqsVpcw+ThHmYcwiB1pbOxEbzJr7", + "integrity: "122041dd7b6443542e75701aa98a0c235951a28a0d851b11564d20022ab11d2589a8", } }] } From 4558f32d7fec17dd9da588b162fc5beed1ace5d8 Mon Sep 17 00:00:00 2001 From: Andor Kesselman Date: Thu, 14 Dec 2023 07:40:34 -0800 Subject: [PATCH 4/5] Update spec.md --- spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec.md b/spec.md index a3bcde7..084d0f4 100644 --- a/spec.md +++ b/spec.md @@ -70,7 +70,7 @@ document. Adherence to the subsequent guidelines is mandatory: - `profile`: A JSON Profile document that can be resolved through HTTPS. Further requisites are detailed in the "Profile Document" section. - `definition`: If provided, this signifies the resolvable URI attribute enmeshed within the DID document. The corresponding definition is required to comply with the specifications delineated in the subsequent profile document section. - - An `integrity` property MAY be added as an aid in integrity protection and verification of the Profile document. It MUST be in the format of a MultiHash, ``, as defined here [Multiformat]([https://multiformats.io/multihash/]). + - An `integrity` property MAY be added as an aid in integrity protection and verification of the Profile document. It MUST be in the format of a MultiHash, `` encoded as a varint and defined here [Multiformat](https://multiformats.io/multihash/). An array of structs is not valid. From 81c8375b59f2c47b39cc3d1fc0968dff6bbb4f96 Mon Sep 17 00:00:00 2001 From: Andor Kesselman Date: Thu, 14 Dec 2023 07:41:39 -0800 Subject: [PATCH 5/5] fixed reference to multihash --- spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec.md b/spec.md index 084d0f4..ea9eddc 100644 --- a/spec.md +++ b/spec.md @@ -304,4 +304,4 @@ provides clarity on the profile's purpose and its role within the DID ecosystem. - DID Core: https://www.w3.org/TR/did-core/ - Referenced mainly the DID Core spec. - DIDComm Messaging: https://identity.foundation/didcomm-messaging/spec/ - used for understanding how to update the service endpoint of the DID Document. -- [Subresource Integrity](https://www.w3.org/TR/SRI/) +- [MultiHash](https://multiformats.io/multihash/): Used for integrity field.