--- a/html-data-guide/index.html	Wed Dec 21 12:16:23 2011 +0000
+++ b/html-data-guide/index.html	Wed Dec 21 12:17:15 2011 +0000
@@ -339,10 +339,9 @@
               <li>There are several built-in prefixes which can be used for popular vocabularies. These are listed as part of the <a href="http://www.w3.org/2011/rdfa-context/rdfa-1.1">RDFa 1.1 Core initial context</a>. Any IRI within one of these <a title="vocabulary">vocabularies</a> can be abbreviated using the <code>prefix:name</code> notation.</li>
               <li>The <code>@prefix</code> attribute can be used to define additional prefixes for other vocabularies.</li>
               <li>The <code>@vocab</code> attribute defines a default <a>vocabulary</a> within its scope; any IRIs that begin with this vocabulary can be abbreviated to a short name (the remainder of the IRI after the vocabulary IRI).</li>
-              <li>Namespace declarations (<code>@xmlns:prefix</code> attributes) can also be used to define prefixes. <strong>This mechanism is deprecated and should not be used.</strong></li>
             </ul>
             <p>
-              Note that if you use any of the last three mechanisms, the shortened IRIs can only be understood when they are within the scope of the relevant attributes. These can be easy to mislay when people copy and paste HTML from one place to another, or as the result of template changes in a content-management system. We therefore recommend that these attributes are avoided where possible &mdash; use the built-in prefixes or full IRIs in preference &mdash; and, where they are used, placed on elements that represent <a title="entity">entities</a> (those with <code>@about</code> or <code>@typeof</code> attributes) and repeated on each entity element rather than being inherited from an ancestor element. For more details, see <a href="#context-independence" class="sectionRef"></a>.
+              Note that if you use any of the last two mechanisms, the shortened IRIs can only be understood when they are within the scope of the relevant attributes. These can be easy to mislay when people copy and paste HTML from one place to another, or as the result of template changes in a content-management system. We therefore recommend that these attributes are avoided where possible &mdash; use the built-in prefixes or full IRIs in preference &mdash; and, where they are used, placed on elements that represent <a title="entity">entities</a> (those with <code>@about</code> or <code>@typeof</code> attributes) and repeated on each entity element rather than being inherited from an ancestor element. For more details, see <a href="#context-independence" class="sectionRef"></a>.
             </p>
           </section>
           <section id="mixing-vocabularies-microdata">