Lazy eval version

Gemfile.lock

@@ -1,6 +1,6 @@
 GIT
   remote: https://github.com/ruby-rdf/json-ld.git
-  revision: 565f89265c1fc06d2fd5b761bdbf95b905065d3a
+  revision: 94a5f041320f71ef89e4e82c73a01fd07ab4af27
   branch: develop
   specs:
     json-ld (3.0.2)
@@ -33,10 +33,10 @@ GEM
     hamster (3.0.0)
       concurrent-ruby (~> 1.0)
     htmlentities (4.3.4)
-    i18n (1.6.0)
+    i18n (1.7.0)
       concurrent-ruby (~> 1.0)
     json-canonicalization (0.1.0)
-    json-ld-preloaded (3.0.4)
+    json-ld-preloaded (3.0.5)
       json-ld (~> 3.0)
       multi_json (~> 1.12)
       rdf (~> 3.0)
@@ -73,7 +73,7 @@ GEM
       sparql (~> 3.0)
       sparql-client (~> 3.0)
     mini_portile2 (2.4.0)
-    multi_json (1.13.1)
+    multi_json (1.14.1)
     net-http-persistent (3.1.0)
       connection_pool (~> 2.2)
     nokogiri (1.10.4)
@@ -82,7 +82,7 @@ GEM
       nokogiri
     public_suffix (4.0.1)
     rack (2.0.7)
-    rake (12.3.3)
+    rake (13.0.0)
     rdf (3.0.12)
       hamster (~> 3.0)
       link_header (~> 0.0, >= 0.0.8)
@@ -134,7 +134,7 @@ GEM
     rdf-turtle (3.0.6)
       ebnf (~> 1.1)
       rdf (~> 3.0)
-    rdf-vocab (3.0.10)
+    rdf-vocab (3.0.11)
       rdf (~> 3.0, >= 3.0.11)
     rdf-xsd (3.0.1)
       rdf (~> 3.0)
@@ -160,8 +160,8 @@ GEM
       rdf (~> 3.0)
     sxp (1.0.2)
       rdf (~> 3.0)
-    temple (0.8.1)
-    tilt (2.0.9)
+    temple (0.8.2)
+    tilt (2.0.10)
 
 PLATFORMS
   ruby

common/terms.html

@@ -320,13 +320,16 @@
     when prepended to the suffix of the <a>compact IRI</a>,
     results in an <a>absolute IRI</a>.</dd>
   <dt><dfn data-cite="JSON-LD11#dfn-processing-mode">processing mode</dfn></dt><dd>
-    The processing mode defines how a <a>JSON-LD document</a> is processed.
-    By default, all documents are assumed to be conformant with <a data-cite="JSON-LD10" data-no-xref="">JSON-LD 1.0</a> [[JSON-LD10]].
+    The <a>processing mode</a> defines how a <a>JSON-LD document</a> is processed.
+    By default, all documents are assumed to be conformant with this specification.
     By defining a different version using the <code>@version</code> <a>entry</a> in a <a>context</a>,
-    or via explicit API option,
-    other processing modes can be accessed.
+    publishers can ensure that processors conformant with <a data-cite="JSON-LD10" data-no-xref="">JSON-LD 1.0</a> [[JSON-LD10]]
+    will not accidently process JSON-LD 1.1 documents, possibly creating a different output.
+    The API provides an option for setting the <a>processing mode</a> to `json-ld-1.0`,
+    which will prevent JSON-LD 1.1 features from being activated,
+    or error if <code>@version</code> <a>entry</a> in a <a>context</a> is explicitly set to `1.1`.
     This specification extends <a data-cite="JSON-LD10" data-no-xref="">JSON-LD 1.0</a>
-    via the <code>json-ld-1.1</code> <a>processing mode</a>.</dd>
+    via the `json-ld-1.1` <a>processing mode</a>.</dd>
   <dt><dfn data-cite="JSON-LD11#dfn-set-object">set object</dfn></dt><dd>
     A <a>set object</a> is a <a>map</a> that has an <code>@set</code> <a>entry</a>.
     It may also have an <code>@index</code> key, but no other <a>entries</a>.</dd>