turn into a candidate addition

I didn't follow the pattern 'change_N' for the id,
because this change will also be present in json-ld-syntax (in comment/terms),
and so will probably require a candidate addition in that spec too (with a different index).
Hence the more robust id used here.

Author: pchampin

common/terms.html

@@ -382,8 +382,9 @@
     as a key, type, or elsewhere that a string is interpreted as a vocabulary item.
     Its value is either a string (<dfn data-cite="JSON-LD11#dfn-simple-term-definition" data-lt="simple term definition|simple term" data-lt-noDefault>simple term definition</dfn>),
     expanding to an <a>IRI</a>,
-    or a map (<a>expanded term definition</a>).<br/>
-    For <a data-cite="JSON-LD11-API#context-processing-algorithms">context processing</a>, <a>term definition</a> values are converted internally to a dedicated data structure that is easier to process.
+    or a map (<a>expanded term definition</a>).
+    <ins cite="#change_api_638"><br/>
+    For <a data-cite="JSON-LD11-API#context-processing-algorithms">context processing</a>, <a>term definition</a> values are converted internally to a dedicated data structure that is easier to process.</ins>
   </dd>
   <dt class="changed"><dfn data-cite="JSON-LD11#dfn-type-map">type map</dfn></dt><dd class="changed">
     A <a>type map</a> is a <a>map</a> value of a <a>term</a>

index.html

@@ -1071,10 +1071,19 @@ <h2>RDF Serialization/Deserialization</h2>
       using information provided by the <a>active context</a>. This
       section describes how to produce an <a>active context</a>.</p>
 
+    <div id="change_api_638" class="candidate correction">
+      <span class="marker">Candidate Correction 8</span>
+      <p>Change the type of <a>term definition</a> from <a>array</a> to <a>map</a> in <a>active context</a>,
+        to be consistent with the way it is used in the algorithms.
+        Clarify the notion <a>term definition</a>.
+        For more information, refer to <a href="https://github.com/w3c/json-ld-api/issues/630">issue 630</a>.
+      </p>
+    </div>
+
     <p>The <a>active context</a> consists of:</p>
     <ul>
       <li>the active <a>term definitions</a> which specify how
-        keys and values have to be interpreted (<a class="changed">map</a> of <a>term definitions</a>),</li>
+        keys and values have to be interpreted (<del cite="#change_api_638"><a>array</a></del><ins cite="#change_api_638"><a>map</a></ins> of <a>term definitions</a>),</li>
       <li>the current <dfn data-lt="context-base-iri" data-lt-noDefault>base IRI</dfn> (<a>IRI</a>),</li>
       <li class="changed">the <dfn>original base URL</dfn> (<a>IRI</a>),</li>
       <li class="changed">an <dfn data-lt="context-inverse" data-lt-noDefault>inverse context</dfn> (<a>inverse context</a>),</li>
@@ -1085,7 +1094,7 @@ <h2>RDF Serialization/Deserialization</h2>
         used when a non-propagated <a>context</a> is defined.</li>
     </ul>
 
-    <p>Each <a>term definition</a><span class="changed">'s value</span> consists of:</p>
+    <p>Each <a>term definition</a><ins cite="#change_api_638">'s value</ins> consists of:</p>
     <ul>
       <li>an <dfn>IRI mapping</dfn> (<a>IRI</a>),</li>
       <li class="changed">a <dfn>prefix flag</dfn> (<a>boolean</a>),</li>
@@ -7092,6 +7101,8 @@ <h2>Change log</h2>
      <li>2024-10-31: Abstract JSON serialization from WebIDL interfaces to allow
       for alternative formats,
       as described in <a href="#change_7">Candidate Correction 7</a></li>
+     <li>2025-02-28: Clarifiy language about <a>term definitions</a>,
+      as described in <a href="#change_api_638">Candidate Correction 8</a></li>
  </ul>
   </details>