Valid vs verify

index.html

@@ -1486,7 +1486,7 @@ <h2>Data Schemas</h2>
         <p>
 Data schemas are often useful when enforcing a particular structure on a given
 collection of data. There are at least two types of data schemas that this
-specification contemplates. The first are data validation schemas, which are
+specification contemplates. The first are data verification schemas, which are
 used to verify that the structure and contents of a
 <a>verifiable credential</a> are conformant to a published schema. The second
 are data encoding schemas, which are used to map the contents of a
@@ -2854,7 +2854,7 @@ <h2>Verification</h2>
 
         <p class="issue" data-number=128>
 The group is currently discussing whether a mechanism should be provided
-that enables linkages to JSON Schema or other optional validation mechanisms.
+that enables linkages to JSON Schema or other optional verification mechanisms.
         </p>
 
       <section>
@@ -2967,7 +2967,7 @@ <h3>Proofs (Signatures)</h3>
 The key MUST NOT be revoked or expired.
             </li>
             <li>
-The cryptographic signature MUST be valid.
+The cryptographic signature MUST verify.
             </li>
             <li>
 If the cryptographic suite expects a <code>proofPurpose</code>, it MUST exist
@@ -2980,7 +2980,7 @@ <h3>Proofs (Signatures)</h3>
 The digital signature provides a number of protections, other than tamper
 resistance, that are not immediately obvious. For example, a Linked Data
 Signature <code>created</code> property establishes a date and time before
-which the <a>credential</a> SHOULD NOT be considered valid. The
+which the <a>credential</a> SHOULD NOT be considered verified. The
 <code>creator</code> property enables the ability to dynamically discover
 information about the <a>entity</a> who created the data to ensure that the
 public key is not revoked or expired. The <code>proofPurpose</code> property

terms.html

@@ -136,8 +136,19 @@
   </dd>
   <dt><dfn data-lt="verification|verified">verification</dfn></dt>
   <dd>
-The process of cryptographically demonstrating the authenticity of a
-<a>verifiable credential</a> or <a>verifiable presentation</a>.
+The evaluation of whether or not a <a>verifiable credential</a> or
+<a>verifiable presentation</a> complies with this specification.
+  </dd>
+  <dt><dfn data-lt="validation|valid">validation</dfn></dt>
+  <dd>
+The assurance that a <a>verifiable credential</a> system meets
+the needs of the customer and other identified stakeholders.
+  </dd>
+  <dd class="note">
+This recommendation is constrained to verifying <a>verifiable credentials</a> and
+<a>verifiable presentations</a> regardless of their usage. Validating <a>verifiable
+credentials</a> or <a>verifiable presentations</a> is out of the scope if this
+recommendation.
   </dd>
   <dt><dfn data-lt="verifier|verifiers|verifier's|credential verifiers|credential verifier's">verifier</dfn></dt>
   <dd>