diff --git a/index.html b/index.html index 1440762..2c110c9 100644 --- a/index.html +++ b/index.html @@ -22,7 +22,8 @@ group: "vc", // if you wish the publication date to be other than today, set this - publishDate: "2024-11-05", + publishDate: "2024-12-19", + crEnd: "2024-01-19", // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date // and its maturity status @@ -35,7 +36,6 @@ // if this is a LCWD, uncomment and set the end of its review period implementationReportURI: "https://w3c.github.io/vc-di-eddsa-test-suite/", - crEnd: "2024-12-05", // if you want to have extra CSS, append them to this list // it is recommended that the respec.css stylesheet be kept @@ -278,7 +278,7 @@

Verification Methods

Multikey

-The Multikey format, defined in +The Multikey format, defined in [[[controller-document]]], is used to express public keys for the cryptographic suites defined in this specification.

@@ -1920,8 +1920,8 @@

Ed25519Signature2020

The `proofValue` property of the proof MUST be a detached EdDSA produced according to [[RFC8032]], encoded using the base-58-btc header and alphabet as described in the - -Multibase section of [[VC-DATA-INTEGRITY]]. + +Multibase section of [[CONTROLLER-DOCUMENT]].

Proof Set
           

           

-The `options` input to +The `options` input to Section 4.4: Add Proof Set/Chain in [[VC-DATA-INTEGRITY]] is shown below. Note that it does not include a `previousProof` attribute since we are constructing a proof set and not a chain. In addition, we will be using @@ -2487,12 +2487,12 @@

Proof Set


           

-Per the algorithm of +Per the algorithm of Section 4.4: Add Proof Set/Chain in [[VC-DATA-INTEGRITY]], we create an array variable, `allProofs`, and add the proof from the starting document to it. Since there is no `previousProof` attribute, no modification of `unsignedDocument` is needed prior to computing the signed proof -in step 6 of +in step 6 of Section 4.4: Add Proof Set/Chain in [[VC-DATA-INTEGRITY]]. The signed proof configuration is shown below.

@@ -2520,7 +2520,7 @@

Proof Chain with Multiple Dependencies


           

-The `options` input to +The `options` input to Section 4.4: Add Proof Set/Chain in [[VC-DATA-INTEGRITY]] is shown below. Note that it includes a `previousProof` attribute since we are constructing a proof chain. @@ -2528,12 +2528,12 @@

Proof Chain with Multiple Dependencies


           

-Per the algorithm of +Per the algorithm of Section 4.4: Add Proof Set/Chain in [[VC-DATA-INTEGRITY]], we create an array variable, `allProofs`, and add the proofs from the starting document to it. Since the options contains the `previousProof` attribute, we compute the `matchingProofs` variable per step 4 -of Section 4.4: Add Proof +of Section 4.4: Add Proof Set/Chain, and we set the `unsecuredDocument.proof` equal to the `matchingProofs`. This produces the document shown below. @@ -2566,7 +2566,7 @@

Extended Proof Chain


           

-The `options` input to +The `options` input to Section 4.4: Add Proof Set/Chain in [[VC-DATA-INTEGRITY]] is shown below. Note that it includes a `previousProof` attribute since we are constructing a proof chain, however this time it is a single value. @@ -2574,12 +2574,12 @@

Extended Proof Chain


           

-Per the algorithm of +Per the algorithm of Section 4.4: Add Proof Set/Chain in [[VC-DATA-INTEGRITY]], we create an array variable, `allProofs`, and add the proofs from the starting document to it. Since the `options` contains the `previousProof` attribute, we compute the `matchingProofs` variable per step 4 -of Section 4.4: Add Proof +of Section 4.4: Add Proof Set/Chain, and we set the `unsecuredDocument.proof` equal to the `matchingProofs`. This produces the document shown below. diff --git a/transitions/2024/CR2/index.html b/transitions/2024/CR2/index.html index b18961c..fea9ec5 100644 --- a/transitions/2024/CR2/index.html +++ b/transitions/2024/CR2/index.html @@ -1,6 +1,6 @@ - +