--- a/paq/working/prov-aq.html	Thu May 03 18:30:09 2012 +0100
+++ b/paq/working/prov-aq.html	Thu May 03 18:35:31 2012 +0100
@@ -636,7 +636,7 @@
             <pre class="example code">
   @prefix prov: &lt;<provns/>&gt;
   SELECT ?generationStartTime WHERE {
-      <http://example.org/resource> prov:wasGeneratedBy ?activity .
+      &lt;http://example.org/resource&gt; prov:wasGeneratedBy ?activity .
       ?activity prov:startedAtTime ?generationStartTime .
   }
             </pre>
@@ -644,9 +644,6 @@
           <p>
             This query essentially extracts all available properties and values available from the query service used that are directly about the specified resource, and returns them as an RDF graph.  This may be fine if the service contains <em>only</em> provenance information about the indicated resource, or if the non-provenance information is also of interest.  A more complex query using specific provenance vocabulary terms may be needed to selectively retrieve just provenance information when other kinds of information are also available.
           </p>
-          <p class="TODO">
-            @@TODO: specific provenance namespace and property to be determined by the model specification?  The above query pattern assumes provenance information is included in direct properties about the resource.  When an RDF provenance vocabulary is fully formulated, this may well turn out to not be the case.  A better example would be one that retrieves specific provenance information when the vocabulary terms have been defined.
-          </p>
         </section>
 
       </section>