diff --git a/Gemfile.lock b/Gemfile.lock
index 37866348..144f32cd 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,9 +1,10 @@
 GIT
   remote: https://github.com/ruby-rdf/json-ld.git
-  revision: 74095b73cdb722b681f34d0f165599c9cb48d844
+  revision: 031d3e7b958d39f7ecd001aa3f617bb8c2e65d44
   branch: develop
   specs:
     json-ld (3.0.2)
+      htmlentities (~> 4.3)
       json-canonicalization (~> 0.1)
       link_header (~> 0.0, >= 0.0.8)
       multi_json (~> 1.13)
@@ -36,7 +37,7 @@ GEM
     i18n (1.6.0)
       concurrent-ruby (~> 1.0)
     json-canonicalization (0.1.0)
-    json-ld-preloaded (3.0.2)
+    json-ld-preloaded (3.0.3)
       json-ld (~> 3.0)
       multi_json (~> 1.12)
       rdf (~> 3.0)
@@ -74,7 +75,7 @@ GEM
       sparql-client (~> 3.0)
     mini_portile2 (2.4.0)
     multi_json (1.13.1)
-    net-http-persistent (3.0.1)
+    net-http-persistent (3.1.0)
       connection_pool (~> 2.2)
     nokogiri (1.10.3)
       mini_portile2 (~> 2.4.0)
@@ -82,7 +83,7 @@ GEM
       nokogiri
     public_suffix (3.1.1)
     rack (2.0.7)
-    rake (12.3.2)
+    rake (12.3.3)
     rdf (3.0.12)
       hamster (~> 3.0)
       link_header (~> 0.0, >= 0.0.8)
@@ -134,7 +135,7 @@ GEM
     rdf-turtle (3.0.6)
       ebnf (~> 1.1)
       rdf (~> 3.0)
-    rdf-vocab (3.0.7)
+    rdf-vocab (3.0.8)
       rdf (~> 3.0, >= 3.0.11)
     rdf-xsd (3.0.1)
       rdf (~> 3.0)
diff --git a/common/terms.html b/common/terms.html
index 88bf1e17..044b7478 100644
--- a/common/terms.html
+++ b/common/terms.html
@@ -225,6 +225,12 @@
     A <a>named graph</a> created from the value of a <a>map entry</a>
     having an <a>expanded term definition</a>
     where <code>@container</code> is set to  <code>@graph</code>.</dd>
+  <dt class="changed"><dfn data-cite="JSON-LD11#dfn-included-map">included map</dfn></dt><dd class="changed">
+    An <a>included map</a> is a <a>map</a> of <a>entries</a> where the key
+    is interpreted as a vocabulary-<a>relative IRI</a>, and the value is a <a>node object</a>, <a>value object</a>,
+    <a>list object</a>, or an array of any of the above.
+    An <a>included map</a> contains values which may be referenced by terms of type `@included`,
+    for which the references are replaced with values from that map when expanding a document.</dd>
   <dt><dfn data-cite="JSON-LD11#dfn-index-map">index map</dfn></dt><dd>
     An <a>index map</a> is a <a>map</a> value of a <a>term</a>
     defined with <code>@container</code> set to <code>@index</code>,
@@ -331,7 +337,7 @@
     or an <a>expanded term definition</a>.
   </dd>
   <dt class="changed"><dfn data-cite="JSON-LD11#dfn-type-map">type map</dfn></dt><dd class="changed">
-    An <a>type map</a> is a <a>map</a> value of a <a>term</a>
+    A <a>type map</a> is a <a>map</a> value of a <a>term</a>
     defined with <code>@container</code> set to <code>@type</code>,
     whose keys are interpreted as <a>IRIs</a>
     representing the <code>@type</code> of the associated <a>node object</a>;
diff --git a/index.html b/index.html
index b88a18d6..7079c248 100644
--- a/index.html
+++ b/index.html
@@ -608,6 +608,11 @@ <h2>Syntax Tokens and Keywords</h2>
         Used in a <a>context definition</a> to load an external context
         within which the containing <a>context definition</a> is merged.
         This can be useful to add JSON-LD 1.1 features to JSON-LD 1.0 contexts.</dd>
+      <dt class="changed">`@included`</dt><dd class="changed">
+        Used in in a top-level <a>node object</a> to define an <a>included map</a>,
+        allowing <a>properties</a> of the `@included` to reference shared values which are
+        copied during <a>expansion</a>.
+      </dd>
     </dl>
 
     <p>All keys, <a>keywords</a>, and values in JSON-LD are case-sensitive.</p>
@@ -6755,6 +6760,11 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
   <dt>Node Type Indexing</dt><dd>As described in <a href="#node-type-indexing" class="sectionRef"></a>,
     node type indexing allows an <a>IRI</a> to reference a <a>node</a>
     and be interpreted as a type of that <a>node</a>.</dd>
+  <dt>Shared Value Indexing</dt><dd>As described in <a href="#shared-value-indexing" class="sectionRef"></a>,
+    property values which may be shared among a number of different <a>node objects</a>, can be
+    collected into an <a>included map</a>, which provides for a central location for referencing such shared values.
+    When expanded, the values are extracted from the <a>included map</a> to replace the indexes in
+    the property values with the referenced values.</dd>
 </dl>
 
 <p>See <a href="#named-graphs" class="sectionRef"></a> for other uses of indexing in JSON-LD.</p>
@@ -8270,6 +8280,243 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
   <p class="note"><a>Type maps</a> are a new feature in JSON-LD 1.1, requiring
     <a>processing mode</a> set to <code>json-ld-1.1</code>.</p>
 </section>
+
+<section class="informative changed"><h3>Shared Value Indexing</h3>
+  <p>It is sometimes the case that a nested data structure will repeat information.
+    Using a <a>node reference</a> provides some opportunities for consolidating
+    the information into a single <a>node object</a>, but this does not help
+    in all cases.</p>
+
+  <p>Specifications such as [[[MICRODATA]]] [[MICRODATA]] have an <a data-cite="MICRODATA#dfn-itemref">itemref</a>
+    mechanism which allows elements to be effectively copied within the [[DOM]].
+    The <a>included map</a> feature provides a similar capability.</p>
+
+  <p>For an example, consider a node object containing a list of different items,
+    some of which share some common elements:</p>
+
+  <pre class="example input"
+       id="included-values-to-be-expanded"
+       title="Included Values"
+       data-transform="updateExample">
+  <!--
+  {
+    "@context": {
+      "@version": 1.1,
+      "@vocab": "http://example.org/",
+      "@base": "http://example.org/base/",
+      "id": "@id", 
+      "type": "@type",
+      "included": "@included",
+      "enum": "http://example.org/enum#",
+      "classification": {"@type": "@included"},
+      "service": {"@type": "@included"},
+      "included": "@included"
+    },
+    "id": "http://example.org/base/1",
+    "type": "Thing-with-Items",
+    "items": [{
+      "id":"http://example.org/base/2",
+      "classification": "enum:c6",
+      "service": "enum:s2"
+    },####
+      3...26 go here####
+    {
+      "id": "http://example.org/base/27",
+      "classification": "enum:c6"
+    }],
+    "included": {
+      "enum:c6": {"type": "Type", "label": "Classification 6"},
+      "enum:s2": {"type": "Service", "label": "Login Service"}
+    }  
+  }
+  -->
+  </pre>
+
+  <p>When expanded, this will copy the `enum:c6` and `enum:s2` elements
+    from the <a>included map</a> into the item which references it.</p>
+
+  <aside class="example ds-selector-tabs"
+         title="Expanded form for included values">
+    <div class="selectors">
+      <button class="selected" data-selects="expanded">Expanded (Result)</button>
+      <button data-selects="statements">Statements</button>
+      <button data-selects="turtle">Turtle</button>
+      <a class="playground" target="_blank"
+         data-result-for="#included-values-to-be-expanded"></a>
+    </div>
+    <pre class="expanded result selected" data-transform="updateExample"
+         data-result-for="Included Values">
+    <!--
+    [{
+      "@id": "http://example.org/base/1",
+      "@type": ["http://example.org/Thing-with-Items"],
+      "http://example.org/items": [{
+        "@id": "http://example.org/base/2",
+        "http://example.org/classification": [{
+          "@type": ["http://example.org/Type"],
+          "http://example.org/label": [{"@value": "Classification 6"}]
+        }],
+        "http://example.org/service": [{
+          "@type": ["http://example.org/Service"],
+          "http://example.org/label": [{"@value": "Login Service"}]
+        }]
+      }, {
+        "@id": "http://example.org/base/27",
+        "http://example.org/classification": [{
+          "@type": ["http://example.org/Type"],
+          "http://example.org/label": [{"@value": "Classification 6"}]
+        }]
+      }]
+    }]
+    -->
+    </pre>
+    <table class="statements"
+           data-result-for="Expanded form for included values-expanded"
+           data-to-rdf>
+      <thead><tr><th>Subject</th><th>Property</th><th>Value</th></tr></thead>
+      <tbody>
+    <tr><td>http://example.org/base/1</td><td>http://example.org/items</td><td>http://example.org/base/27</td></tr>
+    <tr><td>http://example.org/base/1</td><td>http://example.org/items</td><td>http://example.org/base/2</td></tr>
+    <tr><td>http://example.org/base/1</td><td>rdf:type</td><td>http://example.org/Thing-with-Items</td></tr>
+    <tr><td>http://example.org/base/2</td><td>http://example.org/classification</td><td>_:b0</td></tr>
+    <tr><td>_:b0</td><td>http://example.org/label</td><td>Classification 6</td></tr>
+    <tr><td>_:b0</td><td>rdf:type</td><td>http://example.org/Type</td></tr>
+    <tr><td>http://example.org/base/2</td><td>http://example.org/service</td><td>_:b1</td></tr>
+    <tr><td>_:b1</td><td>http://example.org/label</td><td>Login Service</td></tr>
+    <tr><td>_:b1</td><td>rdf:type</td><td>http://example.org/Service</td></tr>
+    <tr><td>http://example.org/base/27</td><td>http://example.org/classification</td><td>_:b2</td></tr>
+    <tr><td>_:b2</td><td>http://example.org/label</td><td>Classification 6</td></tr>
+    <tr><td>_:b2</td><td>rdf:type</td><td>http://example.org/Type</td></tr>
+      </tbody>
+    </table>
+    <pre class="turtle"
+         data-content-type="text/turtle"
+         data-result-for="Expanded form for included values-expanded"
+         data-transform="updateExample"
+         data-to-rdf>
+    <!--
+    @base <http://example.org/base/> .
+    @prefix ex: <http://example.org/> .
+
+    <1> a ex:Thing-with-Items; ex:items <2>, <27> .
+
+    <2> ex:classification [ a ex:Type; ex:label "Classification 6" ];
+      ex:service [ a ex:Service; ex:label "Login Service" ] .
+
+    <27> ex:classification [ a ex:Type; ex:label "Classification 6" ] .
+    -->
+    </pre>
+  </aside>
+
+  <p>This feature becomes more powerful when combined with <a>nested properties</a>,
+    which allows the copied values to be promoted to be properties of the referencing node:</p>
+
+  <pre class="example input"
+       id="included-values-to-be-expanded-with-nesting"
+       title="Included Values with Nesting"
+       data-transform="updateExample">
+  <!--
+  {
+    "@context": {
+      "@version": 1.1,
+      "@vocab": "http://example.org/",
+      "@base": "http://example.org/base/",
+      "id": "@id", 
+      "type": "@type",
+      "included": "@included",
+      "enum": "http://example.org/enum#",
+      "classification": {"@id": "@nest", "@type": "@included"},
+      "service": {"@id": "@nest", "@type": "@included"}
+    },
+    "id": "http://example.org/base/1",
+    "type": "Thing-with-Items",
+    "items": [{
+      "id":"http://example.org/base/2",
+      "classification": "enum:c6",
+      "service": "enum:s2"
+    },####
+      3...26 go here####
+    {
+      "id": "http://example.org/base/27",
+      "classification": "enum:c6"
+    }],
+    "included": {
+      "enum:c6": {"type": "Type", "label": "Classification 6"},
+      "enum:s2": {"type": "Service", "label": "Login Service"}
+    }  
+  }
+  -->
+  </pre>
+
+  <p>When expanded, this will copy the contents of `enum:c6` and `enum:s2` elements
+    from the included map directly into the item which references it,
+    rather than as the value of the nesting properties.</p>
+
+  <aside class="example ds-selector-tabs"
+         title="Expanded form for included values with nesting">
+    <div class="selectors">
+      <button class="selected" data-selects="expanded">Expanded (Result)</button>
+      <button data-selects="statements">Statements</button>
+      <button data-selects="turtle">Turtle</button>
+      <a class="playground" target="_blank"
+         data-result-for="#included-values-to-be-expanded-with-nesting"></a>
+    </div>
+    <pre class="expanded result selected" data-transform="updateExample"
+         data-result-for="Included Values with Nesting">
+    <!--
+    [{
+      "@id": "http://example.org/base/1",
+      "@type": ["http://example.org/Thing-with-Items"],
+      "http://example.org/items": [{
+        "@id": "http://example.org/base/2",
+        "@type": ["http://example.org/Type", "http://example.org/Service"],
+        "http://example.org/label": [
+          {"@value": "Classification 6"},
+          {"@value": "Login Service"}
+        ]
+      }, {
+        "@id": "http://example.org/base/27",
+        "@type": ["http://example.org/Type"],
+        "http://example.org/label": [{"@value": "Classification 6"}]
+      }]
+    }]
+    -->
+    </pre>
+    <table class="statements"
+           data-result-for="Expanded form for included values with nesting-expanded"
+           data-to-rdf>
+      <thead><tr><th>Subject</th><th>Property</th><th>Value</th></tr></thead>
+      <tbody>
+      <tr><td>http://example.org/base/1</td><td>rdf:type</td><td>http://example.org/Thing-with-Items</td></tr>
+      <tr><td>http://example.org/base/2</td><td>rdf:type</td><td>http://example.org/Type</td></tr>
+      <tr><td>http://example.org/base/2</td><td>rdf:type</td><td>http://example.org/Service</td></tr>
+      <tr><td>http://example.org/base/2</td><td>http://example.org/label</td><td>Classification 6</td></tr>
+      <tr><td>http://example.org/base/2</td><td>http://example.org/label</td><td>Login Service</td></tr>
+      <tr><td>http://example.org/base/1</td><td>http://example.org/items</td><td>http://example.org/base/2</td></tr>
+      <tr><td>http://example.org/base/27</td><td>rdf:type</td><td>http://example.org/Type</td></tr>
+      <tr><td>http://example.org/base/27</td><td>http://example.org/label</td><td>Classification 6</td></tr>
+      <tr><td>http://example.org/base/1</td><td>http://example.org/items</td><td>http://example.org/base/27</td></tr>
+      </tbody>
+    </table>
+    <pre class="turtle"
+         data-content-type="text/turtle"
+         data-result-for="Expanded form for included values with nesting-expanded"
+         data-transform="updateExample"
+         data-to-rdf>
+    <!--
+    @base <http://example.org/base/> .
+    @prefix ex: <http://example.org/> .
+
+    <1> a ex:Thing-with-Items; ex:items <2>, <27> .
+
+    <2> a ex:Type, ex:Service;
+      ex:label "Classification 6", "Login Service" .
+
+    <27> a ex:Type; ex:label "Classification 6" .
+    -->
+    </pre>
+  </aside>
+</section>
 </section>
 
 <section class="informative"><h2>Reverse Properties</h2>
@@ -11535,6 +11782,7 @@ <h2>Node Objects</h2>
     <ul>
       <li><code>@context</code>,</li>
       <li><code>@id</code>,</li>
+      <li class="changed"><code>@included</code>,</li>
       <li><code>@graph</code>,</li>
       <li class="changed"><code>@nest</code>,</li>
       <li><code>@type</code>,</li>
@@ -11587,6 +11835,12 @@ <h2>Node Objects</h2>
       a <a>relative IRI</a>, a <a>compact IRI</a>, a <a>blank node identifier</a>,
       a <a>node object</a> or an <a>array</a> containing a combination of these.</p>
 
+    <p class="changed">If the <a>node object</a> contains the <code>@included</code> key,
+      its value MUST be an <a>included map</a>, and the <a>node object</a>
+      MUST NOT be the value of any other <a>map</a>.
+      See <a class="sectionRef" href="#shared-value-indexing"></a> for further discussion
+      on <a>included maps</a>.</p>
+
     <p>If the <a>node object</a> contains the <code>@index</code> key,
       its value MUST be a <a>string</a>. See
       <a class="sectionRef" href="#data-indexing"></a> for further discussion
@@ -11617,8 +11871,9 @@ <h2>Node Objects</h2>
       <li>an <a>array</a> of zero or more of any of the possibilities above,</li>
       <li>a <a>language map</a>,</li>
       <li>an <a>index map</a>,</li>
-      <li class="changed">an <a>id map</a>, or</li>
-      <li class="changed">a <a>type map</a></li>
+      <li class="changed">an <a>id map</a></li>
+      <li class="changed">a <a>type map</a>, or</li>
+      <li class="changed">an <a>included map</a></li>
     </ul>
   </section>
 
@@ -11918,6 +12173,21 @@ <h2>Type Maps</h2>
       added as a <code>@type</code> of the <a>node object</a> value when expanding.</p>
   </section>
 
+  <section class="changed">
+    <h2>Included Maps</h2>
+
+    <p>An <a>included map</a> is used to provide a set of indexed values.
+      The keys of the a <a>included map</a> MUST be <a>IRIs</a>
+      (<a>relative IRI</a>, <a>compact IRI</a> (including <a>blank node identifiers</a>), or <a>absolute IRI</a>)
+      and the values <a>node objects</a>, <a>value objects</a>, <a>list objects</a>
+      or an <a>array</a> of any of the above.
+      An <a>included map</a> MAY appear as the value of `@included`, or an alias,
+      in a top-level <a>node object</a>, and MUST NOT appear in an embedded <a>node object</a>.</p>
+
+    <p><a>Entries</a> in an <a>included map</a> are referenced from <a>properties</a> in a <a>node object</a>, where the
+      type mapping of the property term is `@included`.</p>
+  </section>
+
   <section class="changed">
     <h2>Property Nesting</h2>
 
@@ -12225,7 +12495,7 @@ <h2>Keywords</h2>
       or as the value of the <code>@container</code> key within an <a>expanded term definition</a>.
       The value of the <code>@type</code> key MUST  be a <a>term</a>, <a>absolute IRI</a>, a <a>relative IRI</a>,
       or a <a>compact IRI</a> (including <a>blank node identifiers</a>).
-      Within an expanded term definition, its value may also be either <code>@id</code> or <code>@vocab</code>.
+      Within an <a>expanded term definition</a>, its value may also be either <code class="changed">@included</code>, <code>@id</code>, or <code>@vocab</code>.
       This keyword is described further in <a class="sectionRef" href="#specifying-the-type"></a>
       and <a class="sectionRef" href="#typed-values"></a>.
     </dd>
@@ -12246,6 +12516,13 @@ <h2>Keywords</h2>
       This keyword is described further in <a class="sectionRef" href="#context-definitions"></a>,
       and <a class="sectionRef" href="#default-vocabulary"></a>.
     </dd>
+    <dt><code>@included</code></dt><dd>
+      The `@included` keyword MAY be aliased and MAY be used
+      as the value of <code>@type</code> in an <a>expanded term definition</a>.
+      Its value MUST be an <a>included map</a>.
+      This keyword is described further in <a class="sectionRef" href="#shared-value-indexing"></a>,
+      and <a class="sectionRef" href="#included-maps"></a>.
+    </dd>
   </dl>
 </section>
 </section>
@@ -13171,6 +13448,12 @@ <h2>Changes since JSON-LD Community Group Final Report</h2>
     <li>A context may contain an <code>@import</code> <a>entry</a> used to reference a remote context
       within a context, allowing <code>JSON-LD 1.1</code> features to be added to contexts originally
       authored for <code>JSON-LD 1.0</code>.</li>
+    <li>A top level <a>node object</a> may include an <a>included map</a>,
+      which is used to contain <a>entries</a> which can be substituted for property values
+      in other <a>node objects</a>, where that property has a type mapping to `@included`.
+      This allows values which are frequently repeated within a <a>JSON-LD document</a> to be consolidated
+      within an <a>included map</a>, allowing property values to be replaced with entries from
+      that <a>included map</a> upon <a>expansion</a>.</li>
   </ul>
 </section>