jena-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1019949 [1/2] - in /websites/staging/jena/trunk/content: ./ documentation/ documentation/assembler/ documentation/csv/ documentation/fuseki2/ documentation/hadoop/ documentation/inference/ documentation/io/ documentation/jdbc/ documentatio...
Date Mon, 23 Oct 2017 02:34:03 GMT
Author: buildbot
Date: Mon Oct 23 02:34:02 2017
New Revision: 1019949

Log:
Staging update by buildbot for jena

Modified:
    websites/staging/jena/trunk/content/   (props changed)
    websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html
    websites/staging/jena/trunk/content/documentation/csv/implementation.html
    websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html
    websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-data-services.html
    websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-embedded.html
    websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-logging.html
    websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-server-protocol.html
    websites/staging/jena/trunk/content/documentation/fuseki2/index.html
    websites/staging/jena/trunk/content/documentation/hadoop/common.html
    websites/staging/jena/trunk/content/documentation/inference/index.html
    websites/staging/jena/trunk/content/documentation/io/rdf-input.html
    websites/staging/jena/trunk/content/documentation/io/rdf-output.html
    websites/staging/jena/trunk/content/documentation/io/rdfxml_howto.html
    websites/staging/jena/trunk/content/documentation/jdbc/custom_driver.html
    websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html
    websites/staging/jena/trunk/content/documentation/notes/datasetgraph.html
    websites/staging/jena/trunk/content/documentation/notes/jena-internals.html
    websites/staging/jena/trunk/content/documentation/notes/jena-repack.html
    websites/staging/jena/trunk/content/documentation/notes/reification_previous.html
    websites/staging/jena/trunk/content/documentation/notes/sse.html
    websites/staging/jena/trunk/content/documentation/notes/typed-literals.html
    websites/staging/jena/trunk/content/documentation/ontology/index.html
    websites/staging/jena/trunk/content/documentation/permissions/design.html
    websites/staging/jena/trunk/content/documentation/permissions/evaluator.html
    websites/staging/jena/trunk/content/documentation/permissions/example.html
    websites/staging/jena/trunk/content/documentation/query/algebra.html
    websites/staging/jena/trunk/content/documentation/query/construct-quad.html
    websites/staging/jena/trunk/content/documentation/query/custom_aggregates.html
    websites/staging/jena/trunk/content/documentation/query/explain.html
    websites/staging/jena/trunk/content/documentation/query/group-by.html
    websites/staging/jena/trunk/content/documentation/query/http-auth.html
    websites/staging/jena/trunk/content/documentation/query/library-function.html
    websites/staging/jena/trunk/content/documentation/query/logging.html
    websites/staging/jena/trunk/content/documentation/query/service.html
    websites/staging/jena/trunk/content/documentation/query/spatial-query.html
    websites/staging/jena/trunk/content/documentation/query/text-query.html
    websites/staging/jena/trunk/content/documentation/query/update.html
    websites/staging/jena/trunk/content/documentation/query/writing_functions.html
    websites/staging/jena/trunk/content/documentation/query/writing_propfuncs.html
    websites/staging/jena/trunk/content/documentation/rdf/datasets.html
    websites/staging/jena/trunk/content/documentation/rdf/index.html
    websites/staging/jena/trunk/content/documentation/rdfconnection/index.html
    websites/staging/jena/trunk/content/documentation/sdb/commands.html
    websites/staging/jena/trunk/content/documentation/sdb/configuration.html
    websites/staging/jena/trunk/content/documentation/sdb/dataset_description.html
    websites/staging/jena/trunk/content/documentation/sdb/db_notes.html
    websites/staging/jena/trunk/content/documentation/sdb/javaapi.html
    websites/staging/jena/trunk/content/documentation/sdb/loading_performance.html
    websites/staging/jena/trunk/content/documentation/serving_data/index.html
    websites/staging/jena/trunk/content/documentation/tdb/architecture.html
    websites/staging/jena/trunk/content/documentation/tdb/commands.html
    websites/staging/jena/trunk/content/documentation/tdb/configuration.html
    websites/staging/jena/trunk/content/documentation/tdb/datasets.html
    websites/staging/jena/trunk/content/documentation/tdb/dynamic_datasets.html
    websites/staging/jena/trunk/content/documentation/tdb/optimizer.html
    websites/staging/jena/trunk/content/documentation/tdb/store-parameters.html
    websites/staging/jena/trunk/content/documentation/tdb/tdb_system.html
    websites/staging/jena/trunk/content/documentation/tdb2/tdb2_admin.html
    websites/staging/jena/trunk/content/documentation/tdb2/tdb2_fuseki.html
    websites/staging/jena/trunk/content/documentation/tools/eyeball-manual.html
    websites/staging/jena/trunk/content/documentation/tools/schemagen.html
    websites/staging/jena/trunk/content/documentation/txn/index.html
    websites/staging/jena/trunk/content/documentation/txn/transactions_api.html
    websites/staging/jena/trunk/content/documentation/txn/txn.html
    websites/staging/jena/trunk/content/download/maven.html
    websites/staging/jena/trunk/content/help_and_support/index.html
    websites/staging/jena/trunk/content/tutorials/rdf_api.html
    websites/staging/jena/trunk/content/tutorials/sparql_basic_patterns.html
    websites/staging/jena/trunk/content/tutorials/sparql_query1.html
    websites/staging/jena/trunk/content/tutorials/sparql_union.html

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Oct 23 02:34:02 2017
@@ -1 +1 @@
-1812642
+1812967

Modified: websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html (original)
+++ websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html Mon Oct 23 02:34:02 2017
@@ -560,7 +560,7 @@ appropriate properties:</p>
     <code>ja:likeBuiltinSpec ja:OWL_MEM</code>.</li>
 <li><code>ja:importSource</code>: The value of this optional unique property
     is a <code>ModelSource</code> description which describes where imports are
-    obtained from. A <code>ModelSource</code> is usually of of class <code>ja:ModelSource</code>.</li>
+    obtained from. A <code>ModelSource</code> is usually of class <code>ja:ModelSource</code>.</li>
 <li><code>ja:documentManager</code>: This value of this optional unique
     property is a DocumentManager specification. If absent, the default
     document manager is used.</li>

Modified: websites/staging/jena/trunk/content/documentation/csv/implementation.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/csv/implementation.html (original)
+++ websites/staging/jena/trunk/content/documentation/csv/implementation.html Mon Oct 23 02:34:02 2017
@@ -157,7 +157,7 @@
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h2 id="propertytable-implementations">PropertyTable Implementations<a class="headerlink" href="#propertytable-implementations" title="Permanent link">&para;</a></h2>
-<p>There're 2 implementations for <code>PropertyTable</code>. The pros and cons are summarised in the following table: </p>
+<p>There are 2 implementations for <code>PropertyTable</code>. The pros and cons are summarised in the following table: </p>
 <table class="table">
 <thead>
 <tr>

Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html Mon Oct 23 02:34:02 2017
@@ -290,7 +290,7 @@ web application and the additional class
 single configuration file, will still work.  It is less flexible
 (you can't restart these services after stopping them in a running server)
 and user should plan to migrate to the <a href="./fuseki-layout.html">new layout</a>.</p>
-<p>To convert a Fuseki 1 configuration setup to Fuseki 2 style, move each data service assembler and put in it's own file under <code>FUSEKI_BASE/configuration/</code></p>
+<p>To convert a Fuseki 1 configuration setup to Fuseki 2 style, move each data service assembler and put in its own file under <code>FUSEKI_BASE/configuration/</code></p>
   </div>
 </div>
 

Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-data-services.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-data-services.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-data-services.html Mon Oct 23 02:34:02 2017
@@ -163,7 +163,7 @@ SPARQL update and file upload.</p>
   Datasets and services
   Admin</p>
 <h2 id="sparql-protocol">SPARQL Protocol<a class="headerlink" href="#sparql-protocol" title="Permanent link">&para;</a></h2>
-<p>Queyr
+<p>Query
 update
 GSP including direct naming for GSP</p>
 <p>in addition:</p>

Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-embedded.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-embedded.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-embedded.html Mon Oct 23 02:34:02 2017
@@ -186,7 +186,7 @@ storage choice. <code>DatasetFactory.cre
 
 <p>then the application can modify the dataset:</p>
 <div class="codehilite"><pre><span class="c1">// Add some data while live.</span>
-<span class="c1">// Write trasnaction.</span>
+<span class="c1">// Write transaction.</span>
 <span class="n">Txn</span><span class="p">.</span><span class="n">execWrite</span><span class="p">(</span><span class="n">dsg</span><span class="p">,</span> <span class="p">()</span><span class="o">-&gt;</span><span class="n">RDFDataMgr</span><span class="p">.</span><span class="n">read</span><span class="p">(</span><span class="n">dsg</span><span class="p">,</span> <span class="s">&quot;D.trig&quot;</span><span class="p">))</span> <span class="p">;</span>
 </pre></div>
 
@@ -216,10 +216,10 @@ a transaction.</p>
 </pre></div>
 
 
-<p>This brings in enough dependencies to run Fuseki. Applicartion writers are strongly
-encouraged to use a dependency manager because the numbe rof Jetty and other dependencies
+<p>This brings in enough dependencies to run Fuseki. Application writers are strongly
+encouraged to use a dependency manager because the number of Jetty and other dependencies
 is quite large and difficult to set manually.</p>
-<p>This dependency does not include a logging setting. Fusek uses <a href="http://slf4j.org/">slf4j</a>.
+<p>This dependency does not include a logging setting. Fuseki uses <a href="http://slf4j.org/">slf4j</a>.
 See section "<a href="#logging">Logging</a>" for details.</p>
 <p>If the application wishes to use a dataset with a <a href="http://jena.apache.org/documentation/query/text-query.html">text-index</a>
 then the application wil also need to include jena-text in its dependencies.</p>

Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-logging.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-logging.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-logging.html Mon Oct 23 02:34:02 2017
@@ -212,7 +212,7 @@ or reverse proxy will log access request
 <li>Use java resource <code>org/apache/jena/fuseki/log4j.properties</code> on the classpath.</li>
 <li>Use a built-in configuration.</li>
 </ul>
-<p>The laststep is a fallback to catch the case where Fuseki has been repackaged
+<p>The last step is a fallback to catch the case where Fuseki has been repackaged
 into a new WAR file and <code>org/apache/jena/fuseki/log4j.properties</code> omitted, or run from
 the base jar.  It is better to include <code>org/apache/jena/fuseki/log4j.properties</code>.</p>
 <p>The preferred customization is to use a custom <code>log4j.properties</code> file in

Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-server-protocol.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-server-protocol.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-server-protocol.html Mon Oct 23 02:34:02 2017
@@ -324,7 +324,7 @@ in the container, via <code>GET</code>,
 <blockquote>
 <p><em>@@ May add server-managed templates</em></p>
 </blockquote>
-<p>A dataset set can be added to a running server. There ae several methods
+<p>A dataset set can be added to a running server. There are several methods
 for doing this: </p>
 <ul>
 <li>Post the assembler file</li>
@@ -363,7 +363,7 @@ the following parameters (query string o
 <h4 id="assembler-example">Assembler example<a class="headerlink" href="#assembler-example" title="Permanent link">&para;</a></h4>
 <p>The assembler description contains data and service.  It can be sent by posting the assembler RDF graph
 in any RDF format or by posting from an HTML form (the syntax must be Turtle).</p>
-<p>The assembler file is stored by the server will be used on restart or when makign the datsset active again.</p>
+<p>The assembler file is stored by the server will be used on restart or when making the dataset active again.</p>
 <blockquote>
 <p><em>@@</em></p>
 </blockquote>
@@ -402,8 +402,8 @@ useful for managing the files externally
 <p>The returned JOSN object is <code>{ backups: [ ... ] }</code> where the <code>[]</code> array is
 a list of file names.</p>
 <h2 id="tasks">Tasks<a class="headerlink" href="#tasks" title="Permanent link">&para;</a></h2>
-<p>Some operations cause a backgrond task to be executed, backup is an example.
-The result of such operations includes a json object with teh task id and
+<p>Some operations cause a background task to be executed, backup is an example.
+The result of such operations includes a json object with the task id and
 also a <code>Location:</code> header with the URL of the task created.</p>
 <p>The progress of the task can be monitored with HTTP GET operations:</p>
 <p>Pattern: <code>/$/tasks</code> &ndash; All asynchronous tasks.<br/>

Modified: websites/staging/jena/trunk/content/documentation/fuseki2/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/index.html Mon Oct 23 02:34:02 2017
@@ -246,13 +246,13 @@ preference to using any older versions o
 <p>Previous Apache Jena releases can be found in the Apache archive area
 at <a href="http://archive.apache.org/dist/jena/">http://archive.apache.org/dist/jena</a></p>
 <h3 id="development-builds">Development Builds<a class="headerlink" href="#development-builds" title="Permanent link">&para;</a></h3>
-<p>Regular developement builds of all of Jena are available (these are not
+<p>Regular development builds of all of Jena are available (these are not
 formal releases) from the
 <a href="https://repository.apache.org/snapshots/org/apache/jena">Apache snapshots maven repository</a>.
 This includes packaged builds of Fuseki.</p>
 <h2 id="getting-started-with-fuseki">Getting Started With Fuseki<a class="headerlink" href="#getting-started-with-fuseki" title="Permanent link">&para;</a></h2>
 <p>The <a href="fuseki-quick-start.html">quick start</a> section serves as a basic
-guide to getting a Fuskei server running on your local machine.  </p>
+guide to getting a Fuseki server running on your local machine.  </p>
 <p>See <a href="fuseki-run.html">all the ways to run Fuseki</a> for complete coverage of all the
 deployment methods for Fuseki.</p>
 <h2 id="how-to-contribute">How to Contribute<a class="headerlink" href="#how-to-contribute" title="Permanent link">&para;</a></h2>

Modified: websites/staging/jena/trunk/content/documentation/hadoop/common.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/hadoop/common.html (original)
+++ websites/staging/jena/trunk/content/documentation/hadoop/common.html Mon Oct 23 02:34:02 2017
@@ -160,7 +160,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p>Currently we represent the three main RDF primitives - Nodes, Triples and Quads - though in future a wider range of primitives may be supported if we receive contributions to implement them.</p>
 <h1 id="rdf-primitives">RDF Primitives<a class="headerlink" href="#rdf-primitives" title="Permanent link">&para;</a></h1>
 <h2 id="nodes">Nodes<a class="headerlink" href="#nodes" title="Permanent link">&para;</a></h2>
-<p>The <code>Writable</code> type for nodes is predictably enough called <code>NodeWritable</code> and it implements the <code>WritableComparable</code> interface which means it can be used as both a key and/or value in Map/Reduce.  In standard Hadoop style a <code>get()</code> method returns the actual value as a Jena <code>Node</code> instance while a corresponding <code>set()</code> method allows the value to be set.  Coveying <code>null</code> values is acceptable and fully supported.</p>
+<p>The <code>Writable</code> type for nodes is predictably enough called <code>NodeWritable</code> and it implements the <code>WritableComparable</code> interface which means it can be used as both a key and/or value in Map/Reduce.  In standard Hadoop style a <code>get()</code> method returns the actual value as a Jena <code>Node</code> instance while a corresponding <code>set()</code> method allows the value to be set.  Conveying <code>null</code> values is acceptable and fully supported.</p>
 <p>Note that nodes are lazily converted to and from the underlying binary representation so there is minimal overhead if you create a <code>NodeWritable</code> instance that does not actually ever get read/written.</p>
 <p><code>NodeWritable</code> supports and automatically registers itself for Hadoop's <a href="https://hadoop.apache.org/docs/stable/api/org/apache/hadoop/io/WritableComparator.html"><code>WritableComparator</code></a> mechanism which allows it to provide high efficiency binary comparisons on nodes which helps reduce phases run faster by avoiding unnecessary deserialisation into POJOs.</p>
 <p>However the downside of this is that the sort order for nodes may not be as natural as the sort order using POJOs or when sorting with SPARQL.  Ultimately this is a performance trade off and in our experiments the benefits far outweigh the lack of a more natural sort order.</p>

Modified: websites/staging/jena/trunk/content/documentation/inference/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/inference/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/inference/index.html Mon Oct 23 02:34:02 2017
@@ -1216,7 +1216,7 @@ configuration still leaves something to
 </table>
 <p>As we gain experience with the ways in which OWL is used and the capabilities
   of the rule-based approach we imagine useful subsets of functionality emerging
-  - like that that supported by the RDFS reasoner in the form of the level settings.</p>
+  - like that supported by the RDFS reasoner in the form of the level settings.</p>
 <p>[<a href="#owl">OWL index</a>] [<a href="#index">main index</a>]</p></p>
 <h3 id="owl-example"><a name="OWLexamples"></a>OWL Example<a class="headerlink" href="#owl-example" title="Permanent link">&para;</a></h3>
 <p><p>As an example of using the OWL inference support, consider the sample schema
@@ -1225,7 +1225,7 @@ configuration still leaves something to
 <p>The schema file shows a simple, artificial ontology concerning computers which
   defines a GamingComputer as a Computer which includes at least one bundle of
   type GameBundle and a component with the value gamingGraphics. </p>
-<p>The data file shows information on serveral hypothetical computer configurations
+<p>The data file shows information on several hypothetical computer configurations
   including two different descriptions of the configurations &quot;whiteBoxZX&quot;
   and &quot;<code>bigName42</code>&quot;.</p>
 <p>We can create an instance of the OWL reasoner, specialized to the demo schema
@@ -1276,9 +1276,9 @@ configuration still leaves something to
   property inheritance (<code>eg:hasComponent eg:gameGraphics</code> derives from
   <code>hasGraphics</code> being a subProperty of <code>hasComponent</code>) and
   cardinality reasoning (it is the sameAs <code>eg:unknownMB</code> because computers
-  are defined to have only one motherboard and the two diffferent descriptions
+  are defined to have only one motherboard and the two different descriptions
   of <code>whileBoxZX</code> use these two different terms for the mother board).<i>
-  </i>The anonymous rdf:type statement referencesthe <code>&quot;hasValue(eg:hasComponent,
+  </i>The anonymous rdf:type statement references the <code>&quot;hasValue(eg:hasComponent,
   eg:gamingGraphics)&quot; </code>restriction mentioned in the definition of GamingComputer.</p>
 
 <p>A second, typical operation is instance recognition. Testing if an individual
@@ -1299,7 +1299,7 @@ configuration still leaves something to
 </pre></div>
 
 
-<p> Which gnerates the output:</p>
+<p> Which generates the output:</p>
 
 <pre>  <i>White box recognized as gaming computer</i></pre>
 
@@ -1375,7 +1375,7 @@ class B = cardinality(P,1)</pre>
   a separation of direct and indirect relations for transitive properties such
   as subClassOf. The current implementation of the full and mini OWL reasoner
   fails to do this and the direct forms of the queries will fail. The OWL Micro
-  reasoner, which is but a small extension of RDFS, does suppor the direct queries.</p>
+  reasoner, which is but a small extension of RDFS, does support the direct queries.</p>
 <p>This does not affect querying though the Ontology API, which works around this
   limitation. It only affects direct RDF accesses to the inference model.</p></p>
 <h4 id="performance">Performance<a class="headerlink" href="#performance" title="Permanent link">&para;</a></h4>
@@ -1402,7 +1402,7 @@ class B = cardinality(P,1)</pre>
 <h4 id="incompleteness">Incompleteness<a class="headerlink" href="#incompleteness" title="Permanent link">&para;</a></h4>
 <p><p>The rule based approach cannot offer a complete solution for OWL/Lite, let
   alone the OWL/Full fragment corresponding to the OWL/Lite constructs. In addition
-  the current implementation is still under development and may well have ommisions
+  the current implementation is still under development and may well have ommissions
   and oversights. We intend that the reasoner should be sound (all inferred triples
   should be valid) but not complete. </p></p>
 <p>[<a href="#owl">OWL index</a>] [<a href="#index">main index</a>]</p>
@@ -1904,7 +1904,7 @@ floating point or XSDDateTime).</div>
       it will bind the first n capture groups to the arguments ?m1 to ?mn.
       The regular expression pattern syntax is that provided by java.util.regex.
       Note that the capture groups are numbered from 1 and the first capture group
-      will be bound to ?m1, we ignore the implicit capature group 0 which corresponds to
+      will be bound to ?m1, we ignore the implicit capture group 0 which corresponds to
       the entire matched string. So for example
       <pre>regexp('foo bar', '(.</em>) (.<em>)', ?m1, ?m2)</pre>
       will bind <code>m1</code> to <code>"foo"</code> and <code>m2</code> to <code>"bar"</code>.</div>
@@ -1987,7 +1987,7 @@ floating point or XSDDateTime).</div>
     <td width="59%">
       <div align="left">Binds ?val to the ?index'th entry
 in the RDF list ?list. If there is no such entry the variable will be unbound
-and the call will fail. Only useable in rule bodies.</div>
+and the call will fail. Only usable in rule bodies.</div>
     </td>
   </tr>
   <tr>
@@ -2125,12 +2125,12 @@ while (i.hasNext()) {
 <p>[<a href="#rules">rule index</a>] [<a href="#index">main index</a>]</p></p>
 <h3 id="combining-rdfsowl-with-custom-rules"><a name="RDFSPlusRules"></a>Combining RDFS/OWL with custom rules<a class="headerlink" href="#combining-rdfsowl-with-custom-rules" title="Permanent link">&para;</a></h3>
 <p><p>Sometimes one wishes to write generic inference rules but combine them
- with some RDFS or OWL infernece. With the current Jena architecture limited forms of this
+ with some RDFS or OWL inference. With the current Jena architecture limited forms of this
  is possible but you need to be aware of the limitations.</p>
 <p>There are two ways of achieving this sort of configuration within Jena (not
  counting using an external engine that already supports such a combination).</p>
 <p>Firstly, it is possible to cascade reasoners, i.e. to construct one InfModel
- using another InfModel as the base data. The strength of this appoach is that
+ using another InfModel as the base data. The strength of this approach is that
  the two inference processes are separate and so can be of different sorts. For
  example one could create a GenericRuleReasoner whose base model is an external
  OWL reasoner. The chief weakness of the approach is that it is "layered" - the
@@ -2140,7 +2140,7 @@ while (i.hasNext()) {
  is performance. A query to an InfModel is generally expensive and involves lots
  of queries to the data. The outer InfModel in our layered case will
  typically issue a lot of queries to the inner model, each of which may
- trigger more inferenece. If the inner model caches all of its inferences
+ trigger more inference. If the inner model caches all of its inferences
  (e.g. a forward rule engine) then there may not be very much redundancy there but
  if not then performance can suffer dramatically. </p>
 <p>Secondly, one can create a single GenericRuleReasoner whose rules combine
@@ -2175,7 +2175,7 @@ while (i.hasNext()) {
 
 <p>
  A simple example of this is that the <em>interesting</em> bits of RDFS
- can be captured by enabled TranstiveClosureCaching and including just the
+ can be captured by enabled TransitiveClosureCaching and including just the
  four core rules:</p>
 
 <pre>

Modified: websites/staging/jena/trunk/content/documentation/io/rdf-input.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/io/rdf-input.html (original)
+++ websites/staging/jena/trunk/content/documentation/io/rdf-input.html Mon Oct 23 02:34:02 2017
@@ -336,7 +336,7 @@ add data into an existing model or datas
 <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/riot/RDFParser.html">the javadoc for all details</a>.</p>
 <p>For example, to read Trig data, and set the error handler specially,</p>
 <div class="codehilite"><pre>    <span class="o">//</span> <span class="n">The</span> <span class="n">parsers</span> <span class="n">will</span> <span class="n">do</span> <span class="n">the</span> <span class="n">necessary</span> <span class="n">character</span> <span class="n">set</span> <span class="n">conversion</span><span class="p">.</span>  
-    <span class="k">try</span> <span class="p">(</span><span class="n">InputStream</span> <span class="n">in</span> <span class="p">=</span> <span class="n">new</span> <span class="n">FileInputStream</span><span class="p">(</span>&quot;<span class="n">data</span><span class="p">.</span><span class="n">some</span><span class="p">.</span><span class="n">unusal</span><span class="p">.</span><span class="n">extension</span>&quot;<span class="p">))</span> <span class="p">{</span>
+    <span class="k">try</span> <span class="p">(</span><span class="n">InputStream</span> <span class="n">in</span> <span class="p">=</span> <span class="n">new</span> <span class="n">FileInputStream</span><span class="p">(</span>&quot;<span class="n">data</span><span class="p">.</span><span class="n">some</span><span class="p">.</span><span class="n">unusual</span><span class="p">.</span><span class="n">extension</span>&quot;<span class="p">))</span> <span class="p">{</span>
         <span class="n">RDFParser</span><span class="p">.</span><span class="n">create</span><span class="p">()</span>
             <span class="p">.</span><span class="n">source</span><span class="p">(</span><span class="n">in</span><span class="p">)</span>
             <span class="p">.</span><span class="n">lang</span><span class="p">(</span><span class="n">RDFLanguages</span><span class="p">.</span><span class="n">TRIG</span><span class="p">)</span>
@@ -354,7 +354,7 @@ messages, set this in log4j.properties t
 <p>By default, the <code>RDFDataMgr</code> uses the global <code>StreamManager</code> to open typed
 InputStreams.  This is available to applications via <code>RDFDataMgr.open</code> as well as directly
 using a <code>StreamManager</code>.</p>
-<p>The <code>StreamManager</code> is choosen based on the <code>Context</code> object for the
+<p>The <code>StreamManager</code> is chosen based on the <code>Context</code> object for the
 operation, but normally this defaults to the global <code>Context</code> available via
 <code>Context.get()</code>.  The constant <code>RDFDataMgr.streamManagerSymbol</code>, which is 
 <code>http://jena.apache.org/riot/streamManager</code> is used.</p>
@@ -369,11 +369,11 @@ data:</p>
 <h3 id="configuring-a-streammanager">Configuring a <code>StreamManager</code><a class="headerlink" href="#configuring-a-streammanager" title="Permanent link">&para;</a></h3>
 <p>The <code>StreamManager</code> can be reconfigured with different places to look for
 files.  The default configuration used for the global <code>StreamManager</code> is
-a file access class, wihere the current directory is that of the java
+a file access class, where the current directory is that of the java
 process, a URL accessor for reading from the web, and a
 class loader-based accessor.  Different setups can be built and used
 either as the global set up, </p>
-<p>There is also a <code>LocationMapper</code> for rewiting file names and URLs before
+<p>There is also a <code>LocationMapper</code> for rewriting file names and URLs before
 use to allow placing known names in different places (e.g. having local
 copies of import http resources).</p>
 <h3 id="configuring-a-locationmapper">Configuring a <code>LocationMapper</code><a class="headerlink" href="#configuring-a-locationmapper" title="Permanent link">&para;</a></h3>

Modified: websites/staging/jena/trunk/content/documentation/io/rdf-output.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/io/rdf-output.html (original)
+++ websites/staging/jena/trunk/content/documentation/io/rdf-output.html Mon Oct 23 02:34:02 2017
@@ -213,7 +213,7 @@ are available as part of the standard se
 <p>In addition, there are variants of Trutle, TriG for pretty printing, 
 streamed output and flat output.  RDF/XML has variants for pretty printing 
 and plain output.  Jena RIOT uses <code>org.apache.jena.riot.RDFFormat</code> as a way
-to identfy the language and variant to be written.  The class contains constants
+to identify the language and variant to be written.  The class contains constants
 for the standard supported formats.</p>
 <p>Note:</p>
 <ul>
@@ -340,7 +340,7 @@ data with the same subject in the same g
 All the properties for a given subject are sorted 
 into a predefined order. RDF lists are printed as
 <code>(...)</code> and <code>[...]</code> is used for blank nodes where possible.  </p>
-<p>The analysis for determing what can be pretty printed requires
+<p>The analysis for determining what can be pretty printed requires
 temporary datastructures and also a scan of the whole graph before
 writing begins.  Therefore, pretty printed formats are not suitable
 for writing persistent graphs and datasets.</p>
@@ -615,7 +615,7 @@ compared to the text-based standardised
 </tbody>
 </table>
 <p><code>RDFTHRIFT_VALUES</code> is a variant where numeric values are written as values,
-not as lexcial format and datatype.  See the 
+not as lexical format and datatype.  See the 
 <a href="http://afs.github.io/rdf-thrift">description of RDF Thrift</a>
 for dsicussion.</p>
 <h3 id="rdfxml">RDF/XML<a class="headerlink" href="#rdfxml" title="Permanent link">&para;</a></h3>
@@ -670,7 +670,7 @@ while the jena writer writer name defaul
 </pre></div>
 
 
-<p>Additionaly, a single model can be written in a dataset format - it becomes
+<p>Additionally, a single model can be written in a dataset format - it becomes
 the default graph of the dataset.</p>
 <div class="codehilite"><pre><span class="n">Model</span> <span class="n">m</span> <span class="p">=</span> 
 <span class="n">RDFDataMgr</span><span class="p">.</span><span class="n">write</span><span class="p">(</span><span class="n">System</span><span class="p">.</span><span class="n">out</span><span class="p">,</span> <span class="n">m</span><span class="p">,</span> <span class="n">Lang</span><span class="p">.</span><span class="n">TRIG</span><span class="p">)</span> <span class="p">;</span>
@@ -703,8 +703,8 @@ the default graph of the dataset.</p>
 to manage the character encoding using UTF-8.  Using <code>java.io.Writer</code> 
 does not allow this; on platforms such as MS Windows, the default
 configuration of a <code>Writer</code> is not suitable for Turtle because
-the characte set is the platform default, and not UTF-8.
-The only use of wirters that is useful is using <code>java.io.StringWriter</code>.</p>
+the character set is the platform default, and not UTF-8.
+The only use of writers that is useful is using <code>java.io.StringWriter</code>.</p>
   </div>
 </div>
 

Modified: websites/staging/jena/trunk/content/documentation/io/rdfxml_howto.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/io/rdfxml_howto.html (original)
+++ websites/staging/jena/trunk/content/documentation/io/rdfxml_howto.html Mon Oct 23 02:34:02 2017
@@ -738,7 +738,7 @@ RDF/XML with resources of these types at
  
 As an example,</p>
 <div class="codehilite"><pre><span class="n">RDFWriter</span> <span class="n">w</span> <span class="p">=</span> <span class="n">m</span><span class="p">.</span><span class="n">getWriter</span><span class="p">(</span>&quot;<span class="n">RDF</span><span class="o">/</span><span class="n">XML</span><span class="o">-</span><span class="n">ABBREV</span>&quot;<span class="p">);</span>
-<span class="n">w</span><span class="p">.</span><span class="n">setProperty</span><span class="p">(</span>&quot;<span class="n">attribtueQuoteChar</span>&quot;<span class="p">,</span>&quot;<span class="s">&#39;</span><span class="err">&quot;);</span>
+<span class="n">w</span><span class="p">.</span><span class="n">setProperty</span><span class="p">(</span>&quot;<span class="n">attributeQuoteChar</span>&quot;<span class="p">,</span>&quot;<span class="s">&#39;</span><span class="err">&quot;);</span>
 <span class="n">w</span><span class="p">.</span><span class="n">setProperty</span><span class="p">(</span>&quot;<span class="n">showXMLDeclaration</span>&quot;<span class="p">,</span>&quot;<span class="n">true</span>&quot;<span class="p">);</span>
 <span class="n">w</span><span class="p">.</span><span class="n">setProperty</span><span class="p">(</span>&quot;<span class="n">tab</span>&quot;<span class="p">,</span>&quot;1&quot;<span class="p">);</span>
 <span class="n">w</span><span class="p">.</span><span class="n">setProperty</span><span class="p">(</span>&quot;<span class="n">blockRules</span>&quot;<span class="p">,</span>

Modified: websites/staging/jena/trunk/content/documentation/jdbc/custom_driver.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/jdbc/custom_driver.html (original)
+++ websites/staging/jena/trunk/content/documentation/jdbc/custom_driver.html Mon Oct 23 02:34:02 2017
@@ -184,7 +184,7 @@ need to deviate from the default behavio
 <p>If you wish to go down this route then we recommend looking at the source for the built in implementations
 to guide you in this.  It may be easier to extend one of the built-in implementations rather than writing
 an entire custom implementation yourself.</p>
-<p>Note that custom implementations may also require you to implement custom <code>JenaStatement</code> and <code>JenaPreparedSatement</code>
+<p>Note that custom implementations may also require you to implement custom <code>JenaStatement</code> and <code>JenaPreparedStatement</code>
 implementations.</p>
 <h2 id="testing-your-driver">Testing your Driver<a class="headerlink" href="#testing-your-driver" title="Permanent link">&para;</a></h2>
 <p>To aid testing your custom driver the <code>jena-jdbc-core</code> module provides a number of abstract test classes which

Modified: websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html (original)
+++ websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html Mon Oct 23 02:34:02 2017
@@ -176,7 +176,7 @@ org.apache.jena.</code> will cover the m
 <h3 id="assemblers">Assemblers<a class="headerlink" href="#assemblers" title="Permanent link">&para;</a></h3>
 <p>Migration support is provided by mapping <code>ja:loadClass</code> names beginning
 <code>com.hp.hpl.jena</code> internally to <code>org.apache.jena</code>. A warning is logged.</p>
-<p>Any assmeeberlers that </p>
+<p>Any assemblers that </p>
 <h3 id="logging">Logging<a class="headerlink" href="#logging" title="Permanent link">&para;</a></h3>
 <p>This will also affect logging: logger names reflect the java class naming
 so loggers for <code>com.hp.hpl.jena</code> become <code>org.apache.jena</code></p>
@@ -226,7 +226,7 @@ recommended that data is reloaded at a c
 <p>Data that does use explicit <code>xsd:string</code> must be reloaded.</p>
 <h2 id="permissions-changes">Security package renamed to Permissions<a class="headerlink" href="#permissions-changes" title="Permanent link">&para;</a></h2>
 <p>Jena Security has been renamed Jena Permissions and the Maven <em>artifact id</em> has been changed to <em>jena-permissions</em> to reflect this change.</p>
-<p>Shim code that was introduced to map Jena classes to security classes has been removed.  This change requires changes to SecurtyEvaluator implementations.  More detals are available at the <a href="permissions/migration2To3.html">Permissions migration documentation</a>.</p>
+<p>Shim code that was introduced to map Jena classes to security classes has been removed.  This change requires changes to SecurityEvaluator implementations.  More details are available at the <a href="permissions/migration2To3.html">Permissions migration documentation</a>.</p>
 <h2 id="other">Other<a class="headerlink" href="#other" title="Permanent link">&para;</a></h2>
 <p>The <code>GraphStore</code> interface has been removed.</p>
 <p><code>ModelFactory.createFileModelMaker</code> has been removed.</p>

Modified: websites/staging/jena/trunk/content/documentation/notes/datasetgraph.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/notes/datasetgraph.html (original)
+++ websites/staging/jena/trunk/content/documentation/notes/datasetgraph.html Mon Oct 23 02:34:02 2017
@@ -192,12 +192,12 @@ of implementation and adding specific fu
 <p>There are two markers for transaction features supported.</p>
 <p>If <code>begin</code>, <code>commit</code> and <code>end</code> are supported (which is normally the case)
 <code>supportsTransactions</code> returns true.</p>
-<p>If, further, <code>abort</code> is suported, then <code>supportsTransactionAbort</code> is true.</p>
+<p>If, further, <code>abort</code> is supported, then <code>supportsTransactionAbort</code> is true.</p>
 <h3 id="general-hierarchy">General hierarchy<a class="headerlink" href="#general-hierarchy" title="Permanent link">&para;</a></h3>
 <p><strong>DatasetGraphBase</strong></p>
 <p>This provides some basic machinery and provides implementations of
 operations that have alternative styles.  It converts <code>add(G,S,P,O)</code> to
-<code>add(quad)</code> and <code>delete(G,S,P,O)</code> to <code>delele(quad)</code> and converts
+<code>add(quad)</code> and <code>delete(G,S,P,O)</code> to <code>delete(quad)</code> and converts
 <code>find(quad)</code> to <code>find(G,S,P,O)</code>.</p>
 <p>It provides basic implementations of <code>deleteAny(?,?,?,?)</code> and <code>clear()</code>.</p>
 <p>It provides a Lock (LockMRSW) and the Context.</p>
@@ -256,7 +256,7 @@ modifying them via the DatasetGraph inte
 <p>A small class that provides the "get a graph" operations over a
 <code>DatasetGraph</code> using <code>GraphView</code>.</p>
 <p>Not used because subclasses usually want to inherit from a different part
-fo the hierarchy but the idea of implementating <code>getDefaultGraph()</code> and
+fo the hierarchy but the idea of implementing <code>getDefaultGraph()</code> and
 <code>getGraph(Node)</code> as calls to <code>GraphView</code> is used elsewhere.</p>
 <p>Do not use with an implementations that store using graph
 (e.g. <code>DatasetGraphMap</code>, <code>DatasetGraphMapLink</code>) because it goes into an
@@ -288,8 +288,8 @@ works over systems that do not themselve
 replay abort (do the adds and deletes in reverse operation, reverse order)
 but this is partial. It does not protect against the DatasetGraph
 implementation throwing exceptions nor JVM or machine crash (if any
-persistence). It still needs MRSW to achive isolation.</p>
-<p>Read-commited needs synchronization safe datastructures -including
+persistence). It still needs MRSW to archive isolation.</p>
+<p>Read-committed needs synchronization safe datastructures -including
 co-ordinated changes to several place at once (ConcurrentHashMap isn't
 enough - need to update 2 or more ConcurrentHashMaps together).</p>
 <h3 id="tdb">TDB<a class="headerlink" href="#tdb" title="Permanent link">&para;</a></h3>

Modified: websites/staging/jena/trunk/content/documentation/notes/jena-internals.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/notes/jena-internals.html (original)
+++ websites/staging/jena/trunk/content/documentation/notes/jena-internals.html Mon Oct 23 02:34:02 2017
@@ -238,7 +238,7 @@ implementation
     personalities, for example, may implement interfaces in different
     ways, or not implement some at all.</li>
 <li>enhanced nodes wrap information in the graph, but keep no
-    independant state; they may be discarded and regenerated at whim.</li>
+    independent state; they may be discarded and regenerated at whim.</li>
 </ul>
 <h3 id="how-an-enhanced-node-is-created">How an enhanced node is created<a class="headerlink" href="#how-an-enhanced-node-is-created" title="Permanent link">&para;</a></h3>
 <h4 id="creation-from-another-enhanced-node">Creation from another enhanced node<a class="headerlink" href="#creation-from-another-enhanced-node" title="Permanent link">&para;</a></h4>
@@ -336,13 +336,13 @@ is thus inappropriate for comparing reif
 The goal of reification support in the Jena 2 implementation are:</p>
 <ul>
 <li>to conform to the revised RDF specifications</li>
-<li>to maintain the expections of Jena 1; <em>ie</em> they should still be
+<li>to maintain the expectations of Jena 1; <em>ie</em> they should still be
     able to reify everything without worrying about triple bloat if
     they want to</li>
 <li>as far as is consistent with 2, to not break existing code, or
     at least make it easy to transition old code to Jena 2.</li>
 <li>to enable round tripping through RDF/XML and other RDF
-    representation langauges</li>
+    representation languages</li>
 <li>enable a complete standard compliant implementation, but not
     necessarily as default</li>
 </ul>
@@ -473,7 +473,7 @@ it is expected to store only the impleme
 the <em>Statement</em>.</p>
 <p><em>createReifiedStatement</em> is expected to bypass the construction and
 detection of the quad components, so that in the "usual case" they
-will never come into existance.</p>
+will never come into existence.</p>
 <h2 id="the-reification-spi">The Reification SPI<a class="headerlink" href="#the-reification-spi" title="Permanent link">&para;</a></h2>
 <h3 id="introduction_1">Introduction<a class="headerlink" href="#introduction_1" title="Permanent link">&para;</a></h3>
 <p>This document describes the reification SPI, the mechanisms by
@@ -492,12 +492,12 @@ visible through the graph.</p>
 This is useful for internal graphs that are not exposed as models.
 So there are three kinds of <code>Graph</code>:</p>
 <p>Graphs that do no reification;
-Graphs that only do explicit reficiation;
+Graphs that only do explicit reification;
 Graphs that do implicit reification.</p>
 <h3 id="graph-operations-for-reification">Graph operations for reification<a class="headerlink" href="#graph-operations-for-reification" title="Permanent link">&para;</a></h3>
 <p>The primary reification operation on graphs is to extract their
 <code>Reifier</code> instance. Handing reification off to a different class
-allows reification to be handled independantly of other Graph
+allows reification to be handled independently of other Graph
 issues, eg query handling, bulk update.</p>
 <h4 id="graphgetreifier-62-reifier">Graph.getReifier() -> Reifier<a class="headerlink" href="#graphgetreifier-62-reifier" title="Permanent link">&para;</a></h4>
 <p>Returns the <code>Reifier</code> for this <code>Graph</code>. Each graph has a single
@@ -574,7 +574,7 @@ added to it and have the reifier handle
 this case, the graph's <code>add(t)</code> should call <code>handledAdd(t)</code> and
 only proceed with its add if the result is <code>false</code>.
 A graph that does not use <code>handledAdd()</code> [and <code>handledDelete()</code>]
-can only use the explict reification supplied by its reifier.</p>
+can only use the explicit reification supplied by its reifier.</p>
 <h4 id="handledremove-triple-t">handledRemove( Triple t )<a class="headerlink" href="#handledremove-triple-t" title="Permanent link">&para;</a></h4>
 <p>As for <code>handledAdd(t)</code>, but applied to <code>delete</code>.</p>
 <h3 id="simplereifier">SimpleReifier<a class="headerlink" href="#simplereifier" title="Permanent link">&para;</a></h3>

Modified: websites/staging/jena/trunk/content/documentation/notes/jena-repack.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/notes/jena-repack.html (original)
+++ websites/staging/jena/trunk/content/documentation/notes/jena-repack.html Mon Oct 23 02:34:02 2017
@@ -156,7 +156,7 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>Apache Jena initalizes uses Java's
+<p>Apache Jena initializes uses Java's
 <a href="https://docs.oracle.com/javase/8/docs/api/java/util/ServiceLoader.html">ServiceLoader</a>
 mechanism to locate initialization steps. The 
 documentation for process in Jena is <a href="system-initialization.html">available here</a>.</p>

Modified: websites/staging/jena/trunk/content/documentation/notes/reification_previous.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/notes/reification_previous.html (original)
+++ websites/staging/jena/trunk/content/documentation/notes/reification_previous.html Mon Oct 23 02:34:02 2017
@@ -159,7 +159,7 @@ h2:hover > .headerlink, h3:hover > .head
 <h2 id="reification-styles">Reification styles<a class="headerlink" href="#reification-styles" title="Permanent link">&para;</a></h2>
 <p>Prior to version 2.10.0 of Jena, there were 3 styles of reification, 
 "standard", "minimal" and "convenient".  As of 2.10.0 and later, only 
-what was previosuly the "standard" style is supported.</p>
+what was previously the "standard" style is supported.</p>
 <p>By default and as you might expect, Jena models allow reification
 quads to be manifested as <code>ReifiedStatement</code>s. Similarly,
 explicitly created <code>ReifiedStatement</code>s are visible as statement

Modified: websites/staging/jena/trunk/content/documentation/notes/sse.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/notes/sse.html (original)
+++ websites/staging/jena/trunk/content/documentation/notes/sse.html Mon Oct 23 02:34:02 2017
@@ -221,7 +221,7 @@ structure, and not express the operation
 structures that operational meaning don't enter the picture. There are
 no operations, no <em>push</em>, <em>pop</em> or <em>peek</em>.</p>
 <p>Note that this is to <em>express</em> a data structure, not <em>encode</em> or
-<em>repressent</em> it. By <em>express</em> we mean communicate it, between people or
+<em>represent</em> it. By <em>express</em> we mean communicate it, between people or
 between cooperating machines. The structures are not completely
 self-representing. But we do discuss a way to express in RDF that does
 give a self-describing nature through the use of tagged structures.</p>
@@ -279,7 +279,7 @@ SPARQL algebra for the query in SSE form
 <thead>
 <tr>
 <th>Example</th>
-<th>Explaination</th>
+<th>Explanation</th>
 </tr>
 </thead>
 <tbody>
@@ -488,7 +488,7 @@ namespace).</p>
 IRIs and literals are the same.: to produce Turtle (outline):</p>
 <ol>
 <li>Replace symbols by IRIs: prepend a common URI and %-encode any
-    characters necesary.</li>
+    characters necessary.</li>
 <li>Replace variables by IRIs: prepend a common URI.</li>
 <li>Move prefixes to be <code>@prefix</code> directives.</li>
 <li>Put a dot at the end of the file.</li>
@@ -549,7 +549,7 @@ inline dataset and a query of</p>
 
 
 <p>The tag <code>graph</code> is used twice, with different meanings. First, for an
-RDF graph, and second in <code>GRAPH</code> SPARQL pattern. In a data structrure,
+RDF graph, and second in <code>GRAPH</code> SPARQL pattern. In a data structure,
 context sorts out the different usages.</p>
 <div class="codehilite"><pre><span class="p">(</span><span class="n">prefix</span> <span class="p">((:</span> <span class="o">&lt;</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">example</span><span class="o">/&gt;</span><span class="p">))</span>
    <span class="p">(</span><span class="n">exec</span>

Modified: websites/staging/jena/trunk/content/documentation/notes/typed-literals.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/notes/typed-literals.html (original)
+++ websites/staging/jena/trunk/content/documentation/notes/typed-literals.html Mon Oct 23 02:34:02 2017
@@ -493,7 +493,7 @@ rational numbers:</p>
 </pre></div>
 
 
-<p>To register and and use this type you simply need the call:</p>
+<p>To register and use this type you simply need the call:</p>
 <div class="codehilite"><pre><span class="n">RDFDatatype</span> <span class="n">rtype</span> <span class="p">=</span> <span class="n">RationalType</span><span class="p">.</span><span class="n">theRationalType</span><span class="p">;</span>
 <span class="n">TypeMapper</span><span class="p">.</span><span class="n">getInstance</span><span class="p">().</span><span class="n">registerDatatype</span><span class="p">(</span><span class="n">rtype</span><span class="p">);</span>
 <span class="p">...</span>

Modified: websites/staging/jena/trunk/content/documentation/ontology/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/ontology/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/ontology/index.html Mon Oct 23 02:34:02 2017
@@ -773,7 +773,7 @@ language. In summary, these variants are
 
 
 <p>You can use any of these methods to load an ontology document. Note
-that we advise that you avoid the the <code>read()</code> variants that accept
+that we advise that you avoid the <code>read()</code> variants that accept
 a <code>java.io.Reader</code> argument when loading XML documents containing
 internationalised character sets, since the handling of character
 encoding by the Reader and by XML parsers is not compatible.</p>
@@ -1712,7 +1712,7 @@ three classes as follows:</p>
 </pre></div>
 
 
-<p>Alternatively, we can build a list one element at at time:</p>
+<p>Alternatively, we can build a list one element at time:</p>
 <div class="codehilite"><pre><span class="n">OntModel</span> <span class="n">m</span> <span class="p">=</span> <span class="n">ModelFactory</span><span class="p">.</span><span class="n">createOntModel</span><span class="p">();</span>
 <span class="n">RDFList</span> <span class="n">cs</span> <span class="p">=</span> <span class="n">m</span><span class="p">.</span><span class="n">createList</span><span class="p">();</span> <span class="o">//</span> <span class="n">Cs</span> <span class="n">is</span> <span class="n">empty</span>
 <span class="n">cs</span> <span class="p">=</span> <span class="n">cs</span><span class="p">.</span><span class="n">cons</span><span class="p">(</span> <span class="n">m</span><span class="p">.</span><span class="n">createClass</span><span class="p">(</span> <span class="n">NS</span> <span class="o">+</span> &quot;<span class="n">c0</span>&quot; <span class="p">)</span> <span class="p">);</span>
@@ -1907,7 +1907,7 @@ returned by the listClasses() iterator i
 reasoner that can infer that any restriction is also be a class,
 since <code>Restriction</code> is a subClassOf <code>Class</code>. This difference can be
 exploited by the programmer: to list classes and restrictions
-separately, perform the <code>listClasses()</code> and <code>listRestictions()</code>
+separately, perform the <code>listClasses()</code> and <code>listRestrictions()</code>
 methods on the base model only, or on a model with no reasoner
 attached.</p>
 <h2 id="instances-or-individuals">Instances or individuals<a class="headerlink" href="#instances-or-individuals" title="Permanent link">&para;</a></h2>

Modified: websites/staging/jena/trunk/content/documentation/permissions/design.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/permissions/design.html (original)
+++ websites/staging/jena/trunk/content/documentation/permissions/design.html Mon Oct 23 02:34:02 2017
@@ -199,7 +199,7 @@ returns <code>false</code>. In general t
 <p>Models and Graphs often return objects from methods. For example the <code>model.createStatement()</code> returns a <code>Statement</code> object. That object holds a reference to the model and performs operations against the model (for example <code>Statement.changeLiteralObject()</code>). Since permissions provides a dynamic wrapper around the base model to create the secured model, returning the model <code>Statement</code> would return an object that no longer has any permissions applied. Therefore the permissions system creates a <code>SecuredStatement</code> that applies permission checks to all operations before calling the base <code>Statement</code> methods.</p>
 <p>All secured objects return secured objects if those objects may read or alter the underlying graph/model.</p>
 <p>All secured objects are defined as interfaces and are returned as dynamic proxies.</p>
-<p>All secured objects have concrete implementations. These implementations must remain concrete to ensure that we handle all cases where returned objects may alter the the underlying graph/model.</p>
+<p>All secured objects have concrete implementations. These implementations must remain concrete to ensure that we handle all cases where returned objects may alter the underlying graph/model.</p>
 <h2 id="secured-listeners">Secured Listeners<a class="headerlink" href="#secured-listeners" title="Permanent link">&para;</a></h2>
 <p>Both the Graph and the Model interfaces provide a listener framework. Listeners are attached to the graph/model and changes to the graph/model are reported to them. In order to ensure that listeners do not leak information, the principal that was active when the listener was attached is preserved in a <code>CachedSecurityEvaluator</code> instance. This security evaluator implementation, wraps the original implementation and retains the current user. Thus when the listener performs the permission checks the original user is used not the current user. This is why the SecurityEvaluator <strong>must</strong> use the <code>principal</code> parameters and not call <code>getPrincipal()</code> directly during evaluation calls.</p>
 <h1 id="proxy-implementation">Proxy Implementation<a class="headerlink" href="#proxy-implementation" title="Permanent link">&para;</a></h1>

Modified: websites/staging/jena/trunk/content/documentation/permissions/evaluator.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/permissions/evaluator.html (original)
+++ websites/staging/jena/trunk/content/documentation/permissions/evaluator.html Mon Oct 23 02:34:02 2017
@@ -160,13 +160,13 @@ h2:hover > .headerlink, h3:hover > .head
 <p>The SecurityEvaluator interface defines the access control operations. It provides the interface between the authentication (answers the question: "who are you?") and the authorization (answers the question: "what can you do?"), as such it provides access to the current principal (user). The javadocs contain detailed requirements for implementations of the SecurityEvaluator interface, short notes are provided below.</p>
 <p><strong>NOTE</strong> The permissions system caches intermediate results and will only call the evaluator if the answer is not already in the cache. There is little or no advantage to implementing caching in the SecurityEvaluator itself.</p>
 <h3 id="actions">Actions<a class="headerlink" href="#actions" title="Permanent link">&para;</a></h3>
-<p>Principals may perform Create, Read, Update or Delete operations on secured resources. These operations are defined in the <code>Action</code> enum in the SecurtyEvaluator interface.</p>
+<p>Principals may perform Create, Read, Update or Delete operations on secured resources. These operations are defined in the <code>Action</code> enum in the SecurityEvaluator interface.</p>
 <h3 id="node">Node<a class="headerlink" href="#node" title="Permanent link">&para;</a></h3>
 <p>The permission system uses the standard Node.ANY to represent a wild-card in a permission check and the standard <code>Triple.ANY</code> to represent a triple with wild-cards in each of the three positions: subject, predicate and object.</p>
 <p>The permission system introduces two new node types <code>SecurityEvaluator.VARIABLE</code>, which represents a variable in a permissions query, and <code>SecurityEvaluator.FUTURE</code>, which represents an anonymous node that will be created in the future.</p>
 <h3 id="evaluator-methods">Evaluator Methods<a class="headerlink" href="#evaluator-methods" title="Permanent link">&para;</a></h3>
 <p>The SecurityEvaluator connects the Jena permissions system with the authentication system used by the application. The SecurityEvaluator must be able to query the authentication system, or its proxy, to determine who the "current user" is. In this context the "current user" is the one making the request. In certain instances (specifically when using listeners on secured graphs and models) the "current user" may not be the user identified by the authentication system at the time of the query.</p>
-<p>The SecurityEvaluator must implement the following methods. Any of these methods may throw an <code>AuthenticationRequriedException</code> if there is no authenticated user.</p>
+<p>The SecurityEvaluator must implement the following methods. Any of these methods may throw an <code>AuthenticationRequiredException</code> if there is no authenticated user.</p>
 <p>Most of these methods have a <code>principal</code> parameter. The value of that parameter is guaranteed to be a value returned from an earlier calls to getPrincipal(). The <code>principal</code> parameter, not the "current user" as identified by <code>getPrincipal()</code>, should be used for the permissions evaluation.</p>
 <p>None of these methods should throw any of the PermissionDeniedException based exceptions. That is handled in a different layer.</p>
 <p>See the <a href="../javadoc/permissions/org/apache/jena/permissions/SecurityEvaluator.html">SecurityEvaluator javadocs</a> for detailed implementation notes.</p>

Modified: websites/staging/jena/trunk/content/documentation/permissions/example.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/permissions/example.html (original)
+++ websites/staging/jena/trunk/content/documentation/permissions/example.html Mon Oct 23 02:34:02 2017
@@ -254,7 +254,7 @@ graph.</p>
 </pre></div>
 
 
-<p>Define the base model that contains the unsecured data.  This can be any model type.  For our example we use an in memory model that reads the exampl.ttl file.</p>
+<p>Define the base model that contains the unsecured data.  This can be any model type.  For our example we use an in memory model that reads the example.ttl file.</p>
 <div class="codehilite"><pre><span class="n">my</span><span class="o">:</span><span class="n">baseModel</span> <span class="n">rdf</span><span class="o">:</span><span class="n">type</span> <span class="n">ja</span><span class="o">:</span><span class="n">MemoryModel</span><span class="o">;</span>
     <span class="n">ja</span><span class="o">:</span><span class="n">content</span> <span class="o">[</span><span class="n">ja</span><span class="o">:</span><span class="n">externalContent</span> <span class="o">&lt;</span><span class="n">file</span><span class="o">:./</span><span class="n">example</span><span class="o">.</span><span class="na">ttl</span><span class="o">&gt;]</span>
     <span class="o">.</span>
@@ -278,7 +278,7 @@ graph.</p>
 </pre></div>
 
 
-<p>Define the dataset that we will use for in the server.  Note that in the example dataset only contains the single secured model, adding multiple models and mising secured and
+<p>Define the dataset that we will use for in the server.  Note that in the example dataset only contains the single secured model, adding multiple models and missing secured and
 unsecured models is supported.</p>
 <div class="codehilite"><pre><span class="n">my</span><span class="o">:</span><span class="n">securedDataset</span> <span class="n">rdf</span><span class="o">:</span><span class="n">type</span> <span class="n">ja</span><span class="o">:</span><span class="n">RDFDataset</span> <span class="o">;</span>
     <span class="n">ja</span><span class="o">:</span><span class="n">defaultGraph</span> <span class="n">my</span><span class="o">:</span><span class="n">securedModel</span> <span class="o">.</span>
@@ -286,7 +286,7 @@ unsecured models is supported.</p>
 
 
 <p>Define the fuseki:Server.</p>
-<div class="codehilite"><pre><span class="n">my</span><span class="o">:</span><span class="n">fuskei</span> <span class="n">rdf</span><span class="o">:</span><span class="n">type</span> <span class="n">fuseki</span><span class="o">:</span><span class="n">Server</span> <span class="o">;</span>
+<div class="codehilite"><pre><span class="n">my</span><span class="o">:</span><span class="n">fuseki</span> <span class="n">rdf</span><span class="o">:</span><span class="n">type</span> <span class="n">fuseki</span><span class="o">:</span><span class="n">Server</span> <span class="o">;</span>
     <span class="n">fuseki</span><span class="o">:</span><span class="n">services</span> <span class="o">(</span>
         <span class="n">my</span><span class="o">:</span><span class="n">service1</span>
     <span class="o">)</span> <span class="o">.</span>
@@ -302,7 +302,7 @@ unsecured models is supported.</p>
     <span class="n">fuseki</span><span class="o">:</span><span class="n">serviceUpdate</span>              <span class="s2">&quot;update&quot;</span> <span class="o">;</span>   <span class="err">#</span> <span class="n">SPARQL</span> <span class="n">query</span> <span class="n">service</span>
     <span class="n">fuseki</span><span class="o">:</span><span class="n">serviceUpload</span>              <span class="s2">&quot;upload&quot;</span> <span class="o">;</span>   <span class="err">#</span> <span class="n">Non</span><span class="o">-</span><span class="n">SPARQL</span> <span class="n">upload</span> <span class="n">service</span>
     <span class="n">fuseki</span><span class="o">:</span><span class="n">serviceReadWriteGraphStore</span> <span class="s2">&quot;data&quot;</span> <span class="o">;</span>     <span class="err">#</span> <span class="n">SPARQL</span> <span class="n">Graph</span> <span class="n">store</span> <span class="n">protocol</span> <span class="o">(</span><span class="n">read</span> <span class="n">and</span> <span class="n">write</span><span class="o">)</span>
-    <span class="err">#</span> <span class="n">A</span> <span class="n">separate</span> <span class="n">ead</span><span class="o">-</span><span class="n">only</span> <span class="n">graph</span> <span class="n">store</span> <span class="n">endpoint</span><span class="o">:</span>
+    <span class="err">#</span> <span class="n">A</span> <span class="n">separate</span> <span class="n">read</span><span class="o">-</span><span class="n">only</span> <span class="n">graph</span> <span class="n">store</span> <span class="n">endpoint</span><span class="o">:</span>
     <span class="n">fuseki</span><span class="o">:</span><span class="n">serviceReadGraphStore</span>      <span class="s2">&quot;get&quot;</span> <span class="o">;</span>      <span class="err">#</span> <span class="n">SPARQL</span> <span class="n">Graph</span> <span class="n">store</span> <span class="n">protocol</span> <span class="o">(</span><span class="n">read</span> <span class="n">only</span><span class="o">)</span>
     <span class="n">fuseki</span><span class="o">:</span><span class="n">dataset</span>                    <span class="n">my</span><span class="o">:</span><span class="n">securedDataset</span> <span class="o">;</span>
 <span class="o">.</span>

Modified: websites/staging/jena/trunk/content/documentation/query/algebra.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/algebra.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/algebra.html Mon Oct 23 02:34:02 2017
@@ -169,7 +169,7 @@ algebra within ARQ. The definition of th
 found in the SPARQL specification in
 <a href="http://www.w3.org/TR/sparql11-query/#sparqlDefinition">section 12</a>.
 <a href="arq-query-eval.html">ARQ can be extended</a> to modify the evaluation
-of the algebra form to access difefrent graph storage
+of the algebra form to access different graph storage
 implementations.</p>
 <p>The classes for the datastructures for the algebra resize in the
 package <code>org.apache.jena.sparql.algebra</code> in the <code>op</code> subpackage. 
@@ -205,7 +205,7 @@ passing the parsed Query object to the t
 <p>This reverse translation can handle any algebra expression
 originally from a SPARQL Query, but not any algebra expression.  It
 is possible to create programmatically useful algebra expressions
-that can not be truned into a query, especially if they involve
+that can not be turned into a query, especially if they involve
 algebra.  Also, the query produced may not be exactly the same but
 will yield the same results (for example, filters may be moved
 because the SPARQL query algebra translation in the SPARQL
@@ -258,7 +258,7 @@ solutions (called Bindings).</p>
 </pre></div>
 
 
-<p>Operations of <code>CONSTRUCT</code>, <code>DESCRIBE</code> and <code>ASK</code> are done on on top
+<p>Operations of <code>CONSTRUCT</code>, <code>DESCRIBE</code> and <code>ASK</code> are done on top
 of algebra evaluation. Applications can access this functionality
 by creating their own <code>QueryEngine</code> (see
 <code>arq.examples.engine.MyQueryEngine</code>) and it's factory. A query

Modified: websites/staging/jena/trunk/content/documentation/query/construct-quad.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/construct-quad.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/construct-quad.html Mon Oct 23 02:34:02 2017
@@ -174,7 +174,7 @@ conveniences for the users manipulating
 <a href="http://www.w3.org/TR/turtle/">Turtle</a> format with possible variables.  The
 syntax for this extension follows that style in ARQ, using
 <a href="http://www.w3.org/TR/trig/">TriG</a> plus variables.  Just like SPARQL 1.1,
-there're 2 forms for ARQ Contruct Quad query:</p>
+there are 2 forms for ARQ Construct Quad query:</p>
 <h3 id="complete-form">Complete Form<a class="headerlink" href="#complete-form" title="Permanent link">&para;</a></h3>
 <div class="codehilite"><pre><span class="n">CONSTRUCT</span> <span class="p">{</span>
     # <span class="n">Named</span> <span class="n">graph</span>
@@ -256,8 +256,8 @@ and no complex graph patterns are allowe
 <p>One difference of the 2 methods is: 
 The method of <code>execConstructQuads()</code> returns an <code>Iterator</code> of <code>Quad</code>, allowing duplication.
 But <code>execConstructDataset()</code> constructs the desired Dataset object with only unique <code>Quad</code>s.</p>
-<p>In order to use these methods, it's required to swtich on the query syntax
-of ARQ beforehead, when creating the <code>Query</code> object:</p>
+<p>In order to use these methods, it's required to switch on the query syntax
+of ARQ before head, when creating the <code>Query</code> object:</p>
 <div class="codehilite"><pre><span class="n">Query</span> <span class="n">query</span> <span class="p">=</span> <span class="n">QueryFactory</span><span class="p">.</span><span class="n">create</span><span class="p">(</span><span class="n">queryString</span><span class="p">,</span> <span class="n">Syntax</span><span class="p">.</span><span class="n">syntaxARQ</span><span class="p">);</span>
 </pre></div>
 
@@ -284,11 +284,11 @@ on the default graph. For instance:</p>
 
 <p>More examples can be found at <code>ExampleConstructQuads.java</code> under <code>jena-arq/src-examples</code></p>
 <h2 id="fuseki-support">Fuseki Support<a class="headerlink" href="#fuseki-support" title="Permanent link">&para;</a></h2>
-<p>Jena <a href="http://jena.apache.org/documentation/fuseki2/index.html">Fuseki</a> is also empowed with Construct Quad query as a built-in
-function. No more addtional configuration is required to switch it on.
+<p>Jena <a href="http://jena.apache.org/documentation/fuseki2/index.html">Fuseki</a> is also empowered with Construct Quad query as a built-in
+function. No more additional configuration is required to switch it on.
 Because
 <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/http/QueryEngineHTTP.html">QueryEngineHTTP</a>
-is just an implementation of QueryExcecution, there's no much difference
+is just an implementation of QueryExecution, there's no much difference
 for the client users to manipulate the programming API described in the
 previous sections, e.g.</p>
 <div class="codehilite"><pre><span class="n">String</span> <span class="n">queryString</span> <span class="p">=</span> &quot; <span class="n">CONSTRUCT</span> <span class="p">{</span> <span class="n">GRAPH</span> <span class="o">&lt;</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">example</span><span class="o">/</span><span class="n">ns</span>#<span class="n">g1</span><span class="o">&gt;</span> <span class="p">{</span>?<span class="n">s</span> ?<span class="n">p</span> ?<span class="n">o</span><span class="p">}</span> <span class="p">}</span> <span class="n">WHERE</span> <span class="p">{</span>?<span class="n">s</span> ?<span class="n">p</span> ?<span class="n">o</span><span class="p">}</span>&quot; <span class="p">;</span>

Modified: websites/staging/jena/trunk/content/documentation/query/custom_aggregates.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/custom_aggregates.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/custom_aggregates.html Mon Oct 23 02:34:02 2017
@@ -156,7 +156,7 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>ARQ supports custom aggretate functions as allowed by teh SPARQL 1.1 specification.</p>
+<p>ARQ supports custom aggregate functions as allowed by the SPARQL 1.1 specification.</p>
 <p>See <a href="https://github.com/apache/jena/tree/master/jena-arq/src-examples/arq/examples/aggregates">example code</a>.</p>
   </div>
 </div>

Modified: websites/staging/jena/trunk/content/documentation/query/explain.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/explain.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/explain.html Mon Oct 23 02:34:02 2017
@@ -168,7 +168,7 @@ operators. During query execution, the l
 optimization occurs such as choosing the order of triple patterns within
 basic graph patterns.</p>
 <p>The effect of <a href="#algebra-transformations">high-level optimizations</a> can
-be seen using <code>arq.qparse</code> and the low-level runtime optimziations can
+be seen using <code>arq.qparse</code> and the low-level runtime optimizations can
 be seen by <a href="#execution-logging">execution logging</a>.</p>
 <h2 id="algebra-transformations">Algebra Transformations<a class="headerlink" href="#algebra-transformations" title="Permanent link">&para;</a></h2>
 <p>The preparation for a query for execution can be investigated with the
@@ -245,7 +245,7 @@ globally:</p>
 
 <p>and it may also be set on an individual query execution using it's local
 context.</p>
-<div class="codehilite"><pre> <span class="k">try</span><span class="p">(</span><span class="n">QueryExecutiuon</span> <span class="n">qExec</span> <span class="p">=</span> <span class="n">QueryExecutionFactory</span><span class="p">.</span><span class="n">create</span><span class="p">(...))</span> <span class="p">{</span>
+<div class="codehilite"><pre> <span class="k">try</span><span class="p">(</span><span class="n">QueryExecution</span> <span class="n">qExec</span> <span class="p">=</span> <span class="n">QueryExecutionFactory</span><span class="p">.</span><span class="n">create</span><span class="p">(...))</span> <span class="p">{</span>
      <span class="n">qExec</span><span class="p">.</span><span class="n">getContext</span><span class="p">().</span><span class="n">set</span><span class="p">(</span><span class="n">ARQ</span><span class="p">.</span><span class="n">symLogExec</span><span class="p">,</span> <span class="n">Explain</span><span class="p">.</span><span class="n">InfoLevel</span><span class="p">.</span><span class="n">ALL</span><span class="p">)</span> <span class="p">;</span>
      <span class="n">ResultSet</span> <span class="n">rs</span> <span class="p">=</span> <span class="n">qExec</span><span class="p">.</span><span class="n">execSelect</span><span class="p">()</span> <span class="p">;</span>
      <span class="p">...</span>

Modified: websites/staging/jena/trunk/content/documentation/query/group-by.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/group-by.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/group-by.html Mon Oct 23 02:34:02 2017
@@ -238,7 +238,7 @@ two names can refer to the same individu
 <p>If there was no explicit <code>GROUP BY</code> clause, then it is as if the
 whole of the result set forms a single group element. 
 Equivalently, it is <code>GROUP BY</code> of no variables. Only aggregation
-expressions make sense in the SELECT clause as theer are no
+expressions make sense in the SELECT clause as there are no
 variables from the query pattern to project out.</p>
 <p><a href="index.html">ARQ documentation index</a></p>
   </div>

Modified: websites/staging/jena/trunk/content/documentation/query/http-auth.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/http-auth.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/http-auth.html Mon Oct 23 02:34:02 2017
@@ -156,7 +156,7 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>After <a href="#http-authentication-from-jena-311">Jena 3.1.0</a>, Jena exposes the underlying HTTP Commons functionality to support a range of authentication mechanisms as well as <a href="https://hc.apache.org/httpcomponents-client-ga/examples.html">other HTTP configuration</a>. From <a href="#http-authentication-from-jena-300-through-310">Jena 3.0.0 through Jena 3.1.0</a> there is a Jena-specific framework that provides a uniform mechanism for HTTP authentication. This documentation is therefore devided into two sections. The first explains how to use HTTP Commons code, and the second explains the older Jena-specific functionality.</p>
+<p>After <a href="#http-authentication-from-jena-311">Jena 3.1.0</a>, Jena exposes the underlying HTTP Commons functionality to support a range of authentication mechanisms as well as <a href="https://hc.apache.org/httpcomponents-client-ga/examples.html">other HTTP configuration</a>. From <a href="#http-authentication-from-jena-300-through-310">Jena 3.0.0 through Jena 3.1.0</a> there is a Jena-specific framework that provides a uniform mechanism for HTTP authentication. This documentation is therefore divided into two sections. The first explains how to use HTTP Commons code, and the second explains the older Jena-specific functionality.</p>
 <h2 id="http-authentication-from-jena-311">HTTP Authentication from Jena 3.1.1<a class="headerlink" href="#http-authentication-from-jena-311" title="Permanent link">&para;</a></h2>
 <p>APIs that support authentication typically provide methods for providing an <a href="https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/HttpClient.html">HttpClient</a> for use with the given instance of that API class. Since it may not always be possible/practical to configure authenticators on a per-request basis the API includes a means to specify a default client that is used when no other client is explicitly specified.  This may be configured via the 
 <code>setDefaultHttpClient(HttpClient httpClient)</code> method of the <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/riot/web/HttpOp.html">HttpOp</a> class. This allows for static-scoped configuration of HTTP behavior.</p>

Modified: websites/staging/jena/trunk/content/documentation/query/library-function.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/library-function.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/library-function.html Mon Oct 23 02:34:02 2017
@@ -171,7 +171,7 @@ functions.  Functions and property fu
 "<a href="https://www.w3.org/TR/xpath-functions-3/">XQuery 1.0 and XPath 2.0 Functions and Operators v3.1</a>". </p>
 <p>Functions in involving sequences are not supported.</p>
 <p>See <a href="xsd-support.html">XSD Support</a> for details of datatypes and functions
-currenty supported.  To check the exact current registrations, see
+currently supported.  To check the exact current registrations, see
 <tt><a href="https://github.com/apache/jena/blob/master/jena-arq/src/main/java/org/apache/jena/sparql/function/StandardFunctions.java">function/StandardFunctions.java</a></tt>.</p>
 <p>See also the <a href="library-propfunc.html">property functions</a> library
 page.</p>
@@ -193,7 +193,7 @@ XPath and XQuery function namespace).</p
 <p>These are modelled after SQL aggregate functions <code>STDEV</code>, <code>STDEV_SAMP</code>, <code>STDEV_POP</code>,
 <code>VARIANCE</code>, <code>VAR_SAMP</code>, <code>VAR_POP</code>.</p>
 <p>These, as keywords, are available in ARQ's extended SPARQL (parse using <code>Syntax.syntaxARQ</code>).</p>
-<h3 id="addtional-functions-provided-by-arq">Addtional Functions Provided by ARQ<a class="headerlink" href="#addtional-functions-provided-by-arq" title="Permanent link">&para;</a></h3>
+<h3 id="additional-functions-provided-by-arq">Additional Functions Provided by ARQ<a class="headerlink" href="#additional-functions-provided-by-arq" title="Permanent link">&para;</a></h3>
 <p>Most of these have equivalents, or near equivalents, in SPARQL or as an
 XQuery function and are to be preferred. These ARQ-specific versions remain
 for compatibility.</p>

Modified: websites/staging/jena/trunk/content/documentation/query/logging.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/logging.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/logging.html Mon Oct 23 02:34:02 2017
@@ -253,7 +253,7 @@ globally:</p>
 
 <p>and it may also be set on an individual query execution using its local
 context.</p>
-<div class="codehilite"><pre> <span class="k">try</span><span class="p">(</span><span class="n">QueryExecutiuon</span> <span class="n">qExec</span> <span class="p">=</span> <span class="n">QueryExecutionFactory</span><span class="p">.</span><span class="n">create</span><span class="p">(...))</span> <span class="p">{</span>
+<div class="codehilite"><pre> <span class="k">try</span><span class="p">(</span><span class="n">QueryExecution</span> <span class="n">qExec</span> <span class="p">=</span> <span class="n">QueryExecutionFactory</span><span class="p">.</span><span class="n">create</span><span class="p">(...))</span> <span class="p">{</span>
     <span class="n">qExec</span><span class="p">.</span><span class="n">getContext</span><span class="p">().</span><span class="n">set</span><span class="p">(</span><span class="n">ARQ</span><span class="p">.</span><span class="n">symLogExec</span><span class="p">,</span> <span class="n">Explain</span><span class="p">.</span><span class="n">InfoLevel</span><span class="p">.</span><span class="n">ALL</span><span class="p">)</span> <span class="p">;</span>
     <span class="p">...</span>
  <span class="p">}</span>

Modified: websites/staging/jena/trunk/content/documentation/query/service.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/service.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/service.html Mon Oct 23 02:34:02 2017
@@ -165,7 +165,7 @@ results sent back (in RDF, or an
 <a href="http://www.w3.org/TR/rdf-sparql-XMLres/">XML-based results format</a>
 or even a <a href="http://www.w3.org/TR/rdf-sparql-json-res/">JSON one</a>).</p>
 <p><code>SERVICE</code> is a feature of SPARQL 1.1 that allows an executing query to
-to make a SPARQL protocol to another SPARQL endopoint.</p>
+to make a SPARQL protocol to another SPARQL endpoint.</p>
 <h2 id="syntax">Syntax<a class="headerlink" href="#syntax" title="Permanent link">&para;</a></h2>
 <div class="codehilite"><pre><span class="n">PREFIX</span> <span class="p">:</span> <span class="o">&lt;</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">example</span><span class="o">/&gt;</span>
 <span class="n">PREFIX</span>  <span class="n">dc</span><span class="p">:</span>     <span class="o">&lt;</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">purl</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">dc</span><span class="o">/</span><span class="n">elements</span><span class="o">/</span>1<span class="p">.</span>1<span class="o">/&gt;</span>
@@ -289,11 +289,11 @@ the title already bound from earlier in
 </table>
 <h4 id="srvquerytimeout_1"><code>srv:queryTimeout</code><a class="headerlink" href="#srvquerytimeout_1" title="Permanent link">&para;</a></h4>
 <p>Set the connect and read timeouts for the query.</p>
-<p>If a timeout occurs a QueryExceptionHTTP is thrown.  The cause of that execption will be a java.net.SocketTimeoutException.</p>
+<p>If a timeout occurs a QueryExceptionHTTP is thrown.  The cause of that exception will be a java.net.SocketTimeoutException.</p>
 <p>Number: number of milliseconds for connect timeout.</p>
-<p>String: number of milliseconds for connect timeout.  If string is of the form “X,Y” the first number is the numbr of milliseconds for the connect timeout and the seconds is the number of milliseconds for the read timeout.</p>
+<p>String: number of milliseconds for connect timeout.  If string is of the form “X,Y” the first number is the number of milliseconds for the connect timeout and the seconds is the number of milliseconds for the read timeout.</p>
 <p>Connect timeout =0
-read timout = 0</p>
+read timeout = 0</p>
 <p>Values of 0 indicate no timeout and service operation will wait until the remote server responds.</p>
 <h4 id="srvquerygzip"><code>srv:queryGzip</code><a class="headerlink" href="#srvquerygzip" title="Permanent link">&para;</a></h4>
 <p>Sets the allow Gzip flag.</p>



Mime
View raw message