Skip to content

Commit

Permalink
Update CR2 snapshot with new publication date.
Browse files Browse the repository at this point in the history
  • Loading branch information
@msporny
msporny committed Dec 13, 2024
1 parent dd2ca81 commit 5df6cf5
Show file tree
Hide file tree
Showing 2 changed files with 74 additions and 74 deletions.
28 changes: 14 additions & 14 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand Down Expand Up @@ -278,7 +278,7 @@ <h3>Verification Methods</h3>
<h4>Multikey</h4>

<p>
The <a data-cite="controller-document#multikey">Multikey format</a>, defined in
The <a data-cite="controller-document#Multikey">Multikey format</a>, defined in
[[[controller-document]]], is used to express public keys for the cryptographic
suites defined in this specification.
</p>
Expand Down Expand Up @@ -1920,8 +1920,8 @@ <h4>Ed25519Signature2020</h4>
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
<a href="https://www.w3.org/TR/vc-data-integrity/#multibase-0">
Multibase section</a> of [[VC-DATA-INTEGRITY]].
<a data-cite="controller-document#multibase-0">
Multibase section</a> of [[CONTROLLER-DOCUMENT]].
</p>

<pre class="example nohighlight"
Expand Down Expand Up @@ -2478,7 +2478,7 @@ <h4>Proof Set</h4>
<pre class="example nohighlight" title="Starting Document for Proof Set" data-include="TestVectors/proof-set-chain/signedProofSet1.json"
data-include-format="text"></pre>
<p>
The `options` input to <a data-cite="vc-data-integrity#add-proof-set/chain">
The `options` input to <a data-cite="vc-data-integrity#add-proof-set-chain">
Section 4.4: Add Proof Set/Chain</a> 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
Expand All @@ -2487,12 +2487,12 @@ <h4>Proof Set</h4>
<pre class="example nohighlight" title="Proof Options for Set" data-include="TestVectors/proof-set-chain/proofSetConfig2.json"
data-include-format="text"></pre>
<p>
Per the algorithm of <a data-cite="vc-data-integrity#add-proof-set/chain">
Per the algorithm of <a data-cite="vc-data-integrity#add-proof-set-chain">
Section 4.4: Add Proof Set/Chain</a> 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 <a data-cite="vc-data-integrity#add-proof-set/chain">
in step 6 of <a data-cite="vc-data-integrity#add-proof-set-chain">
Section 4.4: Add Proof Set/Chain</a> in
[[VC-DATA-INTEGRITY]]. The signed proof configuration is shown below.
</p>
Expand Down Expand Up @@ -2520,20 +2520,20 @@ <h4>Proof Chain with Multiple Dependencies</h4>
<pre class="example nohighlight" title="Starting Document for Proof Chain" data-include="TestVectors/proof-set-chain/signedProofSet2.json"
data-include-format="text"></pre>
<p>
The `options` input to <a data-cite="vc-data-integrity#add-proof-set/chain">
The `options` input to <a data-cite="vc-data-integrity#add-proof-set-chain">
Section 4.4: Add Proof Set/Chain</a> in [[VC-DATA-INTEGRITY]]
is shown below. Note that it includes a `previousProof` attribute since we are
constructing a proof chain.
</p>
<pre class="example nohighlight" title="Options for Proof Chain" data-include="TestVectors/proof-set-chain/proofChainConfig1.json"
data-include-format="text"></pre>
<p>
Per the algorithm of <a data-cite="vc-data-integrity#add-proof-set/chain">
Per the algorithm of <a data-cite="vc-data-integrity#add-proof-set-chain">
Section 4.4: Add Proof Set/Chain</a> 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 <a data-cite="vc-data-integrity#add-proof-set/chain">Section 4.4: Add Proof
of <a data-cite="vc-data-integrity#add-proof-set-chain">Section 4.4: Add Proof
Set/Chain</a>, and we set the
`unsecuredDocument.proof` equal to the `matchingProofs`. This
produces the document shown below.
Expand Down Expand Up @@ -2566,20 +2566,20 @@ <h4>Extended Proof Chain</h4>
<pre class="example nohighlight" title="Starting Document for Extended Proof Chain" data-include="TestVectors/proof-set-chain/signedProofChain1.json"
data-include-format="text"></pre>
<p>
The `options` input to <a data-cite="vc-data-integrity#add-proof-set/chain">
The `options` input to <a data-cite="vc-data-integrity#add-proof-set-chain">
Section 4.4: Add Proof Set/Chain</a> 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.
</p>
<pre class="example nohighlight" title="Options for Extended Proof Chain" data-include="TestVectors/proof-set-chain/proofChainConfig2.json"
data-include-format="text"></pre>
<p>
Per the algorithm of <a data-cite="vc-data-integrity#add-proof-set/chain">
Per the algorithm of <a data-cite="vc-data-integrity#add-proof-set-chain">
Section 4.4: Add Proof Set/Chain</a> 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 <a data-cite="vc-data-integrity#add-proof-set/chain">Section 4.4: Add Proof
of <a data-cite="vc-data-integrity#add-proof-set-chain">Section 4.4: Add Proof
Set/Chain</a>, and we set the
`unsecuredDocument.proof` equal to the `matchingProofs`. This
produces the document shown below.
Expand Down
Loading

0 comments on commit 5df6cf5

Please sign in to comment.