--- a/paq/prov-aq.html	Mon Mar 25 15:21:26 2013 +0000
+++ b/paq/prov-aq.html	Mon Mar 25 15:30:42 2013 +0000
@@ -759,12 +759,8 @@
       <!-- <section class="informative"> -->
       <section>
         <h2>Provenance query service description</h2>
-        <p class="TODO">
-          Review.  Stian suggests recommending use of JSON-LD.  I am resisting this because it is clearly allowed by "RDF (in any of its common serializations as determined by HTTP content negotiation)", focusing on a particular format as part of the underlying mechanism seems to go against REST principles, and at this stage it seems that promoting any particular format will draw objections from proponents of other formats.  I've taken a different tack, making the text more open about possible service description formats, while specifically presenting a description based on the RDF model.
-        </p>
         <p>
-          Dereferencing a <a class="internalDFN">service-URI</a> yields a service description. The service description presented here may be supplied as RDF (in any of its common serializations as determined by HTTP content negotiation), and it may contain descriptions of one or more available query mechanisms.  Each query mechanism is associated with an RDF type, as explained below.
-          (The presentation here of RDF service descriptions does not preclude use of non-RDF formats selectable by HTTP content negotiation.)
+          Dereferencing a <a class="internalDFN">service-URI</a> yields a service description. The service description may be in any format selectable through content negotiation, and it may contain descriptions of one or more available query mechanisms.  The format described here uses RDF, serialized as Turtle [[TURTLE]], but any selectable RDF serialization could be used.  In this RDF service description, each query mechanism is associated with an RDF type, as explained below.
         </p>
         <p>
           The overall structure of a service description is as follows: