From 4e04465ba6b8f367bba991414be99a1e0eea1f56 Mon Sep 17 00:00:00 2001
From: Ruben Verborgh <ruben@verborgh.org>
Date: Thu, 12 May 2016 09:37:16 +0200
Subject: [PATCH] Explain why JSON is not hypermedia.

Closes #32.
---
 web-apis/index.html | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/web-apis/index.html b/web-apis/index.html
index 166c2d6..535693a 100644
--- a/web-apis/index.html
+++ b/web-apis/index.html
@@ -996,6 +996,40 @@ <h2>
     </ul>
   </div>
 
+  <div class="slide" id="non-html-hypermedia">
+    <h2>
+      Other media types can also have links,<br>
+      if an interpretation is specified.
+    </h2>
+    <ul>
+      <li>
+        A regular JSON document <em>cannot</em> have hyperlinks.
+        <ul>
+          <li>
+            <code>{ "url": "http://perdu.com/" }</code> is not a link.
+          </li>
+          <li>
+            The <a href="https://tools.ietf.org/html/rfc4627"><code>application/json</code></a> media type<br>
+            does not specify an interpretation for links.
+          </li>
+        </ul>
+      </li>
+      <li class="next">
+        Specific JSON subtypes <em>can</em> have hyperlinks.
+        <ul>
+          <li>
+            The <a href="http://tools.ietf.org/html/draft-kelly-json-hal"><code>application/hal+json</code></a> media type<br>
+            specifies an <a href="https://tools.ietf.org/html/draft-kelly-json-hal-07#section-5">interpretation for links</a>.
+          </li>
+          <li class="next">
+            This interpretation is <em>only</em> allowed if the server<br>
+            replies with <code>Content-Type: application/hal+json</code>.
+          </li>
+        </ul>
+      </li>
+    </ul>
+  </div>
+
   <div class="slide" id="hypertext-definition">
     <blockquote>
       <p>