Rename JSON-LD Implementation to Processor and Processor to API Implementation

See #237 (comment)

This addresses #237.

/cc @msporny @dlongley @gkellogg @niklasl @sandhawke

Author: lanthaler

spec/latest/json-ld-api/index.html

@@ -173,7 +173,8 @@ <h1>Introduction</h1>
   <ul>
     <li>Developers that want an overview of the JSON-LD API.</li>
     <li>Web authors and developers that want a very detailed view of how
-      a JSON-LD Implementation or a JSON-LD Processor's API operates.</li>
+      a <tref>JSON-LD Processor</tref> or a <tref>JSON-LD API Implementation</tref>
+      operates.</li>
     <li>Software developers that want to implement the algorithms to transform
       JSON-LD documents.</li>
   </ul>
@@ -558,33 +559,37 @@ <h1>Conformance</h1>
     in [[!RFC2119]].</p>
 
   <p>There are three classes of products that can claim conformance to this
-    specification: <tref title="JSON-LD Implementation">JSON-LD Implementations</tref>
-    and <tref title="JSON-LD Processor">JSON-LD Processors</tref>.</p>
+    specification: <tref title="JSON-LD Processor">JSON-LD Processors</tref>
+    and <tref title="JSON-LD API Implementation">JSON-LD API Implementations</tref>.</p>
 
-  <p>A conforming <tdef>JSON-LD Implementation</tdef> is a system which can perform the
+  <p>A conforming <tdef>JSON-LD Processor</tdef> is a system which can perform the
     <a href="#expansion-algorithm">Expansion</a>, <a href="#compaction-algorithm">Compaction</a>,
     and <a href="#flattening-algorithm">Flattening</a> operations defined in this specification.</p>
 
-  <p>A conforming <tdef>JSON-LD Processor</tdef> is a conforming <tref>JSON-LD Implementation</tref>
-    that exposes the Application Programming Interface (API) defined in this specification.
-    It MUST implement the <code>json-ld-1.0</code> processing mode (for further details, see the
+  <p>A conforming <tdef>JSON-LD API Implementation</tdef> is a conforming <tref>JSON-LD Processor</tref>
+    that exposes the <a href="#the-application-programming-interface">Application Programming Interface (API)</a>
+    defined in this specification. It MUST implement the <code>json-ld-1.0</code>
+    processing mode (for further details, see the
     <code class="idlMemberName"><a href="#widl-JsonLdOptions-processingMode">processingMode</a></code>
     option of <a>JsonLdOptions</a>).</p>
 
-  <p>JSON-LD Implementations or Processors MUST NOT attempt to correct malformed
-    <tref title="IRI">IRIs</tref> or language tags; however, they MAY issue validation
-    warnings. IRIs are not modified other than converted between
-    <tref title="relative IRI">relative</tref> and
+  <p><tref title="JSON-LD Processor">JSON-LD Processors</tref> and
+    <tref title="JSON-LD API Implementation">API Implementations</tref> MUST NOT
+    attempt to correct malformed <tref title="IRI">IRIs</tref> or language tags;
+    however, they MAY issue validation warnings. IRIs are not modified other
+    than converted between <tref title="relative IRI">relative</tref> and
     <tref title="absolute IRI">absolute IRIs</tref>.</p>
 
   <p>A conforming <tdef>JSON-LD-RDF Converter</tdef> is a system that can perform
     <a href="#convert-to-rdf-algorithm">Conversion to RDF</a> and
     <a href="#convert-from-rdf-algorithm">Conversion from RDF</a>.</p>
 
-  <p>The algorithms in this specification are generally written with more concern for clarity than
-    efficiency. Thus, JSON-LD Implementations and Processors may implement the algorithms
-    given in this specification in any way desired, so long as the end result is indistinguishable
-    from the result that would be obtained by the specification's algorithms.</p>
+  <p>The algorithms in this specification are generally written with more concern for clarity
+    than efficiency. Thus, <tref title="JSON-LD Processor">JSON-LD Processors</tref>
+    and <tref title="JSON-LD API Implementation">API Implementations</tref> may
+    implement the algorithms given in this specification in any way desired,
+    so long as the end result is indistinguishable from the result that would
+    be obtained by the specification's algorithms.</p>
 
   <p class="note">Implementers can partially check their level of conformance to
     this specification by successfully passing the test cases of the JSON-LD test
@@ -3671,8 +3676,9 @@ <h2>Data Round Tripping</h2>
       backslash-escape the forward slash character. For example, the value
       <code>http://example.com/</code> would be serialized as <code>http:\/\/example.com\/</code>.
       This is problematic as other JSON parsers might not understand those escaping characters.
-      There is no need to backslash-escape forward slashes in JSON-LD. To aid interoperability
-      between JSON-LD processors, a JSON-LD serializer MUST NOT backslash-escape forward slashes.</p>
+      There is no need to backslash-escape forward slashes in JSON-LD. To aid
+      interoperability between JSON-LD processors, forward slashes MUST NOT be
+      backslash-escaped.</p>
   </section> <!-- end of Data Round Tripping -->
 </section>
 
@@ -3682,19 +3688,19 @@ <h2>The Application Programming Interface</h2>
 
   <p>This API provides a clean mechanism that enables developers to convert
     JSON-LD data into a variety of output formats that are often easier to
-    work with. A conformant JSON-LD Processor MUST implement the entirety of the
-    following API.</p>
+    work with. A conformant <tref>JSON-LD API Implementation</tref> MUST
+    implement the entirety of the following API.</p>
 
   <section>
     <h3>JsonLdProcessor</h3>
 
-    <p>The JSON-LD Processor interface is the high-level programming structure
+    <p>The <a>JsonLdProcessor</a> interface is the high-level programming structure
       that developers use to access the JSON-LD transformation methods.</p>
 
     <p>It is important to highlight that conformant
-      <tref title="JSON-LD Processor">JSON-LD processors</tref> MUST NOT modify
-      the input parameters. If an error is detected, the <i>callback</i> is
-      invoked passing a <a>JsonLdError</a> with the corresponding error
+      <tref title="JSON-LD API Implementation">JSON-LD API Implementations</tref>
+      MUST NOT modify the input parameters. If an error is detected, the <i>callback</i>
+      is invoked passing a <a>JsonLdError</a> with the corresponding error
       <code class="idlMemberName"><a href="#widl-JsonLdError-code">code</a></code>
       and processing is stopped.</li></p>
 
@@ -3866,9 +3872,9 @@ <h3>JsonLdProcessor</h3>
   <section>
     <h3>Callbacks</h3>
 
-    <p>JSON-LD processors utilize callbacks in order to exchange information in
-      an asynchronous manner with applications. This section details the
-      parameters of those callbacks.</p>
+    <p><tref title="JSON-LD API Implementation">JSON-LD API Implementations</tref>
+      utilize callbacks in order to exchange information in an asynchronous manner
+      with applications. This section details the parameters of those callbacks.</p>
 
     <section>
       <h3>JsonLdCallback</h3>
@@ -3964,9 +3970,9 @@ <h3>JsonLdOptions</h3>
         <dt>object or DOMString expandContext = null</dt>
         <dd>A context that is used to initialize the active context when expanding a document.</dd>
         <dt>DOMString processingMode = "json-ld-1.0"</dt>
-        <dd>If set to <code>json-ld-1.0</code>, the JSON-LD Processor MUST produce
+        <dd>If set to <code>json-ld-1.0</code>, the JSON-LD processor MUST produce
           exactly the same results as the algorithms defined in this specification.
-          If set to another value, the JSON-LD Processor is allowed to extend
+          If set to another value, the JSON-LD processor is allowed to extend
           or modify the algorithms defined in this specification to enable
           application-specific optimizations. The definition of such
           optimizations is beyond the scope of this specification and thus