--- a/bestpractices/BestPractices.html	Thu Feb 02 12:38:16 2012 +0000
+++ b/bestpractices/BestPractices.html	Thu Feb 02 12:53:29 2012 +0000
@@ -197,12 +197,17 @@
         In the above example,
         <code>&lt;/home/stain/src/provenance-wg/prov&gt;</code> is asserted to
         be a PROV Account. Applications should take care to process HTTP
-        redirections, HTTP headers like <code>Content-Entity</code> to
-        relate the provenance resource with any modifications to
+        redirections and HTTP headers like <code>Content-Location</code> to
+        relate the URI for the provenance resource with 
         relative URIs in RDF representations, such as using
         <code>xml:base</code> and <code>@base</code>.
         </p>
 
+        <div class="recommendation">
+        PROV resources SHOULD in their RDF representation(s)
+        assert that they are an instance of prov:Account. This MAY be
+        a relative URI reference
+        </div>
 
         <div class="note">
         TODO: Add <code>prov:Account</code> to PROV-O for this purpose.
@@ -218,7 +223,13 @@
         <section id="dublincore">
             <h3>Dublin core</h3>
         </section>
-        
+    </section>
+
+    <section id="collections">
+        <h2>Collections</h2>
+        <div class="note">
+        To be written by Paolo and Stian.
+        </div>
     </section>
 
 	<section id="specializing-provenance-ontology-for-domain-specific-provenance-applications">