--- a/spec/latest/json-ld-api/index.html	Tue Nov 27 17:40:30 2012 +0100
+++ b/spec/latest/json-ld-api/index.html	Sun Dec 02 16:12:47 2012 -0500
@@ -1213,7 +1213,7 @@
         process the value using <a href="#context-process-property">step 2.4.3.1</a> of the
         <a href="#context">Context Processing algorithm</a>.</li>
       <li>If the <tref>active context</tref> contains a <tref>term</tref> mapping for the value using
-        a case-sensitive comparison, use the mapped value as an IRI, unless a <tref>local context</tref>
+        a case-sensitive comparison, use the mapped value, unless a <tref>local context</tref>
         is being processed, in which case, return the result of recursing to expand the mapped value.</li>
       <li>Otherwise, split the value into a <em>prefix</em> and <em>suffix</em> from the first occurrence of ':'.</li>
       <li>If the prefix is a '_' (underscore), the value represents a named <tref>blank node</tref>.</li>

--- a/spec/latest/json-ld-syntax/index.html	Tue Nov 27 17:40:30 2012 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Sun Dec 02 16:12:47 2012 -0500
@@ -375,11 +375,14 @@
     <dt><tdef>true</tdef> and <tdef>false</tdef></dt><dd>
       Values that are used to express one of two possible boolean states.</dd>
     <dt><tdef>null</tdef></dt>
-    <dd>The <code>null</code> value. Unless otherwise specified, a key-value
-      pair in the body of a JSON-LD document whose value is <em>null</em>
-      has the same meaning as if the key-value pair was not defined. If <code>@value</code>,
-      <code>@list</code>, or <code>@set</code> is set to <em>null</em> in
-      expanded form, then the entire <tref>JSON object</tref> is ignored.</dd>
+    <dd>The <tref>null</tref> value. A key-value pair in the 
+      <code>@context</code> where the value, or the <code>@id</code> of the
+      value, is <tref>null</tref> explicitly decouples a term's association 
+      with an IRI. A key-value pair in the body of a JSON-LD document whose 
+      value is <tref>null</tref> has the same meaning as if the key-value pair 
+      was not defined. If <code>@value</code>, <code>@list</code>, or 
+      <code>@set</code> is set to <tref>null</tref> in expanded form, then 
+      the entire <tref>JSON object</tref> is ignored.</dd>
   </dl>
 </section>
 
@@ -2407,6 +2410,40 @@
 
 </section>
 
+
+<section>
+<h2>Explicitly Ignoring Data</h2>
+
+<p>At times, it becomes necessary to explicitly ignore data expressed in JSON
+documents because it has no semantic meaning. For this purpose, an author
+may associate the <tref>null</tref> keyword with a <tref>term</tref> in the
+JSON-LD Context.</p>
+
+<pre class="example" data-transform="updateExample"
+     title="Using the null keyword to ignore data">
+<!--
+{
+  "@context":
+  {
+     "@vocab": "http://schema.org/",
+     ****"databaseId": null****
+  },
+  "name": "Manu Sporny",
+  "description": "That guy",
+  "gender": "Male",
+  ****"databaseId": "23987520"****
+}
+-->
+</pre>
+
+<p>In the example above, the author has used <code>@vocab</code> as the base
+IRI for all terms in the document, but has expressed that the
+<code>databaseId</code> value should not be processed by the JSON-LD processor
+by associating it with the <tref>null</tref> keyword in the JSON-LD Context.
+</p>
+
+</section>
+
 <section>
 <h3>Expanded Document Form</h3>
 <p>The JSON-LD API [[JSON-LD-API]] defines an method for <em>expanding</em> a