Rename "General Solution" to "Overview"
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Mon, 01 Apr 2013 19:59:51 +0200
changeset 1512 257739503f1e
parent 1511 ab677a490da7
child 1513 64add7931d64
Rename "General Solution" to "Overview"

This addresses #234.
spec/latest/json-ld-api/index.html
--- a/spec/latest/json-ld-api/index.html	Mon Apr 01 15:38:30 2013 +0200
+++ b/spec/latest/json-ld-api/index.html	Mon Apr 01 19:59:51 2013 +0200
@@ -811,7 +811,7 @@
       references to remote contexts, this includes their retrieval.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>First we prepare a new <tref>active context</tref> <i>result</i> by cloning
         the current <tref>active context</tref>. Then we normalize the form of the passed
@@ -982,7 +982,7 @@
       for a <tref>term</tref> being processed in a <tref>local context</tref>.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p><tref title="term definition">Term definitions</tref> are created by
         parsing the information in the given <tref>local context</tref> for the
@@ -1205,7 +1205,7 @@
       <a href="#create-term-definition">Create Term Definition algorithm</a>.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>In order to expand <i>value</i> to an <tref>absolute IRI</tref>, we must
         first determine if it is <tref>null</tref>, a <tref>term</tref>, a
@@ -1332,7 +1332,7 @@
       <tref title="array">arrays</tref> in <tref>expanded form</tref>.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>Starting with its root <i>element</i>, we can process the
         JSON-LD document recursively, until we have a fully
@@ -1731,7 +1731,7 @@
       after the application of this algorithm.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>If <tref>active property</tref> has a <tref>type mapping</tref> in the
         <tref>active context</tref> set to <code>@id</code> or <code>@vocab</code>,
@@ -1820,7 +1820,7 @@
       <tref title="number">numbers</tref>.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>Starting with its root <i>element</i>, we can process the
         JSON-LD document recursively, until we have a fully
@@ -2180,7 +2180,7 @@
       matches the value's mappings.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>To create an <tref>inverse context</tref> for a given
         <tref>active context</tref>, each <tref>term</tref> in the
@@ -2314,7 +2314,7 @@
       context-appropriate <tref>term</tref>.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>If the passed <tref>IRI</tref> is <tref>null</tref>, we simply
         return <tref>null</tref>. Otherwise, we first try to find a <tref>term</tref>
@@ -2571,7 +2571,7 @@
       be best used to express the value.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>The <tref title="inverse context">inverse context's</tref> entry for
         the <tref>IRI</tref> will be first searched according to the preferred
@@ -2651,7 +2651,7 @@
       <tref>active property</tref>.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>The <i>value</i> to compact has either an <code>@id</code> or an
         <code>@value</code> member.</p>
@@ -2750,7 +2750,7 @@
       the code required to process JSON-LD data in certain applications.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>First, a <i>node map</i> is generated using the
         <a href="#node-map-generation">Node Map Generation algorithm</a>
@@ -2820,7 +2820,7 @@
       stored under their <tref>graph name</tref>.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>The algorithm recursively runs over an expanded JSON-LD document to
         collect all <tref title="property">properties</tref> of a <tref>node</tref>
@@ -2988,7 +2988,7 @@
       by the introduction of new ones.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>The simplest case is if there exists already a <tref>blank node identifier</tref>
         in the <i>identifier map</i> for the passed <i>identifier</i>, in which
@@ -3069,7 +3069,7 @@
       <tref>blank node identifier</tref> to be used as a <tref>graph name</tref>.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>The JSON-LD document is expanded and converted to a <i>node map</i> using the
         <a href="#node-map-generation">Node Map Generation algorithm</a>.
@@ -3162,7 +3162,7 @@
       to be used as the <tref>object</tref> of an <tref>RDF triple</tref>.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p><tref title="value object">Value objects</tref> are transformed to
         <tref title="RDF literal">RDF literals</tref> as defined in the section
@@ -3224,7 +3224,7 @@
       as defined in RDF Semantics [[!RDF-MT]].</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>For each element of the <tref>list</tref> a new <tref>blank node identifier</tref>
         is allocated which is used to generate <code>rdf:first</code> and
@@ -3275,7 +3275,7 @@
     <p class="note">This algorithm does not support lists containing lists.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p>Iterate through each graph in the dataset, converting
         <tref title="rdf collection">RDF Collections</tref> into a <tref>list</tref>
@@ -3442,7 +3442,7 @@
       and a RDF blank node or IRI to an JSON-LD <tref>node object</tref>.</p>
 
     <section class="informative">
-      <h3>General Solution</h3>
+      <h3>Overview</h3>
 
       <p><tref title="RDF literal">RDF literals</tref> are transformed to
         <tref title="value object">value objects</tref> as defined in the section