RESOLVED: accept conformance section with "server" instead of "engine" and "parsing" ldpatch
authorAndrei Sambra <andrei@w3.org>
Mon, 09 Feb 2015 11:09:57 -0500
branchldpatch
changeset 942 8b80d696fa0d
parent 941 ddb7b8df660f
child 943 f718028dbedc
RESOLVED: accept conformance section with "server" instead of "engine" and "parsing"
ldpatch.html
--- a/ldpatch.html	Sun Feb 08 21:44:43 2015 -0500
+++ b/ldpatch.html	Mon Feb 09 11:09:57 2015 -0500
@@ -481,19 +481,19 @@
 
       <p>This specification defines conformance criteria for:</p>
       <ul>
-          <li>LD Patch documents</li>
-	  <li>LD Patch parsers</li>
-	  <li>LD Patch processors</li>
-	  <li>LD Patch engines</li>
+        <li>LD Patch documents</li>
+        <li>LD Patch parsers</li>
+        <li>LD Patch processors</li>
+        <li>LD Patch engines</li>
       </ul>
 
       <p>A conforming <strong>LD Patch document</strong> is a Unicode string that conforms to the grammar defined in the <a href="#concrete-syntax">Concrete Syntax section</a>.</p>
 
-      <p>A conforming <strong>LD Patch parser</strong> is a system capable of reading LD Patch documents. The resulting abstract concept is called a <strong>Linked Data patch</strong>, or simply <strong>patch</strong> when the context is unambiguous.</p>
+      <p>A conforming <strong>LD Patch parser</strong> is a system capable of parsing LD Patch documents. The resulting abstract concept is called a <strong>Linked Data patch</strong>, or simply <strong>patch</strong> when the context is unambiguous.</p>
 
       <p>A conforming <strong>LD Patch processor</strong> is a system capable of executing a Linked Data patch against an <a class="externalDFN" href="http://www.w3.org/TR/rdf11-concepts/#section-rdf-graph">RDF Graph</a> and whose semantics follow the ones defined in the <a href="#semantics">LD Patch Semantics section</a>. It would either return a new graph or update the input graph in place.</p>
 
-      <p>A conforming <strong>LD Patch engine</strong> is a system capable of processing an LD Patch document through an HTTP PATCH request as defined in <a href="http://www.w3.org/TR/ldp/#h4_ldpr-HTTP_PATCH">LDP PATCH</a> [[!LDP]]. It MUST handle errors as defined in the <a href="#error-handling">Error Handling section</a>.</p>
+      <p>A conforming <strong>LD Patch server</strong> is a system capable of processing an LD Patch document through an HTTP PATCH request as defined in <a href="http://www.w3.org/TR/ldp/#h4_ldpr-HTTP_PATCH">LDP PATCH</a> [[!LDP]]. It MUST handle errors as defined in the <a href="#error-handling">Error Handling section</a>.</p>
 
       <p>The IRI that identifies the LD Patch format is: <code>http://www.w3.org/ns/formats/LD_Patch</code>.</p>