From 6edb213f8c8d8b83e1db8380f391ddbce47d1d1b Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sat, 4 Jan 2025 12:57:13 -0500 Subject: [PATCH] Clean up internal references to point to CID specification. --- index.html | 98 +++++++++++++++--------------------------------------- 1 file changed, 26 insertions(+), 72 deletions(-) diff --git a/index.html b/index.html index b4105742..3959d6c6 100644 --- a/index.html +++ b/index.html @@ -1538,40 +1538,24 @@

Identifiers

DID Subject

The DID for a particular DID subject is expressed using the -id property in the DID document. This property +id property in the DID document. This property is defined in Section 2.1.1: Subjects of the [[[CID]]] specification and extended by this specification to include -DIDs as defined in Section [[[#did-syntax]]]. +decentralized identifiers as defined in Section [[[#did-syntax]]].

-
-
id
-
-The value of id MUST be a string that conforms to the rules in and MUST exist in the root map of the data -model for the DID document. -
-
- 
 {
   "id": "did:example:123456789abcdefghijk"
 }
-

-The id property only denotes the DID of the -DID subject when it is present in the topmost -map of the DID document. -

DID method specifications can create intermediate representations of a -DID document that do not contain the id property, +DID document that do not contain the id property, such as when a DID resolver is performing DID resolution. However, the fully resolved DID document always contains a valid -id property. +id property.

@@ -1588,29 +1572,6 @@

DID Controller

DID controller is defined by the DID method.

-
-
controller
-
-The controller property is OPTIONAL. If present, the value MUST -be a string or a set of strings that conform to the rules in . The corresponding DID document(s) SHOULD -contain verification relationships that explicitly permit the use of -certain verification methods for specific purposes. -
-
- -

-When a controller property is present in a DID -document, its value expresses one or more DIDs. Any verification -methods contained in the DID documents for those DIDs SHOULD -be accepted as authoritative, such that proofs that satisfy those -verification methods are to be considered equivalent to proofs provided -by the DID subject and represent the DID controller(s) authorized to -make updates to the DID document. -

- 
 {
@@ -1620,16 +1581,6 @@ 
DID Controller

 }
-

-Note that authorization provided by the value of controller is -separate from authentication as described in . -This is particularly important for key recovery in the case of cryptographic key -loss, where the DID subject no longer has access to their keys, or key -compromise, where the DID controller's trusted third parties need to -override malicious activity by an attacker. See for information related to threat models -and attack vectors. -

@@ -2560,15 +2511,15 @@

Method Operations