Remove design goal "One-pass Processing"
authorMarkus Lanthaler <>
Mon, 21 Jan 2013 18:44:49 +0100
changeset 1144 7b643e13e52a
parent 1143 1ebebaca9248
child 1145 137686e06d32
Remove design goal "One-pass Processing"

I think it confuses more than it helps. Most algorithms wouldn't work if, e.g., an object has been received just partially.
--- a/spec/latest/json-ld-syntax/index.html	Mon Jan 21 18:19:00 2013 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Mon Jan 21 18:44:49 2013 +0100
@@ -258,11 +258,6 @@
      esoteric use case, we chose not to support the use case. While Zero Edits is
      a design goal, it is not always possible without adding great complexity
      to the language. We should focus on simplicity when possible.</dd>
-   <dt>One-pass Processing</dt>
-   <dd>JSON-LD supports one-pass processing, which results in a very small memory
-     footprint when processing documents. For example, to expand a JSON-LD document
-     from a compacted form, only one pass is required over the data. This mechanism
-     should make some forms of JSON-LD very useful when used in streaming protocols.</dd>
@@ -683,11 +678,8 @@
-    <p class="note">To ensure the best possible performance, it is a best practice to
-      put the <tref>context</tref> definition at the top of the JSON-LD document. If it isn't listed
-      first, processors have to save each key-value pair until the <tref>context</tref> is processed.
-      This creates a memory and complexity burden for certain types of
-      low-memory footprint JSON-LD processors.</p>
+    <p class="note">It is a best practice to put the <tref>context</tref> definition
+      at the top of the JSON-LD document.</p>
       <h2>Referencing Contexts from JSON Documents</h2>