Skip to content

Commit

Permalink
Update crypto-suite names.
Browse files Browse the repository at this point in the history 
Names now conform to VC-DI specification.
  • Loading branch information
@Wind4Greg @msporny
Wind4Greg authored and msporny committed Aug 10, 2023
1 parent 4325b02 commit 6f9b3fa
Showing 1 changed file with 47 additions and 47 deletions.
94 changes: 47 additions & 47 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -396,7 +396,7 @@ <h4>DataIntegrityProof</h4>
The `type` property of the proof MUST be `DataIntegrityProof`.
</p>
<p>
The `cryptosuite` property of the proof MUST be `ecdsa-2019`.
The `cryptosuite` property of the proof MUST be `ecdsa-rdfc-2019` or `ecdsa-jcs-2019`.
</p>
<p>
The `created` property of the proof MUST be an [[XMLSCHEMA11-2]]
Expand Down Expand Up @@ -449,10 +449,10 @@ <h2>Algorithms</h2>
</p>

<section>
<h3>ecdsa-2019</h3>
<h3>ecdsa-rdfc-2019</h3>

<p>
The `ecdsa-2019` cryptographic suite takes an input document, canonicalizes
The `ecdsa-rdfc-2019` cryptographic suite takes an input document, canonicalizes
the document using the Universal RDF Dataset Canonicalization Algorithm
[[RDF-CANON]], and then cryptographically hashes and signs the output
resulting in the production of a data integrity proof. The algorithms in this
Expand All @@ -467,7 +467,7 @@ <h3>ecdsa-2019</h3>
</p>

<section>
<h4>Add Proof (ecdsa-2019)</h4>
<h4>Add Proof (ecdsa-rdfc-2019)</h4>

<p>
To generate a proof, the algorithm in
Expand All @@ -477,18 +477,18 @@ <h4>Add Proof (ecdsa-2019)</h4>
For that algorithm, the cryptographic suite specific
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-transformation-algorithm">
transformation algorithm</a> is defined in Section
<a href="#transformation-ecdsa-2019"></a>, the
<a href="#transformation-ecdsa-rdfc-2019"></a>, the
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-hashing-algorithm">
hashing algorithm</a> is defined in Section <a href="#hashing-ecdsa-2019"></a>,
hashing algorithm</a> is defined in Section <a href="#hashing-ecdsa-rdfc-2019"></a>,
and the
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-proof-serialization-algorithm">
proof serialization algorithm</a> is defined in Section
<a href="#proof-serialization-ecdsa-2019"></a>.
<a href="#proof-serialization-ecdsa-rdfc-2019"></a>.
</p>
</section>

<section>
<h4>Verify Proof (ecdsa-2019)</h4>
<h4>Verify Proof (ecdsa-rdfc-2019)</h4>

<p>
To verify a proof, the algorithm in
Expand All @@ -498,23 +498,23 @@ <h4>Verify Proof (ecdsa-2019)</h4>
For that algorithm, the cryptographic suite specific
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-transformation-algorithm">
transformation algorithm</a> is defined in Section
<a href="#transformation-ecdsa-2019"></a>, the
<a href="#transformation-ecdsa-rdfc-2019"></a>, the
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-hashing-algorithm">
hashing algorithm</a> is defined in Section <a href="#hashing-ecdsa-2019"></a>,
hashing algorithm</a> is defined in Section <a href="#hashing-ecdsa-rdfc-2019"></a>,
and the
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-proof-serialization-algorithm">
proof verification algorithm</a> is defined in Section
<a href="#proof-verification-ecdsa-2019"></a>.
<a href="#proof-verification-ecdsa-rdfc-2019"></a>.
</p>
</section>

<section>
<h4>Transformation (ecdsa-2019)</h4>
<h4>Transformation (ecdsa-rdfc-2019)</h4>

<p>
The following algorithm specifies how to transform an unsecured input document
into a transformed document that is ready to be provided as input to the
hashing algorithm in Section <a href="#hashing-ecdsa-2019"></a>.
hashing algorithm in Section <a href="#hashing-ecdsa-rdfc-2019"></a>.
</p>

<p>
Expand All @@ -534,7 +534,7 @@ <h4>Transformation (ecdsa-2019)</h4>
<li>
If <var>options</var>.<var>type</var> is not set to the string
`DataIntegrityProof` and <var>options</var>.<var>cryptosuite</var> is not
set to the string `ecdsa-2019` then a `PROOF_TRANSFORMATION_ERROR` MUST be
set to the string `ecdsa-rdfc-2019` then a `PROOF_TRANSFORMATION_ERROR` MUST be
raised.
</li>
<li>
Expand All @@ -552,14 +552,14 @@ <h4>Transformation (ecdsa-2019)</h4>
</section>

<section>
<h4>Hashing (ecdsa-2019)</h4>
<h4>Hashing (ecdsa-rdfc-2019)</h4>

<p>
The following algorithm specifies how to cryptographically hash a
<em>transformed data document</em> and <em>proof configuration</em>
into cryptographic hash data that is ready to be provided as input to the
algorithms in Section <a href="#proof-serialization-ecdsa-2019"></a> or
Section <a href="#proof-verification-ecdsa-2019"></a>. One must use the hash
algorithms in Section <a href="#proof-serialization-ecdsa-rdfc-2019"></a> or
Section <a href="#proof-verification-ecdsa-rdfc-2019"></a>. One must use the hash
algorithm appropriate in security level to the curve used, i.e., for curve
P-256 one uses SHA-256 and for curve P-384 one uses SHA-384.
</p>
Expand Down Expand Up @@ -599,12 +599,12 @@ <h4>Hashing (ecdsa-2019)</h4>
</section>

<section>
<h4>Proof Configuration (ecdsa-2019)</h4>
<h4>Proof Configuration (ecdsa-rdfc-2019)</h4>

<p>
The following algorithm specifies how to generate a
<em>proof configuration</em> from a set of <em>proof options</em>
that is used as input to the <a href="#hashing-ecdsa-2019">proof hashing algorithm</a>.
that is used as input to the <a href="#hashing-ecdsa-rdfc-2019">proof hashing algorithm</a>.
</p>

<p>
Expand All @@ -631,7 +631,7 @@ <h4>Proof Configuration (ecdsa-2019)</h4>
</li>
<li>
If <var>options</var>.<var>type</var> is not set to `DataIntegrityProof` and
<var>proofConfig</var>.<var>cryptosuite</var> is not set to `ecdsa-2019`, an
<var>proofConfig</var>.<var>cryptosuite</var> is not set to `ecdsa-rdfc-2019`, an
`INVALID_PROOF_CONFIGURATION` error MUST be raised.
</li>
<li>
Expand Down Expand Up @@ -664,7 +664,7 @@ <h4>Proof Configuration (ecdsa-2019)</h4>
</section>

<section>
<h4>Proof Serialization (ecdsa-2019)</h4>
<h4>Proof Serialization (ecdsa-rdfc-2019)</h4>

<p>
The following algorithm specifies how to serialize a digital signature from
Expand Down Expand Up @@ -706,7 +706,7 @@ <h4>Proof Serialization (ecdsa-2019)</h4>
</section>

<section>
<h4>Proof Verification (ecdsa-2019)</h4>
<h4>Proof Verification (ecdsa-rdfc-2019)</h4>

<p>
The following algorithm specifies how to verify a digital signature from
Expand Down Expand Up @@ -745,18 +745,18 @@ <h4>Proof Verification (ecdsa-2019)</h4>
</section>
</section>
<section>
<h3>jcs-ecdsa-2019</h3>
<h3>ecdsa-jcs-2019</h3>

<p>
The `jcs-ecdsa-2019` cryptographic suite takes an input document, canonicalizes
The `ecdsa-jcs-2019` cryptographic suite takes an input document, canonicalizes
the document using the JSON Canonicalization Scheme [[RFC8785]], and then
cryptographically hashes and signs the output
resulting in the production of a data integrity proof. The algorithms in this
section also include the verification of such a data integrity proof.
</p>

<section>
<h4>Add Proof (jcs-ecdsa-2019)</h4>
<h4>Add Proof (ecdsa-jcs-2019)</h4>

<p>
To generate a proof, the algorithm in
Expand All @@ -766,18 +766,18 @@ <h4>Add Proof (jcs-ecdsa-2019)</h4>
For that algorithm, the cryptographic suite-specific
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-transformation-algorithm">
transformation algorithm</a> is defined in Section
<a href="#transformation-jcs-ecdsa-2019"></a>, the
<a href="#transformation-ecdsa-jcs-2019"></a>, the
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-hashing-algorithm">
hashing algorithm</a> is defined in Section <a href="#hashing-jcs-ecdsa-2019"></a>,
hashing algorithm</a> is defined in Section <a href="#hashing-ecdsa-jcs-2019"></a>,
and the
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-proof-serialization-algorithm">
proof serialization algorithm</a> is defined in Section
<a href="#proof-serialization-jcs-ecdsa-2019"></a>.
<a href="#proof-serialization-ecdsa-jcs-2019"></a>.
</p>
</section>

<section>
<h4>Verify Proof (jcs-ecdsa-2019)</h4>
<h4>Verify Proof (ecdsa-jcs-2019)</h4>

<p>
To verify a proof, the algorithm in
Expand All @@ -787,23 +787,23 @@ <h4>Verify Proof (jcs-ecdsa-2019)</h4>
For that algorithm, the cryptographic suite-specific
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-transformation-algorithm">
transformation algorithm</a> is defined in Section
<a href="#transformation-jcs-ecdsa-2019"></a>, the
<a href="#transformation-ecdsa-jcs-2019"></a>, the
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-hashing-algorithm">
hashing algorithm</a> is defined in Section <a href="#hashing-jcs-ecdsa-2019"></a>,
hashing algorithm</a> is defined in Section <a href="#hashing-ecdsa-jcs-2019"></a>,
and the
<a href="https://www.w3.org/TR/vc-data-integrity/#dfn-proof-serialization-algorithm">
proof verification algorithm</a> is defined in Section
<a href="#proof-verification-jcs-ecdsa-2019"></a>.
<a href="#proof-verification-ecdsa-jcs-2019"></a>.
</p>
</section>

<section>
<h4>Transformation (jcs-ecdsa-2019)</h4>
<h4>Transformation (ecdsa-jcs-2019)</h4>

<p>
The following algorithm specifies how to transform an unsecured input document
into a transformed document that is ready to be provided as input to the
hashing algorithm in Section <a href="#hashing-jcs-ecdsa-2019"></a>.
hashing algorithm in Section <a href="#hashing-ecdsa-jcs-2019"></a>.
</p>

<p>
Expand All @@ -823,7 +823,7 @@ <h4>Transformation (jcs-ecdsa-2019)</h4>
<li>
If <var>options</var>.<var>type</var> is not set to the string
`DataIntegrityProof` and <var>options</var>.<var>cryptosuite</var> is not
set to the string `jcs-ecdsa-2019`, then a `PROOF_TRANSFORMATION_ERROR` MUST be
set to the string `ecdsa-jcs-2019`, then a `PROOF_TRANSFORMATION_ERROR` MUST be
raised.
</li>
<li>
Expand All @@ -840,14 +840,14 @@ <h4>Transformation (jcs-ecdsa-2019)</h4>
</section>

<section>
<h4>Hashing (jcs-ecdsa-2019)</h4>
<h4>Hashing (ecdsa-jcs-2019)</h4>

<p>
The following algorithm specifies how to cryptographically hash a
<em>transformed data document</em> and <em>proof configuration</em>
into cryptographic hash data that is ready to be provided as input to the
algorithms in Section <a href="#proof-serialization-jcs-ecdsa-2019"></a> or
Section <a href="#proof-verification-jcs-ecdsa-2019"></a>. One must use the
algorithms in Section <a href="#proof-serialization-ecdsa-jcs-2019"></a> or
Section <a href="#proof-verification-ecdsa-jcs-2019"></a>. One must use the
hash algorithm appropriate in security level to the curve used, i.e., for curve
P-256 one uses SHA-256, and for curve P-384 one uses SHA-384.
</p>
Expand Down Expand Up @@ -887,12 +887,12 @@ <h4>Hashing (jcs-ecdsa-2019)</h4>
</section>

<section>
<h4>Proof Configuration (jcs-ecdsa-2019)</h4>
<h4>Proof Configuration (ecdsa-jcs-2019)</h4>

<p>
The following algorithm specifies how to generate a
<em>proof configuration</em> from a set of <em>proof options</em>
that is used as input to the <a href="#hashing-jcs-ecdsa-2019">proof hashing algorithm</a>.
that is used as input to the <a href="#hashing-ecdsa-jcs-2019">proof hashing algorithm</a>.
</p>

<p>
Expand All @@ -919,7 +919,7 @@ <h4>Proof Configuration (jcs-ecdsa-2019)</h4>
</li>
<li>
If <var>options</var>.<var>type</var> is not set to `DataIntegrityProof` and
<var>proofConfig</var>.<var>cryptosuite</var> is not set to `jcs-ecdsa-2019`, an
<var>proofConfig</var>.<var>cryptosuite</var> is not set to `ecdsa-jcs-2019`, an
`INVALID_PROOF_CONFIGURATION` error MUST be raised.
</li>
<li>
Expand Down Expand Up @@ -947,7 +947,7 @@ <h4>Proof Configuration (jcs-ecdsa-2019)</h4>
</section>

<section>
<h4>Proof Serialization (jcs-ecdsa-2019)</h4>
<h4>Proof Serialization (ecdsa-jcs-2019)</h4>

<p>
The following algorithm specifies how to serialize a digital signature from
Expand Down Expand Up @@ -989,7 +989,7 @@ <h4>Proof Serialization (jcs-ecdsa-2019)</h4>
</section>

<section>
<h4>Proof Verification (jcs-ecdsa-2019)</h4>
<h4>Proof Verification (ecdsa-jcs-2019)</h4>

<p>
The following algorithm specifies how to verify a digital signature from
Expand Down Expand Up @@ -2674,7 +2674,7 @@ <h2>Test Vectors</h2>
The group is debating the names used for the cryptosuite identifiers in <a href="https://github.com/w3c/vc-data-integrity/issues/38">VC Data Integrity issue #38</a>. Cryptosuite identifiers might change in the future.
</p>
<section>
<h3>Representation: ecdsa-2019, with curve P-256</h3>
<h3>Representation: ecdsa-rdfc-2019, with curve P-256</h3>
<p>
The signer needs to generate a private/public key pair with the private key used
for signing and the public key made available for verification. The
Expand Down Expand Up @@ -2745,7 +2745,7 @@ <h3>Representation: ecdsa-2019, with curve P-256</h3>
data-include="TestVectors/ecdsa-2019-p256/signedECDSAP256.json" data-include-format="text"></pre>
</section>
<section>
<h3>Representation: ecdsa-2019, with curve P-384</h3>
<h3>Representation: ecdsa-rdfc-2019, with curve P-384</h3>
<p>
The signer needs to generate a private/public key pair with the private key used
for signing and the public key made available for verification. The
Expand Down Expand Up @@ -2816,7 +2816,7 @@ <h3>Representation: ecdsa-2019, with curve P-384</h3>
data-include="TestVectors/ecdsa-2019-p384/signedECDSAP384.json" data-include-format="text"></pre>
</section>
<section>
<h3>Representation: jcs-ecdsa-2019 with curve P-256</h3>
<h3>Representation: ecdsa-jcs-2019 with curve P-256</h3>
<p>
The signer needs to generate a private/public key pair with the private key used
for signing and the public key made available for verification. The
Expand Down Expand Up @@ -2887,7 +2887,7 @@ <h3>Representation: jcs-ecdsa-2019 with curve P-256</h3>
data-include="TestVectors/jcs-ecdsa-2019-p256/signedJCSECDSAP256.json" data-include-format="text"></pre>
</section>
<section>
<h3>Representation: jcs-ecdsa-2019 with curve P-384</h3>
<h3>Representation: ecdsa-jcs-2019 with curve P-384</h3>
<p>
The signer needs to generate a private/public key pair with the private key used
for signing and the public key made available for verification. The
Expand Down

0 comments on commit 6f9b3fa

Please sign in to comment.