Replace identifier registry with Verifiable data registry. Clarify …

index.html

@@ -253,11 +253,12 @@ <h3>Ecosystem Overview</h3>
 <a>verifiable credentials</a> for processing.
 Examples of verifiers include employers, security personnel, and websites.
         </dd>
-        <dt><a>identifier registry</a></dt>
+        <dt><a>Verifiable data repository</a></dt>
         <dd>
-A role a system may perform by mediating the creation and verification of
-<a>subject</a> identifiers. Examples of identifier registries include
-corporate employee databases, government ID databases, and distributed ledgers.
+Mediates the creation and verification of <a>issuer</a> identifiers, keys and
+other relevant data (schemas) required to use verifiable credentials. Examples of
+such data repositories include trusted databases, decentralised databases,
+government ID databases, and distributed ledgers.
         </dd>
       </dl>
 
@@ -579,19 +580,15 @@ <h1>Trust Model</h1>
 risk assessment of the verifier.
         </li>
         <li>
-All entities trust the <a>identifier registry</a> to be incorruptible and
-to be a correct record of which identifiers belong to which <a>entities</a>.
+All entities trust the <a>Verifiable data repository</a> to be un-corruptible and
+to be a correct record of which data is owned (and can be updated) by which
+<a>entities</a>.
         </li>
         <li>
 The <a>subject</a> trusts the <a>issuer</a> to issue true (i.e., not false)
 <a>credentials</a> about the subject, and to revoke them quickly when
 appropriate.
         </li>
-        <li>
-The <a>holder</a> trusts the <a>repository</a> to store the
-<a>credentials</a> securely, to not release them to anyone other than the
-<a>holder</a>, and to not corrupt or lose them whilst they are in its care.
-        </li>
       </ol>
 
       <p>
@@ -1556,9 +1553,9 @@ <h3> 'Subject Only' Terms of Use </h3>
       </p>
 
   <p>
-The Subject Only Terms of Use states that a verifiable credential MUST only be 
-presented to a verifier by the subject. If a verifier is presented with a 
-verifiable credential containing the Subject Only Terms of Use, by anyone other 
+The Subject Only Terms of Use states that a verifiable credential MUST only be
+presented to a verifier by the subject. If a verifier is presented with a
+verifiable credential containing the Subject Only Terms of Use, by anyone other
     than the subject, it MUST refuse to accept it.
      </p>
 
@@ -1596,7 +1593,7 @@ <h3> Passing on a Verifiable Credential </h3>
 holder, the subject SHOULD issue a new verifiable credential to the holder in which:
 the issuer is the subject,
 the subject is the holder to whom the verifiable credential is being passed,
-and the claim contains the properties that are being passed on. In addition, the 
+and the claim contains the properties that are being passed on. In addition, the
 holder creates a verifiable presentation that contains these two
 verifiable credentials.
 </p>

terms.html

@@ -42,7 +42,7 @@
   </dd>
   <dt><dfn data-lt="decentralized identifier documents|DID document|DID documents">decentralized identifier document</dfn></dt>
   <dd>
-A document that is accessible via an identifier registry and contains information
+A document that is accessible via an Verifiable data repository and contains information
 related to a particular <a>decentralized identifier</a> such as the
 associated <a>repository</a> and public key information.
   </dd>
@@ -71,7 +71,7 @@
 distribution or use of identity information can compromise privacy. Collection
 and use of such information should follow the principles of minimal disclosure.
   </dd>
-  <dt><dfn data-lt="identifier registries">identifier registry</dfn></dt>
+  <dt><dfn data-lt="verifiable data repositories">Verifiable data repository</dfn></dt>
   <dd>
 A role a system may perform by mediating the creation and verification of
 <a>subject</a> identifiers. Some registries, such as ones for UUIDs and