From d9f0f225c2a15714e6510766d60eaf8483a1bbce Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sat, 27 Jul 2024 18:15:55 -0400 Subject: [PATCH] Remove unused terminology. Tighten up loose terminology. --- index.html | 68 +++++++++++++++--------------------------------------- 1 file changed, 18 insertions(+), 50 deletions(-) diff --git a/index.html b/index.html index 699d6a2..c336736 100644 --- a/index.html +++ b/index.html @@ -216,7 +216,7 @@ restrictRefs, window.respecVc.createVcExamples ], - xref: ["INFRA", "MIMESNIFF", "VC-DATA-MODEL-2.0"], + xref: ["INFRA", "MIMESNIFF", "VC-DATA-MODEL-2.0", "CONTROLLER-DOCUMENT"], otherLinks: [{ key: "Related Specifications", data: [{ @@ -573,16 +573,19 @@

Terminology

data integrity proof
A set of attributes that represent a digital proof and the parameters required -to verify it. +to verify it. A digital signature is a type of data integrity +proof.
public key
Cryptographic material that can be used to verify digital proofs created with a -corresponding [=private key=]. +corresponding [=secret key=].
-
private key
+
secret key
-Cryptographic material that can be used to generate digital proofs. +Cryptographic material, sometimes referred to as a +private key, that is not to be shared with anyone, and is used +to generate digital proofs and/or digital signatures.
proof type
@@ -597,26 +600,6 @@

Terminology

protected declaration acts as a safeguard to prevent the proof from being misused for a purpose other than the one it was intended for.
-
challenge
-
-A random or pseudo-random value used by some authentication protocols to -mitigate replay attacks. -
-
domain
-
-A string value that specifies the operational domain of a digital proof. -This could be an Internet domain name like example.com, an -ad-hoc value such as mycorp-level3-access, or a very -specific transaction value like 8zF6T8J34qP3mqP. A signer could -include a [=domain=] in its digital proof to restrict its use -to particular target, identified by the specified [=domain=]. -
- -
authentication
-
-A process by which an entity can prove to a verifier that it has a specific -attribute or controls a specific secret. -
cryptographic suite
@@ -627,33 +610,18 @@

Terminology

[[[#cryptographic-suites]]] for further detail.
-
controller
- -
-An entity that has the capability to make changes to a -[=controller document=]. -
- -
controller document
- -
-A set of data that specifies one or more relationships between a -[=controller=] and a set of data, such as a set of public cryptographic keys. -
- -
subject
+
controller document
-The entity identified by the `id` property in a [=controller document=]. -Anything can be a subject: person, group, organization, physical thing, digital -thing, logical thing, etc. +A document that contains public cryptographic material as defined in the +[[[CONTROLLER-DOCUMENT]]] specification.
verifier
A role an entity performs by receiving data containing one or more [=data integrity proofs=] and then determining whether or not the proof -is valid. +is legitimate.
verification method
@@ -661,9 +629,9 @@

Terminology

A set of parameters that can be used together with a process to independently -verify a proof. For example, a cryptographic public key can be used as a +verify a proof. For example, a cryptographic [=public key=] can be used as a verification method with respect to a digital signature; in such usage, it -verifies that the signer possessed the associated cryptographic private key. +verifies that the signer possessed the associated cryptographic [=secret key=].

"Verification" and "proof" in this definition are intended to apply broadly. For @@ -832,7 +800,7 @@

Proofs

`b31d37d4-dd59-47d3-9dd8-c973da43b63a` (UUID).
-
challenge
+
challenge
A string value that SHOULD be included in a proof if a `domain` is specified. The value is used once for a particular [=domain=] and window of time. This @@ -964,7 +932,7 @@

Proofs

the merkle paths for each N-Quad that is to be revealed. This mechanism would merely consume the normalized output differently (this, and the proof mechanism would be modifications to this core spec). It might also -be necessary to generate proof parameters such as a private key/seed +be necessary to generate proof parameters such as a [=secret key=]/seed that can be used along with an algorithm to deterministically generate nonces that are concatenated with each N-Quad to prevent rainbow table or similar attacks. @@ -1125,7 +1093,7 @@

Proof Purposes

-
authentication
+
authentication
Indicates that a given proof is only to be used for the purposes of an authentication protocol. @@ -1709,7 +1677,7 @@

Relationship to Verifiable Credentials

revocation and expiration times for a [=verification method=] are expressed using the `revocation` and `expires` -properties, respectively; are related to events such as a private key being +properties, respectively; are related to events such as a [=secret key=] being compromised or expiring; and can provide timing information which might reveal details about a controller, such as their security practices or when they might have been compromised. The revocation information for a [=verifiable