--- a/paq/prov-aq.html	Fri Apr 12 11:32:40 2013 +0100
+++ b/paq/prov-aq.html	Fri Apr 12 12:07:26 2013 +0100
@@ -387,9 +387,6 @@
 
       <section>
         <h2>URI types and dereferencing</h2>
-        <p class="TODO">
-          Proposed to drop Target-URI entry from this section.
-        </p>
         <p>
           A number of resource types are described above in <a href="#concepts" class="sectionRef"></a>.  The table below summarizes what these various URIs are intended to denote, and the kind of information that should be returned if they are dereferenced:
         </p>
@@ -402,7 +399,10 @@
           <tr style="vertical-align: top;">
             <td><a class="internalDFN">Target-URI</a></td>
             <td>Any resource that is described by some provenance - typically an <a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">entity</a> (in the sense of [[PROV-DM]]), but may be of another type (such as [[PROV-DM]] activity).</td>
-            <td>If the URI is dereferencable, it should return a representation or description of the resource for which provenance is provided.</td>
+            <td>
+              Not specified (the URI is not even required to be dereferencable).
+              <!-- If the URI is dereferencable, it should return a representation or description of the resource for which provenance is provided. -->
+            </td>
           </tr>
           <tr style="vertical-align: top;">
             <td><a class="internalDFN">Provenance-URI</a></td>
@@ -1030,7 +1030,7 @@
         The only defined operation on a pingback-URI is POST, which supplies links to provenance information or services as described above.  A pingback-URI MAY respond to other requests, but no requirements are imposed on how it responds.  In particular, it is not specified here how a pingback resource should respond to an HTTP GET request.
       </p>
       <p>
-        The pingback client MAY include extra <code>has_provenance</code> links to indicate provenance records related to a different resources, specified with correspondingly different anchor URIs. For example:
+        The pingback client MAY include extra <code>has_provenance</code> links to indicate provenance records related to a different resources, specified with correspondingly different anchor URIs.  These MAY indicate further provenance about existing resources, or about new resources (such as new entities derived or specialized from that for which the pingback URI was provided). For example:
       </p>
       <pre class="example code">
   C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1