Fix broken links.

Author: msporny

index.html

@@ -226,7 +226,7 @@
             restrictRefs,
             window.respecVc.createVcExamples
           ],
-          xref: ["INFRA", "MIMESNIFF", "VC-DATA-MODEL-2.0", "CID-1.0"],
+          xref: ["INFRA", "MIMESNIFF", "VC-DATA-MODEL-2.0", "CID"],
           otherLinks: [{
             key: "Related Specifications",
             data: [{
@@ -350,7 +350,7 @@ <h2>Introduction</h2>
         </li>
         <li>
 Authenticate as an entity identified by a particular identifier, for example, as
-the subject identified by a Decentralized Identifier (DID) [[?DID-CORE]].
+the subject identified by a Decentralized Identifier (DID) [[?DID]].
         </li>
         <li>
 Delegate authorization for actions in a remote execution environment, via
@@ -622,7 +622,7 @@ <h3>Terminology</h3>
 
           <dd>
 A document that contains public cryptographic material as defined in the
-[[[CID-1.0]]] specification.
+[[[CID]]] specification.
           </dd>
 
           <dt><dfn data-lt="verifier|verifiers|verifier's">verifier</dfn></dt>
@@ -657,7 +657,7 @@ <h3>Terminology</h3>
             <p>
 An expression of the relationship between the [=subject=] and a
 [=verification method=]. An example of a verification relationship is
-<a data-cite="CID-1.0#authentication">authentication</a>.
+<a data-cite="CID#authentication">authentication</a>.
             </p>
           </dd>
 
@@ -823,8 +823,8 @@ <h3>Proofs</h3>
 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
-<a data-cite="CID-1.0#multibase-0">2.4 Multibase</a> of the
-[[[CID-1.0]]] specification to express the binary data.
+<a data-cite="CID#multibase-0">2.4 Multibase</a> of the
+[[[CID]]] specification to express the binary data.
 The contents of this value are determined by a specific cryptosuite and set
 to the <em>proof value</em> generated by the <a href="#add-proof">Add Proof Algorithm</a>
 for that cryptosuite. Alternative properties with different encodings specified by the
@@ -1157,8 +1157,8 @@ <h2>Resource Integrity</h2>
 property named <dfn class="lint-ignore">`digestMultibase`</dfn> 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
-<a data-cite="CID-1.0#multibase">Multibase</a>-encoded
-<a data-cite="CID-1.0#multihash">Multihash</a> value.
+<a data-cite="CID#multibase">Multibase</a>-encoded
+<a data-cite="CID#multihash">Multihash</a> value.
         </p>
         <p>
 JSON-LD context authors are expected to add `digestMultibase` to contexts that
@@ -1188,7 +1188,7 @@ <h2>Resource Integrity</h2>
 Implementers are urged to consult appropriate sources, such as the
 <a href="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf">
 FIPS 180-4 Secure Hash Standard</a> and the
-<a href="https://media.defense.gov/2022/Sep/07/2003071834/-1/-1/0/CSA_CNSA_2.0_ALGORITHMS_.PDF">
+<a href="https://en.wikipedia.org/wiki/Commercial_National_Security_Algorithm_Suite">
 Commercial National Security Algorithm Suite 2.0</a> to ensure that they are
 choosing a hash algorithm that is appropriate for their use case.
         </p>
@@ -1259,7 +1259,7 @@ <h2>Contexts and Vocabularies</h2>
         <p class="note">
 Beyond the security terms defined by this specification, the
 <a href="https://w3id.org/security">https://w3id.org/security#</a> namespace
-also includes the terms defined in the [[[CID-1.0]]] [[CID-1.0]]
+also includes the terms defined in the [[[CID]]] [[CID]]
 specification, with the corresponding mappings in the context files listed above.
         </p>
 
@@ -1641,11 +1641,11 @@ <h2>Relationship to Verifiable Credentials</h2>
         <p>
 Finally, implementers are also urged to understand that there is a difference
 between the revocation information associated with a [=verifiable credential=],
-and the <a data-cite="CID-1.0#dfn-revoked">revocation</a>
-and <a data-cite="CID-1.0#defn-vm-expires">expiration</a> times
+and the <a data-cite="CID#dfn-revoked">revocation</a>
+and <a data-cite="CID#defn-vm-expires">expiration</a> times
 for a [=verification method=]. The
-<a data-cite="CID-1.0#dfn-revoked">revocation</a> and
-<a data-cite="CID-1.0#defn-vm-expires">expiration</a> times for a
+<a data-cite="CID#dfn-revoked">revocation</a> and
+<a data-cite="CID#defn-vm-expires">expiration</a> 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
@@ -2877,7 +2877,7 @@ <h3>Verification Method Binding</h3>
 [=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
-<a data-cite="?CID-1.0#retrieve-verification-method">
+<a data-cite="?CID#retrieve-verification-method">
 retrieving a verification method</a>.
         </p>
       </section>
@@ -2895,8 +2895,8 @@ <h3>Verification Relationship Validation</h3>
         <p>
 The process of validating a verification relationship is outlined in
 Section
-<a data-cite="CID-1.0#retrieve-verification-method">
-3.3 Retrieve Verification Method</a> of the [[[CID-1.0]]]
+<a data-cite="CID#retrieve-verification-method">
+3.3 Retrieve Verification Method</a> of the [[[CID]]]
 specification.
         </p>
         <p>