--- a/paq/working/prov-aq.html	Thu Apr 26 13:19:03 2012 +0100
+++ b/paq/working/prov-aq.html	Thu Apr 26 14:14:11 2012 +0100
@@ -250,8 +250,12 @@
             <dd>a service that provides <class="internalDFN">provenance information</a> given a <a class="internalDFN">target-uri</a>.</dd>
             <dt><dfn>Service-URI</dfn></dt>
             <dd>the URI of a <a class="internalDFN">provenance service</a>.</dd>
+<!--
             <dt><dfn>Resource</dfn></dt>
             <dd>also referred to as <dfn>resource on the Web</dfn>: a resource as described by the Architecture of the World Wide Web [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>. A resource may be associated with multiple instances or views (<a class="internalDFN">constrained resource</a>s) with differing provenance.</dd>
+-->
+            <dt><dfn>Resource</dfn></dt>
+            <dd>also referred to as <dfn>resource on the Web</dfn>: a resource  in the general sense of "whatever might be identified by a URI", as described by the Architecture of the World Wide Web [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>. A resource may be associated with multiple instances or views (<a class="internalDFN">constrained resource</a>s) with differing provenance.</dd>
           </dl>
         </p>
 
@@ -476,7 +480,7 @@
             <li>MIME multipart/related [[RFC2387]]: both email and HTTP are based on MIME or MIME-derivatives, so this has the advantage of working well with the network transfer mechanisms discussed in the motivating scenarios considered.
             </li>
             <li>
-              Composite object-packaging work from the digital library community, of which there are several (e.g., <a href="http://www.openarchives.org/ore/">ORE</a>, <a href="http://xml.coverpages.org/mpeg21-didl.html">MPEG-21 DIDL</a>, <a href="https://wiki.ucop.edu/display/Curation/BagIt">BagIt</a>) to name a handful.  Practical implementations of these are commonly based on the ZIP file format.
+              Composite object-packaging work from the digital library community, of which there are several (e.g., <a href="http://www.openarchives.org/ore/">ORE</a>, <a href="http://www.loc.gov/standards/mets/">METS</a>, <a href="http://xml.coverpages.org/mpeg21-didl.html">MPEG-21 DIDL</a>, <a href="https://wiki.ucop.edu/display/Curation/BagIt">BagIt</a>) to name a handful.
             </li>
             <li>
               Packaging formats along the lines of those used for shipping Java web applications (basically, a ZIP file with a manifest and some imposed structure)
@@ -532,6 +536,9 @@
           To facilitate service discovery, we recommend that RDF publication of service descriptions uses the provenance service type <code><provns/>ProvenanceService</code>, defined by the provenance ontology [[PROV-O]].
           The RDF service description example below in <a href="#provenance-service-description" class="sectionRef"></a> shows this use.
         </p>
+        <p class="TODO">
+          @@TODO: sync up term definitions with provenance ontology specification.
+        </p>
       </section>
 
       <!-- <section class="informative"> -->
@@ -548,6 +555,9 @@
         </p>
         <p>A client may retrieve this service description and extract the associated value for <code>prov:provenance-uri-template</code>.  This value is a string containing a URI template [[URI-template]] (level 2). A URI for the desired provenance information is obtained by expanding the URI template with the variable <code>uri</code> set to the resource-URI for which provenance is required.  If the target-URI contains '#' or '&amp;' these  must be %-escaped as <code>%23</code> or <code>%26</code> respectively before template expansion.
         </p>
+        <p class="TODO">
+          @@TODO: sync up term definitions with provenance ontology specification.
+        </p>
       </section>
 
     </section>
@@ -774,7 +784,7 @@
         Provenance is central to establishing trust in data. If provenance information is corrupted, it may lead agents (human or software) to draw inappropriate and possibly harmful conclusions.  Therefore, care is needed to ensure that the integrity of provenance information is maintained.
       </p>
       <p>
-        When using HTTP to access provenance information, or to determine a provenance URI, secure HTTP (https) SHOULD be used.
+        Secure HTTP (https) SHOULD be used across unsecured networks when accessing provenance information that may be used as a basis for trust decisions, or to obtain a provenance URI for same.
       </p>
       <p>
         When retrieving a provenance URI from a document, steps SHOULD be taken to ensure the document itself is an accurate copy of the original whose author is being trusted (e.g. signature checking, or verifying its checksum against an author-provided secure web service).