Update open issues.

Author: gkellogg

index.html

@@ -12227,14 +12227,13 @@ <h3>Security Considerations</h3>
 <section class="appendix informative preserve">
   <h4>Open Issues</h4>
   <p>The following is a list of issues open at the time of publication.</p>
-  <p class="issue" data-number="4">Consider using <code>"@type": "@json"</code> to describe native values in the compact form.</p>
   <p class="issue" data-number="9">Provide a means for refering to a remote context without without requiring it to be downloaded.</p>
   <p class="issue" data-number="19">Consider a mechanism such as Microdata's <code>@itemref</code> for including objects within another referencing node.</p>
-  <p class="issue" data-number="20">Mechinism to allow freezing terms so that additional contexts don't override them.</p>
-  <p class="issue" data-number="46">Consider documentation best practices.</p>
-  <p class="issue" data-number="59">Define a recommended context to import.</p>
-  <p class="issue" data-number="76">Node Types in <code>@context</code>.</p>
-  <p class="issue" data-number="86"></p>
+  <p class="issue" data-number="86">Can SRI be used in JSON-LD and for which use cases?</p>
+  <p class="issue" data-number="108">Consider context by reference with metadata.</p>
+  <p class="issue" data-number="134">Does HTML's <code>&lt;base&gt;</code> effect <code>@context</code> IRI resolution?</p>
+  <p class="issue" data-number="149">DocumentLoader should be more visible in the specs.</p>
+  <p class="issue" data-number="155">IRIs are terms can be misdefined.</p>
 </section>
 
 <section class="appendix informative" id="changes-from-10">