diff --git a/common.js b/common.js
index 6d34670..80f3803 100644
--- a/common.js
+++ b/common.js
@@ -24,6 +24,16 @@ var ccg = {
       status: "CG-DRAFT",
       publisher: "Digital Verification Community Group"
     },
+    "DATA-INTEGRITY": {
+      title: "Verifiable Credential Data Integrity 1.0",
+      href: "https://www.w3.org/TR/vc-data-integrity/",
+      authors: [
+        "Dave Longley",
+        "Manu Sporny"
+      ],
+      status: "CRD",
+      publisher: "W3C Verifiable Credentials Working Group"
+    },
     "MATRIX-URIS": {
       title: "Matrix URIs - Ideas about Web Architecture",
       date: "December 1996",
diff --git a/index.html b/index.html
index 1eb181d..7108a86 100644
--- a/index.html
+++ b/index.html
@@ -1434,7 +1434,7 @@ <h2>Resolver Architectures</h2>
 			<p>Also describe mitigations against potential downsides of <a>remote bindings</a>, e.g.:</p>
 			<ul>
 				<li>A <a>DID resolver's</a> <a>remote binding</a> can use a trusted channel such as VPN or TLS with mutual authentication.</li>
-				<li>A <a>DID resolver</a> can add a <a href="https://www.w3.org/TR/vc-data-integrity/">data integrity proof</a>
+				<li>A <a>DID resolver</a> can add a data integrity proof (see [[DATA-INTEGRITY]])
 				to a <a>DID document</a> and/or the <a>DID resolution result</a>. Discuss what this does and doesn't achieve. Also see
 				<a href="https://www.w3.org/TR/did-core/#proving-control-and-binding">Proving Control and Binding</a>.</li>
 				<li>A client could query multiple <a>DID resolvers</a> over a <a>remote binding</a> and compare results.</li>