From b0ec22f3535594023088d080018c6733c4dd9dee Mon Sep 17 00:00:00 2001
From: jonnycrunch <jonnycrunch@me.com>
Date: Mon, 29 Oct 2018 16:37:26 -0500
Subject: [PATCH 1/2] added IPLD as JSON syntax choice

---
 index.html | 45 +++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 45 insertions(+)

diff --git a/index.html b/index.html
index 1569f9a62..e51f11b6b 100644
--- a/index.html
+++ b/index.html
@@ -2148,6 +2148,51 @@ <h2>JSON-LD</h2>
 
       </section>
 
+  <section>
+        <h2>IPLD</h2>
+        
+        <p>
+Content addressing through hashes has become a widely-used means of connecting 
+data in distributed systems. <a href="https://ipld.io">IPLD</a> is a way of representing 
+hash-linked data to be used in content-addressed data retrieval systems such as 
+<a href="https://ipfs.io">IPFS</a>. Other content that can be resolved using IPLD include 
+blockchains such as Bitcoin, Ethereum, ZCash and Git repositories. IPLD enables 
+creation of decentralized data-structures that are universally addressable facilitating 
+resolving content accross different protocols. It achieves this through an interoperable 
+data model that represents various protocol formats. IPLD relies on self-describing 
+<a href="https://github.com/ipld/cid">Content Identifiers (CIDs)]</a> for content addressing. 
+CIDs are a self-describing, flexible, and interoperable way of expressing cryptographic hashes. 
+It uses several multiformats to achieve flexible self-description, namely 
+<a href="https://github.com/multiformats/multihash"> multihash </a> for hashes, 
+<a href="https://github.com/multiformats/multicodec"> multicodec </a> for data content types, and 
+<a href="https://github.com/multiformats/multibase">multibase </a> to represent the base encoding 
+of the CID itself. This interoperability makes IPLD a valuable structure for the DID document 
+that can be used across a variety of DID methods or distributed ledgers and 
+ensures cryptographic validity of the DID document.  Since both IPLD and JSON-LD 
+are 100% compatible with JSON, the large number of JSON parsers and libraries are already available. 
+      </p>
+      <p>
+The key symbol <code>"/"</code> (foward slash) SHOULD be reserved to represent a self describing 
+content indentifier (CID) for content addressing resolved using 
+<a href="https://github.com/ipld/specs">Interplanetary Linked Data (IPLD)</a>.  
+      </p>
+
+ <p>The following example demonstrates how one could
+          express this data model using IPLD.</p>
+
+  <pre class="example" title="A verifiable claim with @context and previous linked data using IPLD">
+{ "@context" : 
+    { "/" : "zdpuAmoZixxJjvosviGeYcqduzDhSwGV2bL6ZTTXo1hbEJHfq" }, 
+    ... 
+    "previous" : 
+    { "/" : "zdpuAvqt1YTeAdcyyncBDdJLVgKyZNbHm17rBEJNqFzVbg24B" }
+    ... 
+}
+  </pre>
+
+      </section>
+
+
     </section>
 
     <section>

From a3d1090ff412677f512b07a410c57ea73457c3be Mon Sep 17 00:00:00 2001
From: jonnycrunch <jonnycrunch@me.com>
Date: Mon, 29 Oct 2018 16:49:06 -0500
Subject: [PATCH 2/2] added creator to example

---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index e51f11b6b..13db732f0 100644
--- a/index.html
+++ b/index.html
@@ -2180,11 +2180,11 @@ <h2>IPLD</h2>
  <p>The following example demonstrates how one could
           express this data model using IPLD.</p>
 
-  <pre class="example" title="A verifiable claim with @context and previous linked data using IPLD">
+  <pre class="example" title="A verifiable claim with @context and creator of the claim as linked data using IPLD">
 { "@context" : 
     { "/" : "zdpuAmoZixxJjvosviGeYcqduzDhSwGV2bL6ZTTXo1hbEJHfq" }, 
     ... 
-    "previous" : 
+    "creator" : 
     { "/" : "zdpuAvqt1YTeAdcyyncBDdJLVgKyZNbHm17rBEJNqFzVbg24B" }
     ... 
 }