From 40d3397efa58e3868ccf32e880e1d91217f6b248 Mon Sep 17 00:00:00 2001 From: Lionello Lunesu Date: Wed, 14 Oct 2020 11:24:29 -0700 Subject: [PATCH] fix(spec): fix broken anchors commitment-value-generation --- docs/api/content.md | 4 ++-- docs/spec/operations.md | 4 ++-- www/spec/v0.1.0/index.html | 14 +++++++------- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/api/content.md b/docs/api/content.md index 401f0e969..b8a81c82b 100644 --- a/docs/api/content.md +++ b/docs/api/content.md @@ -11,8 +11,8 @@ As detailed in [Resolution](#resolution), the resolution request MAY include the The server responds with the [DID Resolution Result](https://w3c-ccg.github.io/did-resolution/#did-resolution-result) composed of the DID Document and Method Metadata. Sidetree defines `published`, `updateCommitment`, and `recoveryCommitment` method metadata. - `published` is detailed in [Published Property](#published-property). - - `updateCommitment` is the commitement for the next update operation as defined in [commitment value generation](https://identity.foundation/sidetree/spec/#commitment-value-generation). - - `recoveryCommitment` is the commitement for the next recover or deactivate operation as defined in [commitment value generation](https://identity.foundation/sidetree/spec/#commitment-value-generation). + - `updateCommitment` is the commitement for the next update operation as defined in [commitment schemes](https://identity.foundation/sidetree/spec/#commitment-schemes). + - `recoveryCommitment` is the commitement for the next recover or deactivate operation as defined in [commitment schemes](https://identity.foundation/sidetree/spec/#commitment-schemes). ::: example ```json diff --git a/docs/spec/operations.md b/docs/spec/operations.md index 86986b827..65b3812e9 100644 --- a/docs/spec/operations.md +++ b/docs/spec/operations.md @@ -87,8 +87,8 @@ Use the following process to recover a Sidetree-based DID: 3. Create a _Recovery Commitment_ using the [Hashing Process](#hashing-process) to generate a hash value from the canonicalized [IETF RFC 7517](https://tools.ietf.org/html/rfc7517) JWK representation (using the implementation's [`JSON_CANONICALIZATION_SCHEME`](#json-canonicalization-scheme)) of the _Next Recovery Public Key_, and retain the hash value for inclusion in an [Anchor File](#anchor-file). 4. Generate a new operation key pair, which ****SHOULD NOT**** be the same key used in any previous operations, via the [`KEY_ALGORITHM`](#key-algorithm), retaining the _Next Update Public Key_ for use in generating the next _Update Commitment_, and the private key for use in the next [Update](#update) operation. 5. Create an _Update Commitment_ using the [Hashing Process](#hashing-process) to generate a hash value from the canonicalized [IETF RFC 7517](https://tools.ietf.org/html/rfc7517) JWK representation (using the implementation's [`JSON_CANONICALIZATION_SCHEME`](#json-canonicalization-scheme)) of the _Next Update Public Key_, and retain the hash value for inclusion in the [_Recovery Operation Delta Object_](#recover-delta-object)(as described below). -6. Generate and retain a [`COMMITMENT_VALUE`](#commitment-value), in adherence with the [Commitment Value Generation](#commitment-value-generation) directives, for use in the next Update operation, herein referred to as the _Update Reveal Value_. -7. Generate an _Update Commitment_ using the [Hashing Process](#hashing-process), in adherence with the [Commitment Value Generation](#commitment-value-generation) directives, to generate a hash of the _Update Reveal Value_, and retain the resulting hash value for inclusion in an [Anchor File](#anchor-file). +6. Generate and retain a [`COMMITMENT_VALUE`](#commitment-value), in adherence with the [Commitment Schemes](#commitment-schemes) directives, for use in the next Update operation, herein referred to as the _Update Reveal Value_. +7. Generate an _Update Commitment_ using the [Hashing Process](#hashing-process), in adherence with the [Commitment Schemes](#commitment-schemes) directives, to generate a hash of the _Update Reveal Value_, and retain the resulting hash value for inclusion in an [Anchor File](#anchor-file). 8. Generate a canonicalized representation of the following object using the implementation's [`JSON_CANONICALIZATION_SCHEME`](#json-canonicalization-scheme), herein referred to as the [_Recovery Operation Delta Object_](#recover-delta-object){ id="recover-delta-object" }, composed as follows: ```json { diff --git a/www/spec/v0.1.0/index.html b/www/spec/v0.1.0/index.html index 8be878c82..d7f24f5ba 100644 --- a/www/spec/v0.1.0/index.html +++ b/www/spec/v0.1.0/index.html @@ -624,7 +624,7 @@

§ Map File

"delta_hash": DELTA_HASH }, "signature": SIGNATURE_STRING - } + } }, {...} ] @@ -686,7 +686,7 @@

§ Chunk File href="#create-operation-chunk-file-entry">EXAMPLE 
{
   "deltas": [
-       
+
     { // JSON.stringify()-ed, and Base64URL encoded
       "patches": PATCH_ARRAY,
       "update_commitment": COMMITMENT_HASH
@@ -1040,10 +1040,10 @@ 
§ Recover

                     the Recovery Operation Delta Object(as described
                     below).
                 
  • Generate and retain a COMMITMENT_VALUE, in adherence
-                    with the Commitment Value Generation directives, for use
+                    with the Commitment Schemes directives, for use
                     in the next Update operation, herein referred to as the Update Reveal Value.
    • 
                 
  • Generate an Update Commitment using the Hashing Process, in
-                    adherence with the Commitment Value Generation
+                    adherence with the Commitment Schemes
                     directives, to generate a hash of the Update Reveal Value, and retain the resulting hash
                     value for inclusion in an Anchor File.
    • 
                 
  • Generate an encoded representation of the following object using the implementation’s
@@ -2389,7 +2389,7 @@ 
    § Context
    
             
    For example:
    
             
    {
     "@context": [
-        "https://www.w3.org/ns/did/v1", 
+        "https://www.w3.org/ns/did/v1",
         "https://identity.foundation/sidetree/context-v1.jsonld",
         "https://example.com/method/specific.jsonld"
     ]
@@ -2401,7 +2401,7 @@ 
    § recovery
    
             
    For Example:
    
             
    {
     "@context": [
-        "https://www.w3.org/ns/did/v1", 
+        "https://www.w3.org/ns/did/v1",
         "https://identity.foundation/sidetree/context-v1.jsonld"
     ],
     "recovery": [{
@@ -2425,7 +2425,7 @@ 
    § operation
    
             
    For Example:
    
             
    {
     "@context": [
-        "https://www.w3.org/ns/did/v1", 
+        "https://www.w3.org/ns/did/v1",
         "https://identity.foundation/sidetree/context-v1.jsonld"
     ],
     "operation": [{