From 35ae54b9ec969a13c334d9fde85ea536eaf27708 Mon Sep 17 00:00:00 2001 From: Ivan Herman Date: Tue, 4 Feb 2025 16:33:40 +0100 Subject: [PATCH] General change from controller-document to cid-1.0 --- index.html | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/index.html b/index.html index dea00c1..beac9ea 100644 --- a/index.html +++ b/index.html @@ -226,7 +226,7 @@ restrictRefs, window.respecVc.createVcExamples ], - xref: ["INFRA", "MIMESNIFF", "VC-DATA-MODEL-2.0", "CONTROLLER-DOCUMENT"], + xref: ["INFRA", "MIMESNIFF", "VC-DATA-MODEL-2.0", "CID-1.0"], otherLinks: [{ key: "Related Specifications", data: [{ @@ -618,11 +618,11 @@

Terminology

[[[#cryptographic-suites]]] for further detail. -
controller document
+
controlled identifier document
A document that contains public cryptographic material as defined in the -[[[CONTROLLER-DOCUMENT]]] specification. +[[[CID-1.0]]] specification.
verifier
@@ -657,7 +657,7 @@

Terminology

An expression of the relationship between the [=subject=] and a [=verification method=]. An example of a verification relationship is -authentication. +authentication.

@@ -763,7 +763,7 @@

Proofs

expressed in a [=data integrity proof=], the value points to the actual location of the data; that is, the `verificationMethod` references, via a URL, the location of the [=public key=] that can be used to verify the proof. This -[=public key=] data is stored in a [=controller document=], which contains a +[=public key=] data is stored in a [=controlled identifier document=], which contains a full description of the verification method. @@ -823,8 +823,8 @@

Proofs

A [=string=] value that expresses base-encoded binary data necessary to verify the digital proof using the `verificationMethod` specified. The value MUST use a header and encoding as described in Section -2.4 Multibase of the -[[[CONTROLLER-DOCUMENT]]] specification to express the binary data. +2.4 Multibase of the +[[[CID-1.0]]] specification to express the binary data. The contents of this value are determined by a specific cryptosuite and set to the proof value generated by the Add Proof Algorithm for that cryptosuite. Alternative properties with different encodings specified by the @@ -1157,8 +1157,8 @@

Resource Integrity

property named `digestMultibase` in any object that includes an `id` property. If present, the `digestMultibase` value MUST be a single [=string=] value, or an [=list=] of [=string=] values, each of which is a -Multibase-encoded -Multihash value. +Multibase-encoded +Multihash value.

JSON-LD context authors are expected to add `digestMultibase` to contexts that @@ -1259,7 +1259,7 @@

Contexts and Vocabularies

Beyond the security terms defined by this specification, the https://w3id.org/security# namespace -also includes the terms defined in the [[[CONTROLLER-DOCUMENT]]] [[CONTROLLER-DOCUMENT]] +also includes the terms defined in the [[[CID-1.0]]] [[CID-1.0]] specification, with the corresponding mappings in the context files listed above.

@@ -1641,11 +1641,11 @@

Relationship to Verifiable Credentials

Finally, implementers are also urged to understand that there is a difference between the revocation information associated with a [=verifiable credential=], -and the revocation -and expiration times +and the revocation +and expiration times for a [=verification method=]. The -revocation and -expiration times for a +revocation and +expiration times for a [=verification method=] are expressed using the `revocation` and `expires` properties, respectively; are related to events such as a [=secret key=] being compromised or expiring; and can provide timing information which might reveal @@ -2874,10 +2874,10 @@

Verification Method Binding

Implementers ensure that a [=verification method=] is bound to a particular controller by going from the definition of the [=verification method=] to the -[=controller document=], and then ensuring that the [=controller document=] also +[=controlled identifier document=], and then ensuring that the [=controlled identifier document=] also contains a reference to the [=verification method=]. This process is described in the algorithm for - + retrieving a verification method.

@@ -2888,15 +2888,15 @@

Verification Relationship Validation

When an implementation is verifying a proof, it is imperative that it verify not only that the [=verification method=] used to -generate the proof is listed in the [=controller document=], but also that it +generate the proof is listed in the [=controlled identifier document=], but also that it was intended to be used to generate the proof that is being verified. This process is known as "verification relationship validation".

The process of validating a verification relationship is outlined in Section - -3.3 Retrieve Verification Method of the [[[CONTROLLER-DOCUMENT]]] + +3.3 Retrieve Verification Method of the [[[CID-1.0]]] specification.

@@ -3507,7 +3507,7 @@

Revision History

Various editorial changes in algorithms and descriptions to improve readability.
  • -Moved Multikey definitions to Controller Document. +Moved Multikey definitions to controlled identifier document.
  • Unify error handling between all Data Integrity cryptosuites.