Rollback changes to issue index created because of API throttling.

Author: gkellogg

publication-snapshots/FPWD/Overview.html

@@ -6461,16 +6461,16 @@ <h4 id="x9-4-2-jsonlderrorcode"><span class="secno">9.4.2 </span>JsonLdErrorCode
 <section class="appendix informative preserve" id="open-issues">
   <!--OddPage--><h2 id="c-open-issues"><span class="secno">C. </span>Open Issues&nbsp;<span class="permalink"><a href="#open-issues" aria-label="Permalink for C. Open Issues" title="Permalink for C. Open Issues"><span>§</span></a></span></h2><p><em>This section is non-normative.</em></p>
   <p>The following is a list of issues open at the time of publication.</p>
-  <div class="issue" id="issue-container-number-3"><div role="heading" class="issue-title marker" id="h-issue" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/3"><span class="issue-number">Issue 3</span></a></div><p class="">Provide a way to compact <a href="#dfn-terms" class="internalDFN" data-link-type="dfn">terms</a>, but not <a href="#dfn-value-objects" class="internalDFN" data-link-type="dfn">value objects</a> or <a href="#dfn-node-references" class="internalDFN" data-link-type="dfn">node references</a>.</p></div>
-  <div class="issue" id="issue-container-number-4"><div role="heading" class="issue-title marker" id="h-issue-0" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/4"><span class="issue-number">Issue 4</span></a></div><p class="">Allow <code>@type</code> to have a <code>@container</code> specification, such as <code>@set</code>.</p></div>
+  <div class="issue closed" id="issue-container-number-3"><div role="heading" class="issue-title marker" id="h-issue" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/3"><span class="issue-number">Issue 3</span></a><span style="text-transform: none">: Option to compact terms but not values<a class="respec-gh-label respec-label-dark" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Aenhancement%22" style="background-color: rgb(193, 21, 55);">spec:enhancement</a></span></div><p class="">Provide a way to compact <a href="#dfn-terms" class="internalDFN" data-link-type="dfn">terms</a>, but not <a href="#dfn-value-objects" class="internalDFN" data-link-type="dfn">value objects</a> or <a href="#dfn-node-references" class="internalDFN" data-link-type="dfn">node references</a>.</p></div>
+  <div class="issue" id="issue-container-number-4"><div role="heading" class="issue-title marker" id="h-issue-0" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/4"><span class="issue-number">Issue 4</span></a><span style="text-transform: none">: Relax the colliding keywords constraint for @type<a class="respec-gh-label respec-label-dark" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Aenhancement%22" style="background-color: rgb(193, 21, 55);">spec:enhancement</a></span></div><p class="">Allow <code>@type</code> to have a <code>@container</code> specification, such as <code>@set</code>.</p></div>
   <div class="issue" id="issue-container-number-5"><div role="heading" class="issue-title marker" id="h-issue-1" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/5"><span class="issue-number">Issue 5</span></a><span style="text-transform: none">: Streaming Profiles for JSON-LD to/from RDF<a class="respec-gh-label respec-label-dark" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Aenhancement%22" style="background-color: rgb(193, 21, 55);">spec:enhancement</a></span></div><p class="">Define a "streaming profile" for JSON-LD to help parse data from a stream, rather than require the entire document to be in memory. Also to generate documents that can be so streamed. This would aid in using JSON-LD as a dataset dump format where there are a very large number of quads.</p></div>
   <div class="issue closed" id="issue-container-number-6"><div role="heading" class="issue-title marker" id="h-issue-2" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/6"><span class="issue-number">Issue 6</span></a><span style="text-transform: none">: method to require {"id": "uri"} resource compaction result <a class="respec-gh-label respec-label-dark" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Aenhancement%22" style="background-color: rgb(193, 21, 55);">spec:enhancement</a></span></div><p class="">Provide a way to not compact <a href="#dfn-node-references" class="internalDFN" data-link-type="dfn">node references</a>.</p></div>
-  <div class="issue" id="issue-container-number-8"><div role="heading" class="issue-title marker" id="h-issue-3" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/8"><span class="issue-number">Issue 8</span></a></div><p class="">Remove requirement that dictionary memberes to either processed in lexographical order or generated in lexographical order.</p></div>
-  <div class="issue" id="issue-container-number-14"><div role="heading" class="issue-title marker" id="h-issue-4" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/14"><span class="issue-number">Issue 14</span></a></div><p class="">Problems importing contexts which reference other common contexts and result in an error.</p></div>
-  <div class="issue" id="issue-container-number-22"><div role="heading" class="issue-title marker" id="h-issue-5" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/22"><span class="issue-number">Issue 22</span></a></div></div>
-  <div class="issue" id="issue-container-number-25"><div role="heading" class="issue-title marker" id="h-issue-6" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/25"><span class="issue-number">Issue 25</span></a></div><p class="">Currently, the algorithms are quite proscriptive on how blank node identifiers are named, principally to make it easier to test the results, however for some things this becomes difficult or impossible, and inhibits algorithms from being conformant based on a strict textual/structural validation of the results.</p></div>
-  <div class="issue" id="issue-container-number-26"><div role="heading" class="issue-title marker" id="h-issue-7" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/26"><span class="issue-number">Issue 26</span></a></div><p class="">For <code>@graph</code> containers, use the generated graph name identifier as the default subject for nodes in that graph.</p></div>
-  <div class="issue" id="issue-container-number-27"><div role="heading" class="issue-title marker" id="h-issue-8" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/27"><span class="issue-number">Issue 27</span></a></div></div>
+  <div class="issue" id="issue-container-number-8"><div role="heading" class="issue-title marker" id="h-issue-3" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/8"><span class="issue-number">Issue 8</span></a><span style="text-transform: none">: Make ordering keys when compaction optional<a class="respec-gh-label respec-label-dark" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Aeditorial%22" style="background-color: rgb(88, 130, 10);">spec:editorial</a><a class="respec-gh-label respec-label-dark" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Aenhancement%22" style="background-color: rgb(193, 21, 55);">spec:enhancement</a></span></div><p class="">Remove requirement that dictionary memberes to either processed in lexographical order or generated in lexographical order.</p></div>
+  <div class="issue" id="issue-container-number-14"><div role="heading" class="issue-title marker" id="h-issue-4" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/14"><span class="issue-number">Issue 14</span></a><span style="text-transform: none">: Circular imports: Abort, Retry, Fail?<a class="respec-gh-label respec-label-dark" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Aenhancement%22" style="background-color: rgb(193, 21, 55);">spec:enhancement</a></span></div><p class="">Problems importing contexts which reference other common contexts and result in an error.</p></div>
+  <div class="issue" id="issue-container-number-22"><div role="heading" class="issue-title marker" id="h-issue-5" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/22"><span class="issue-number">Issue 22</span></a><span style="text-transform: none">: toRdf test output sorting</span></div><p>The toRdf n-quads test outputs used to be lexicographically sorted by line, but a handful of newer tests are not.  For instance 0100.  I don't think the spec says anything about this type of ordering?  jsonld.js is having issues with this.  Semantically it shouldn't matter, so what should test runners do to check outputs?  Just sort api result and expected result prior to a compare?  Or did we sort the older results on purpose just to make testing easier?</p></div>
+  <div class="issue" id="issue-container-number-25"><div role="heading" class="issue-title marker" id="h-issue-6" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/25"><span class="issue-number">Issue 25</span></a><span style="text-transform: none">: remove requirement on blank node naming<a class="respec-gh-label respec-label-dark" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Aenhancement%22" style="background-color: rgb(193, 21, 55);">spec:enhancement</a><a class="respec-gh-label respec-label-light" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Asubstantive%22" style="background-color: rgb(207, 249, 164);">spec:substantive</a><a class="respec-gh-label respec-label-light" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22test%3Aneeds+implementation%22" style="background-color: rgb(228, 194, 249);">test:needs implementation</a></span></div><p class="">Currently, the algorithms are quite proscriptive on how blank node identifiers are named, principally to make it easier to test the results, however for some things this becomes difficult or impossible, and inhibits algorithms from being conformant based on a strict textual/structural validation of the results.</p></div>
+  <div class="issue" id="issue-container-number-26"><div role="heading" class="issue-title marker" id="h-issue-7" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/26"><span class="issue-number">Issue 26</span></a><span style="text-transform: none">: Ensure that blank node identifiers for anonymous graphs are reused<a class="respec-gh-label respec-label-dark" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Aenhancement%22" style="background-color: rgb(193, 21, 55);">spec:enhancement</a></span></div><p class="">For <code>@graph</code> containers, use the generated graph name identifier as the default subject for nodes in that graph.</p></div>
+  <div class="issue" id="issue-container-number-27"><div role="heading" class="issue-title marker" id="h-issue-8" aria-level="3"><a href="https://github.com/w3c/json-ld-api/issues/27"><span class="issue-number">Issue 27</span></a><span style="text-transform: none">: toRdf and fromRdf algorithms need WebIDL API methods defined<a class="respec-gh-label respec-label-dark" href="https://github.com/w3c/json-ld-api/issues/?q=is%3Aissue+is%3Aopen+label%3A%22spec%3Aeditorial%22" style="background-color: rgb(88, 130, 10);">spec:editorial</a></span></div></div>
 </section>
 
 <section class="appendix informative" id="changes-since-1-0-recommendation-of-16-january-2014">