--- a/paq/provenance-access.html	Thu Nov 17 17:16:19 2011 +0000
+++ b/paq/provenance-access.html	Thu Nov 17 17:27:38 2011 +0000
@@ -929,7 +929,7 @@
           <li>I: Accessing the provenance
             <ul>
               <li>W: a web client needs one or more URIs for provenance information, and/or URI(s) for a provenance query service and sufficient additional information about the resource to formulate an effective query.  They may also need access information that can be used to assess (or help a user assess) the trustworthiness of provenance of information obtained, (which could be more provenance information)</li>
-              <li>E: an email client is a passive receiver of information, so asking one to retrieve provenance information is a perverse expectation.  There have been some attempts to standardize email protocols that interact with the email sender (e.g. [[RFC3297]]) but such mechanisms have not been significantly deployed in practice. This case can be viewed as a variation on the shell-client case (S) below.  If all provenance information is sent <em>with</em> the original content using standard email mechanisms (MIME multipart, etc.) then the email client may use that (or hand it off to a helper application) as the basis for provenance-based analysis or presentation.</li>
+              <li>E: an email client is a passive receiver of information, so asking one to retrieve provenance information is a perverse expectation.  There have been some attempts to standardize email protocols that interact with the email sender but such mechanisms have not been significantly deployed in practice. This case can be viewed as a variation on the shell-client case (S) below.  If all provenance information is sent <em>with</em> the original content using standard email mechanisms (MIME multipart, etc.) then the email client may use that (or hand it off to a helper application) as the basis for provenance-based analysis or presentation.</li>
               <li>S: command shell or other local application.  This is the general case for provenance access.  Given some arbitrary information, what does a provenance-aware application need to access the required provenance information?  It may employ any of the mechanisms described above.</li>
             </ul>
           </li>