Author: kinow
Date: Mon Oct 23 02:32:48 2017
New Revision: 1812967
URL: http://svn.apache.org/viewvc?rev=1812967&view=rev
Log:
Spell checking the website
Modified:
jena/site/trunk/content/documentation/assembler/assembler-howto.mdtext
jena/site/trunk/content/documentation/csv/implementation.mdtext
jena/site/trunk/content/documentation/fuseki2/fuseki-configuration.mdtext
jena/site/trunk/content/documentation/fuseki2/fuseki-data-services.mdtext
jena/site/trunk/content/documentation/fuseki2/fuseki-embedded.md
jena/site/trunk/content/documentation/fuseki2/fuseki-logging.mdtext
jena/site/trunk/content/documentation/fuseki2/fuseki-server-protocol.mdtext
jena/site/trunk/content/documentation/fuseki2/index.mdtext
jena/site/trunk/content/documentation/hadoop/common.mdtext
jena/site/trunk/content/documentation/inference/index.mdtext
jena/site/trunk/content/documentation/io/rdf-input.mdtext
jena/site/trunk/content/documentation/io/rdf-output.mdtext
jena/site/trunk/content/documentation/io/rdfxml_howto.mdtext
jena/site/trunk/content/documentation/jdbc/artifacts.mdtext
jena/site/trunk/content/documentation/jdbc/custom_driver.mdtext
jena/site/trunk/content/documentation/migrate_jena2_jena3.mdtext
jena/site/trunk/content/documentation/notes/datasetgraph.md
jena/site/trunk/content/documentation/notes/jena-internals.mdtext
jena/site/trunk/content/documentation/notes/jena-repack.md
jena/site/trunk/content/documentation/notes/reification_previous.mdtext
jena/site/trunk/content/documentation/notes/sse.mdtext
jena/site/trunk/content/documentation/notes/typed-literals.mdtext
jena/site/trunk/content/documentation/ontology/index.mdtext
jena/site/trunk/content/documentation/permissions/design.mdtext
jena/site/trunk/content/documentation/permissions/evaluator.mdtext
jena/site/trunk/content/documentation/permissions/example.mdtext
jena/site/trunk/content/documentation/query/algebra.mdtext
jena/site/trunk/content/documentation/query/construct-quad.mdtext
jena/site/trunk/content/documentation/query/custom_aggregates.mdtext
jena/site/trunk/content/documentation/query/explain.mdtext
jena/site/trunk/content/documentation/query/group-by.mdtext
jena/site/trunk/content/documentation/query/http-auth.mdtext
jena/site/trunk/content/documentation/query/library-function.mdtext
jena/site/trunk/content/documentation/query/logging.mdtext
jena/site/trunk/content/documentation/query/property_paths.mdtext
jena/site/trunk/content/documentation/query/service.mdtext
jena/site/trunk/content/documentation/query/spatial-query.mdtext
jena/site/trunk/content/documentation/query/text-query.mdtext
jena/site/trunk/content/documentation/query/update.mdtext
jena/site/trunk/content/documentation/query/writing_functions.mdtext
jena/site/trunk/content/documentation/query/writing_propfuncs.mdtext
jena/site/trunk/content/documentation/rdf/datasets.md
jena/site/trunk/content/documentation/rdf/index.mdtext
jena/site/trunk/content/documentation/rdfconnection/index.md
jena/site/trunk/content/documentation/sdb/commands.mdtext
jena/site/trunk/content/documentation/sdb/configuration.mdtext
jena/site/trunk/content/documentation/sdb/dataset_description.mdtext
jena/site/trunk/content/documentation/sdb/db_notes.mdtext
jena/site/trunk/content/documentation/sdb/javaapi.mdtext
jena/site/trunk/content/documentation/sdb/loading_performance.mdtext
jena/site/trunk/content/documentation/serving_data/index.mdtext
jena/site/trunk/content/documentation/tdb/architecture.mdtext
jena/site/trunk/content/documentation/tdb/commands.mdtext
jena/site/trunk/content/documentation/tdb/configuration.mdtext
jena/site/trunk/content/documentation/tdb/datasets.mdtext
jena/site/trunk/content/documentation/tdb/dynamic_datasets.mdtext
jena/site/trunk/content/documentation/tdb/optimizer.mdtext
jena/site/trunk/content/documentation/tdb/store-parameters.mdtext
jena/site/trunk/content/documentation/tdb/tdb_system.mdtext
jena/site/trunk/content/documentation/tdb2/tdb2_admin.md
jena/site/trunk/content/documentation/tdb2/tdb2_fuseki.md
jena/site/trunk/content/documentation/tools/eyeball-manual.mdtext
jena/site/trunk/content/documentation/tools/schemagen.mdtext
jena/site/trunk/content/documentation/txn/index.md
jena/site/trunk/content/documentation/txn/transactions_api.md
jena/site/trunk/content/documentation/txn/txn.md
jena/site/trunk/content/download/maven.mdtext
jena/site/trunk/content/help_and_support/index.mdtext
jena/site/trunk/content/tutorials/rdf_api.mdtext
jena/site/trunk/content/tutorials/sparql_basic_patterns.mdtext
jena/site/trunk/content/tutorials/sparql_query1.mdtext
jena/site/trunk/content/tutorials/sparql_union.mdtext
Modified: jena/site/trunk/content/documentation/assembler/assembler-howto.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/assembler/assembler-howto.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/assembler/assembler-howto.mdtext
(original)
+++ jena/site/trunk/content/documentation/assembler/assembler-howto.mdtext Mon
Oct 23 02:32:48 2017
@@ -424,7 +424,7 @@ appropriate properties:
`ja:likeBuiltinSpec ja:OWL_MEM`.
- `ja:importSource`: The value of this optional unique property
is a `ModelSource` description which describes where imports are
- obtained from. A `ModelSource` is usually of of class `ja:ModelSource`.
+ obtained from. A `ModelSource` is usually of class `ja:ModelSource`.
- `ja:documentManager`: This value of this optional unique
property is a DocumentManager specification. If absent, the default
document manager is used.
Modified: jena/site/trunk/content/documentation/csv/implementation.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/csv/implementation.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/csv/implementation.mdtext (original)
+++ jena/site/trunk/content/documentation/csv/implementation.mdtext Mon Oct 23
02:32:48 2017
@@ -2,7 +2,7 @@ Title: CSV PropertyTable - Implementatio
## PropertyTable Implementations
-There're 2 implementations for `PropertyTable`. The pros and cons are
summarised in the following table:
+There are 2 implementations for `PropertyTable`. The pros and cons are
summarised in the following table:
PropertyTable Implementation | Description | Supported Indexes | Advantages |
Disadvantages
---------------------------- | ----------- | ----------------- | ---------- |
-------------
Modified:
jena/site/trunk/content/documentation/fuseki2/fuseki-configuration.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/fuseki2/fuseki-configuration.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/fuseki2/fuseki-configuration.mdtext
(original)
+++ jena/site/trunk/content/documentation/fuseki2/fuseki-configuration.mdtext
Mon Oct 23 02:32:48 2017
@@ -152,4 +152,4 @@ single configuration file, will still wo
(you can't restart these services after stopping them in a running server)
and user should plan to migrate to the [new layout](./fuseki-layout.html).
-To convert a Fuseki 1 configuration setup to Fuseki 2 style, move each data
service assembler and put in it's own file under `FUSEKI_BASE/configuration/`
+To convert a Fuseki 1 configuration setup to Fuseki 2 style, move each data
service assembler and put in its own file under `FUSEKI_BASE/configuration/`
Modified:
jena/site/trunk/content/documentation/fuseki2/fuseki-data-services.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/fuseki2/fuseki-data-services.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/fuseki2/fuseki-data-services.mdtext
(original)
+++ jena/site/trunk/content/documentation/fuseki2/fuseki-data-services.mdtext
Mon Oct 23 02:32:48 2017
@@ -10,7 +10,7 @@ URI scheme.
## SPARQL Protocol
-Queyr
+Query
update
GSP including direct naming for GSP
Modified: jena/site/trunk/content/documentation/fuseki2/fuseki-embedded.md
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/fuseki2/fuseki-embedded.md?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/fuseki2/fuseki-embedded.md (original)
+++ jena/site/trunk/content/documentation/fuseki2/fuseki-embedded.md Mon Oct 23
02:32:48 2017
@@ -33,7 +33,7 @@ To build and start the server:
then the application can modify the dataset:
// Add some data while live.
- // Write trasnaction.
+ // Write transaction.
Txn.execWrite(dsg, ()->RDFDataMgr.read(dsg, "D.trig")) ;
or read the dataset and see any updates made by remote systems:
@@ -61,11 +61,11 @@ To include an embedded Fuseki server in
<version>2.x.y</version> <!-- Set the version -->
</dependency>
-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
+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.
-This dependency does not include a logging setting. Fusek uses
[slf4j](http://slf4j.org/).
+This dependency does not include a logging setting. Fuseki uses
[slf4j](http://slf4j.org/).
See section "[Logging](#logging)" for details.
If the application wishes to use a dataset with a
[text-index](http://jena.apache.org/documentation/query/text-query.html)
Modified: jena/site/trunk/content/documentation/fuseki2/fuseki-logging.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/fuseki2/fuseki-logging.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/fuseki2/fuseki-logging.mdtext
(original)
+++ jena/site/trunk/content/documentation/fuseki2/fuseki-logging.mdtext Mon Oct
23 02:32:48 2017
@@ -39,7 +39,7 @@ The Fuseki engine looks for the log4j co
* Use java resource `org/apache/jena/fuseki/log4j.properties` on the classpath.
* Use a built-in configuration.
-The laststep is a fallback to catch the case where Fuseki has been repackaged
+The last step is a fallback to catch the case where Fuseki has been repackaged
into a new WAR file and `org/apache/jena/fuseki/log4j.properties` omitted, or
run from
the base jar. It is better to include
`org/apache/jena/fuseki/log4j.properties`.
Modified:
jena/site/trunk/content/documentation/fuseki2/fuseki-server-protocol.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/fuseki2/fuseki-server-protocol.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/fuseki2/fuseki-server-protocol.mdtext
(original)
+++ jena/site/trunk/content/documentation/fuseki2/fuseki-server-protocol.mdtext
Mon Oct 23 02:32:48 2017
@@ -72,7 +72,7 @@ in the container, via `GET`, `POST` and
> _@@ May add server-managed templates_
-A dataset set can be added to a running server. There ae several methods
+A dataset set can be added to a running server. There are several methods
for doing this:
* Post the assembler file
@@ -108,7 +108,7 @@ Datasets are created in director `databa
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).
-The assembler file is stored by the server will be used on restart or when
makign the datsset active again.
+The assembler file is stored by the server will be used on restart or when
making the dataset active again.
> _@@_
@@ -164,8 +164,8 @@ The returned JOSN object is `{ backups:
a list of file names.
## Tasks
-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
+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 `Location:` header with the URL of the task created.
The progress of the task can be monitored with HTTP GET operations:
Modified: jena/site/trunk/content/documentation/fuseki2/index.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/fuseki2/index.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/fuseki2/index.mdtext (original)
+++ jena/site/trunk/content/documentation/fuseki2/index.mdtext Mon Oct 23
02:32:48 2017
@@ -82,7 +82,7 @@ at [http://archive.apache.org/dist/jena]
### Development Builds
-Regular developement builds of all of Jena are available (these are not
+Regular development builds of all of Jena are available (these are not
formal releases) from the
[Apache snapshots maven
repository](https://repository.apache.org/snapshots/org/apache/jena).
This includes packaged builds of Fuseki.
@@ -90,7 +90,7 @@ This includes packaged builds of Fuseki.
## Getting Started With Fuseki
The [quick start](fuseki-quick-start.html) section serves as a basic
-guide to getting a Fuskei server running on your local machine.
+guide to getting a Fuseki server running on your local machine.
See [all the ways to run Fuseki](fuseki-run.html) for complete coverage of all
the
deployment methods for Fuseki.
Modified: jena/site/trunk/content/documentation/hadoop/common.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/hadoop/common.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/hadoop/common.mdtext (original)
+++ jena/site/trunk/content/documentation/hadoop/common.mdtext Mon Oct 23
02:32:48 2017
@@ -8,7 +8,7 @@ Currently we represent the three main RD
## Nodes
-The `Writable` type for nodes is predictably enough called `NodeWritable` and
it implements the `WritableComparable` interface which means it can be used as
both a key and/or value in Map/Reduce. In standard Hadoop style a `get()`
method returns the actual value as a Jena `Node` instance while a corresponding
`set()` method allows the value to be set. Coveying `null` values is
acceptable and fully supported.
+The `Writable` type for nodes is predictably enough called `NodeWritable` and
it implements the `WritableComparable` interface which means it can be used as
both a key and/or value in Map/Reduce. In standard Hadoop style a `get()`
method returns the actual value as a Jena `Node` instance while a corresponding
`set()` method allows the value to be set. Conveying `null` values is
acceptable and fully supported.
Note that nodes are lazily converted to and from the underlying binary
representation so there is minimal overhead if you create a `NodeWritable`
instance that does not actually ever get read/written.
@@ -44,4 +44,4 @@ In some cases you may have data that is
Like the other primitives it implements `WritableComparable` so can be used as
a key and/or value. However this primitive does not support binary comparisons
meaning it may not perform as well as using the other primitives.
-In this case the `get()` and `set()` methods get/set a `Tuple<Node>` instance
which is a convenience container class provided by ARQ. Currently the
implementation does not support lazy conversion so the full `Tuple<Node>` is
reconstructed as soon as an `NodeTupleWritable` instance is deserialised.
\ No newline at end of file
+In this case the `get()` and `set()` methods get/set a `Tuple<Node>` instance
which is a convenience container class provided by ARQ. Currently the
implementation does not support lazy conversion so the full `Tuple<Node>` is
reconstructed as soon as an `NodeTupleWritable` instance is deserialised.
Modified: jena/site/trunk/content/documentation/inference/index.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/inference/index.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/inference/index.mdtext (original)
+++ jena/site/trunk/content/documentation/inference/index.mdtext Mon Oct 23
02:32:48 2017
@@ -1035,7 +1035,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>
###<a name="OWLexamples"></a>OWL Example
@@ -1045,7 +1045,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
"whiteBoxZX"
and "<code>bigName42</code>".</p>
<p>We can create an instance of the OWL reasoner, specialized to the demo
schema
@@ -1088,9 +1088,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>"hasValue(eg:hasComponent,
+ </i>The anonymous rdf:type statement references the
<code>"hasValue(eg:hasComponent,
eg:gamingGraphics)" </code>restriction mentioned in the definition of
GamingComputer.</p>
<p>A second, typical operation is instance recognition. Testing if an
individual
is an instance of a class expression. In this case the
<code>whileBoxZX</code>
@@ -1108,7 +1108,7 @@ configuration still leaves something to
System.out.println("Failed to recognize white box correctly");
}
-<p> Which gnerates the output:</p>
+<p> Which generates the output:</p>
<pre> <i>White box recognized as gaming computer</i></pre>
<p>Finally, we can check for inconsistencies within the data by using the
validation
interface:</p>
@@ -1180,7 +1180,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>
@@ -1209,7 +1209,7 @@ class B = cardinality(P,1)</pre>
####Incompleteness
<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>
@@ -1730,7 +1730,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', '(.*) (.*)', ?m1, ?m2)</pre>
will bind <code>m1</code> to <code>"foo"</code> and <code>m2</code> to
<code>"bar"</code>.</div>
@@ -1813,7 +1813,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>
@@ -1960,12 +1960,12 @@ while (i.hasNext()) {
###<a name="RDFSPlusRules"></a>Combining RDFS/OWL with custom rules
<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
@@ -1975,7 +1975,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
@@ -2007,7 +2007,7 @@ while (i.hasNext()) {
computing all possible answers when an application might only want a few.]</p>
<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>
[rdfs2: (?x ?p ?y), (?p rdfs:domain ?c) -> (?x rdf:type ?c)]
Modified: jena/site/trunk/content/documentation/io/rdf-input.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/io/rdf-input.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/io/rdf-input.mdtext (original)
+++ jena/site/trunk/content/documentation/io/rdf-input.mdtext Mon Oct 23
02:32:48 2017
@@ -120,7 +120,7 @@ Detail control over the setup of the par
For example, to read Trig data, and set the error handler specially,
// The parsers will do the necessary character set conversion.
- try (InputStream in = new
FileInputStream("data.some.unusal.extension")) {
+ try (InputStream in = new
FileInputStream("data.some.unusual.extension")) {
RDFParser.create()
.source(in)
.lang(RDFLanguages.TRIG)
@@ -140,7 +140,7 @@ By default, the `RDFDataMgr` uses the gl
InputStreams. This is available to applications via `RDFDataMgr.open` as well
as directly
using a `StreamManager`.
-The `StreamManager` is choosen based on the `Context` object for the
+The `StreamManager` is chosen based on the `Context` object for the
operation, but normally this defaults to the global `Context` available via
`Context.get()`. The constant `RDFDataMgr.streamManagerSymbol`, which is
`http://jena.apache.org/riot/streamManager` is used.
@@ -157,12 +157,12 @@ data:
The `StreamManager` can be reconfigured with different places to look for
files. The default configuration used for the global `StreamManager` 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,
-There is also a `LocationMapper` for rewiting file names and URLs before
+There is also a `LocationMapper` 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).
@@ -264,4 +264,4 @@ See [RIOT example 4](https://github.com/
The set of languages is not fixed. A new languages,
together with a parser, can be added to RIOT as shown in
-[RIOT example
5](https://github.com/apache/jena/tree/master/jena-arq/src-examples/arq/examples/riot/ExRIOT_5.java)
\ No newline at end of file
+[RIOT example
5](https://github.com/apache/jena/tree/master/jena-arq/src-examples/arq/examples/riot/ExRIOT_5.java)
Modified: jena/site/trunk/content/documentation/io/rdf-output.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/io/rdf-output.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/io/rdf-output.mdtext (original)
+++ jena/site/trunk/content/documentation/io/rdf-output.mdtext Mon Oct 23
02:32:48 2017
@@ -62,7 +62,7 @@ are available as part of the standard se
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 `org.apache.jena.riot.RDFFormat` 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.
Note:
@@ -122,7 +122,7 @@ All the properties for a given subject a
into a predefined order. RDF lists are printed as
`(...)` and `[...]` is used for blank nodes where possible.
-The analysis for determing what can be pretty printed requires
+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.
@@ -328,7 +328,7 @@ compared to the text-based standardised
| RDFTHRIFT_VALUES |
`RDFTHRIFT_VALUES` 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
[description of RDF Thrift](http://afs.github.io/rdf-thrift)
for dsicussion.
@@ -372,7 +372,7 @@ The prefered style is to use `RDFDataMgr
// Write as N-Quads
RDFDataMgr.write(System.out, dataset, Lang.NQUADS) ;
-Additionaly, a single model can be written in a dataset format - it becomes
+Additionally, a single model can be written in a dataset format - it becomes
the default graph of the dataset.
Model m =
@@ -406,5 +406,5 @@ Using `OutputStream`s is strongly encour
to manage the character encoding using UTF-8. Using `java.io.Writer`
does not allow this; on platforms such as MS Windows, the default
configuration of a `Writer` 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 `java.io.StringWriter`.
+the character set is the platform default, and not UTF-8.
+The only use of writers that is useful is using `java.io.StringWriter`.
Modified: jena/site/trunk/content/documentation/io/rdfxml_howto.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/io/rdfxml_howto.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/io/rdfxml_howto.mdtext (original)
+++ jena/site/trunk/content/documentation/io/rdfxml_howto.mdtext Mon Oct 23
02:32:48 2017
@@ -581,7 +581,7 @@ RDF/XML with resources of these types at
As an example,
RDFWriter w = m.getWriter("RDF/XML-ABBREV");
- w.setProperty("attribtueQuoteChar","'");
+ w.setProperty("attributeQuoteChar","'");
w.setProperty("showXMLDeclaration","true");
w.setProperty("tab","1");
w.setProperty("blockRules",
Modified: jena/site/trunk/content/documentation/jdbc/artifacts.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/jdbc/artifacts.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/jdbc/artifacts.mdtext (original)
+++ jena/site/trunk/content/documentation/jdbc/artifacts.mdtext Mon Oct 23
02:32:48 2017
@@ -60,4 +60,4 @@ This artifact depends on all the other a
<groupId>org.apache.jena</groupId>
<artifactId>jena-jdbc-driver-bundle</artifactId>
<version>x.y.z</version>
- </dependency>
\ No newline at end of file
+ </dependency>
Modified: jena/site/trunk/content/documentation/jdbc/custom_driver.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/jdbc/custom_driver.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/jdbc/custom_driver.mdtext (original)
+++ jena/site/trunk/content/documentation/jdbc/custom_driver.mdtext Mon Oct 23
02:32:48 2017
@@ -36,11 +36,11 @@ If you wish to go down this route then w
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.
-Note that custom implementations may also require you to implement custom
`JenaStatement` and `JenaPreparedSatement`
+Note that custom implementations may also require you to implement custom
`JenaStatement` and `JenaPreparedStatement`
implementations.
## Testing your Driver
To aid testing your custom driver the `jena-jdbc-core` module provides a
number of abstract test classes which
can be derived from in order to provide a wide variety of tests for your
driver implementation. This is how
-all the built in drivers are tested so you can check out their test sources
for examples of this.
\ No newline at end of file
+all the built in drivers are tested so you can check out their test sources
for examples of this.
Modified: jena/site/trunk/content/documentation/migrate_jena2_jena3.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/migrate_jena2_jena3.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/migrate_jena2_jena3.mdtext (original)
+++ jena/site/trunk/content/documentation/migrate_jena2_jena3.mdtext Mon Oct 23
02:32:48 2017
@@ -30,7 +30,7 @@ Only java package names are being change
Migration support is provided by mapping `ja:loadClass` names beginning
`com.hp.hpl.jena` internally to `org.apache.jena`. A warning is logged.
-Any assmeeberlers that
+Any assemblers that
### Logging
@@ -89,7 +89,7 @@ Data that does use explicit `xsd:string`
Jena Security has been renamed Jena Permissions and the Maven _artifact id_
has been changed to _jena-permissions_ to reflect this change.
-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>.
+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>.
## Other
Modified: jena/site/trunk/content/documentation/notes/datasetgraph.md
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/notes/datasetgraph.md?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/notes/datasetgraph.md (original)
+++ jena/site/trunk/content/documentation/notes/datasetgraph.md Mon Oct 23
02:32:48 2017
@@ -41,7 +41,7 @@ There are two markers for transaction fe
If `begin`, `commit` and `end` are supported (which is normally the case)
`supportsTransactions` returns true.
-If, further, `abort` is suported, then `supportsTransactionAbort` is true.
+If, further, `abort` is supported, then `supportsTransactionAbort` is true.
### General hierarchy
@@ -49,7 +49,7 @@ If, further, `abort` is suported, then `
This provides some basic machinery and provides implementations of
operations that have alternative styles. It converts `add(G,S,P,O)` to
-`add(quad)` and `delete(G,S,P,O)` to `delele(quad)` and converts
+`add(quad)` and `delete(G,S,P,O)` to `delete(quad)` and converts
`find(quad)` to `find(G,S,P,O)`.
It provides basic implementations of `deleteAny(?,?,?,?)` and `clear()`.
@@ -136,7 +136,7 @@ A small class that provides the "get a g
`DatasetGraph` using `GraphView`.
Not used because subclasses usually want to inherit from a different part
-fo the hierarchy but the idea of implementating `getDefaultGraph()` and
+fo the hierarchy but the idea of implementing `getDefaultGraph()` and
`getGraph(Node)` as calls to `GraphView` is used elsewhere.
Do not use with an implementations that store using graph
@@ -183,9 +183,9 @@ Abort requires work to be undone. Jena
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.
+persistence). It still needs MRSW to archive isolation.
-Read-commited needs synchronization safe datastructures -including
+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).
Modified: jena/site/trunk/content/documentation/notes/jena-internals.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/notes/jena-internals.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/notes/jena-internals.mdtext (original)
+++ jena/site/trunk/content/documentation/notes/jena-internals.mdtext Mon Oct
23 02:32:48 2017
@@ -94,7 +94,7 @@ Some key features of the design are:
personalities, for example, may implement interfaces in different
ways, or not implement some at all.
- enhanced nodes wrap information in the graph, but keep no
- independant state; they may be discarded and regenerated at whim.
+ independent state; they may be discarded and regenerated at whim.
### How an enhanced node is created
@@ -211,13 +211,13 @@ is thus inappropriate for comparing reif
The goal of reification support in the Jena 2 implementation are:
- to conform to the revised RDF specifications
-- to maintain the expections of Jena 1; *ie* they should still be
+- to maintain the expectations of Jena 1; *ie* they should still be
able to reify everything without worrying about triple bloat if
they want to
- 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.
- to enable round tripping through RDF/XML and other RDF
- representation langauges
+ representation languages
- enable a complete standard compliant implementation, but not
necessarily as default
@@ -371,7 +371,7 @@ the *Statement*.
*createReifiedStatement* is expected to bypass the construction and
detection of the quad components, so that in the "usual case" they
-will never come into existance.
+will never come into existence.
## The Reification SPI
@@ -398,14 +398,14 @@ This is useful for internal graphs that
So there are three kinds of `Graph`:
Graphs that do no reification;
-Graphs that only do explicit reficiation;
+Graphs that only do explicit reification;
Graphs that do implicit reification.
### Graph operations for reification
The primary reification operation on graphs is to extract their
`Reifier` 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.
#### Graph.getReifier() -\> Reifier
@@ -508,7 +508,7 @@ added to it and have the reifier handle
this case, the graph's `add(t)` should call `handledAdd(t)` and
only proceed with its add if the result is `false`.
A graph that does not use `handledAdd()` [and `handledDelete()`]
-can only use the explict reification supplied by its reifier.
+can only use the explicit reification supplied by its reifier.
#### handledRemove( Triple t )
Modified: jena/site/trunk/content/documentation/notes/jena-repack.md
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/notes/jena-repack.md?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/notes/jena-repack.md (original)
+++ jena/site/trunk/content/documentation/notes/jena-repack.md Mon Oct 23
02:32:48 2017
@@ -1,6 +1,6 @@
Title: Combining Apache Jena jars
-Apache Jena initalizes uses Java's
+Apache Jena initializes uses Java's
[ServiceLoader](https://docs.oracle.com/javase/8/docs/api/java/util/ServiceLoader.html)
mechanism to locate initialization steps. The
documentation for process in Jena is [available
here](system-initialization.html).
Modified:
jena/site/trunk/content/documentation/notes/reification_previous.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/notes/reification_previous.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/notes/reification_previous.mdtext
(original)
+++ jena/site/trunk/content/documentation/notes/reification_previous.mdtext Mon
Oct 23 02:32:48 2017
@@ -4,7 +4,7 @@ Title: Reification styles (archive mater
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.
+what was previously the "standard" style is supported.
By default and as you might expect, Jena models allow reification
quads to be manifested as `ReifiedStatement`s. Similarly,
Modified: jena/site/trunk/content/documentation/notes/sse.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/notes/sse.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/notes/sse.mdtext (original)
+++ jena/site/trunk/content/documentation/notes/sse.mdtext Mon Oct 23 02:32:48
2017
@@ -62,7 +62,7 @@ structures that operational meaning don'
no operations, no *push*, *pop* or *peek*.
Note that this is to *express* a data structure, not *encode* or
-*repressent* it. By *express* we mean communicate it, between people or
+*represent* it. By *express* 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.
@@ -133,7 +133,7 @@ SPARQL algebra for the query in SSE form
Tokens are the atomic elements of the syntax.
-| Example | Explaination |
+| Example | Explanation |
| -------------------------- | ------------ |
| `"abc"` | string
| `"abc"@en` | string with language tag.
@@ -328,7 +328,7 @@ The syntax of SSE is very close to Turtl
IRIs and literals are the same.: to produce Turtle (outline):
1. Replace symbols by IRIs: prepend a common URI and %-encode any
- characters necesary.
+ characters necessary.
2. Replace variables by IRIs: prepend a common URI.
3. Move prefixes to be `@prefix` directives.
4. Put a dot at the end of the file.
@@ -391,7 +391,7 @@ inline dataset and a query of
}
The tag `graph` is used twice, with different meanings. First, for an
-RDF graph, and second in `GRAPH` SPARQL pattern. In a data structrure,
+RDF graph, and second in `GRAPH` SPARQL pattern. In a data structure,
context sorts out the different usages.
(prefix ((: <http://example/>))
Modified: jena/site/trunk/content/documentation/notes/typed-literals.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/notes/typed-literals.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/notes/typed-literals.mdtext (original)
+++ jena/site/trunk/content/documentation/notes/typed-literals.mdtext Mon Oct
23 02:32:48 2017
@@ -319,7 +319,7 @@ rational numbers:
}
}
-To register and and use this type you simply need the call:
+To register and use this type you simply need the call:
RDFDatatype rtype = RationalType.theRationalType;
TypeMapper.getInstance().registerDatatype(rtype);
Modified: jena/site/trunk/content/documentation/ontology/index.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/ontology/index.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/ontology/index.mdtext (original)
+++ jena/site/trunk/content/documentation/ontology/index.mdtext Mon Oct 23
02:32:48 2017
@@ -560,7 +560,7 @@ language. In summary, these variants are
read( InputStream reader, String base, String Lang )
You can use any of these methods to load an ontology document. Note
-that we advise that you avoid the the `read()` variants that accept
+that we advise that you avoid the `read()` variants that accept
a `java.io.Reader` 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.
@@ -1448,7 +1448,7 @@ three classes as follows:
RDFList cs = m.createList( new RDFNode[] {c0, c1, c2} );
-Alternatively, we can build a list one element at at time:
+Alternatively, we can build a list one element at time:
OntModel m = ModelFactory.createOntModel();
RDFList cs = m.createList(); // Cs is empty
@@ -1645,7 +1645,7 @@ returned by the listClasses() iterator i
reasoner that can infer that any restriction is also be a class,
since `Restriction` is a subClassOf `Class`. This difference can be
exploited by the programmer: to list classes and restrictions
-separately, perform the `listClasses()` and `listRestictions()`
+separately, perform the `listClasses()` and `listRestrictions()`
methods on the base model only, or on a model with no reasoner
attached.
@@ -2016,4 +2016,4 @@ static methods. Currently available tool
path returns `true` to the `onPath` predicate.
- `List namedHierarchyRoots( OntModel m )`
Compute a list containing the uppermost fringe of the class
- hierarchy in the given model which consists only of named classes.
\ No newline at end of file
+ hierarchy in the given model which consists only of named classes.
Modified: jena/site/trunk/content/documentation/permissions/design.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/permissions/design.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/permissions/design.mdtext (original)
+++ jena/site/trunk/content/documentation/permissions/design.mdtext Mon Oct 23
02:32:48 2017
@@ -53,7 +53,7 @@ All secured objects return secured objec
All secured objects are defined as interfaces and are returned as dynamic
proxies.
-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.
+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.
Secured Listeners
-----------------
Modified: jena/site/trunk/content/documentation/permissions/evaluator.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/permissions/evaluator.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/permissions/evaluator.mdtext
(original)
+++ jena/site/trunk/content/documentation/permissions/evaluator.mdtext Mon Oct
23 02:32:48 2017
@@ -8,7 +8,7 @@ The SecurityEvaluator interface defines
### Actions
-Principals may perform Create, Read, Update or Delete operations on secured
resources. These operations are defined in the `Action` enum in the
SecurtyEvaluator interface.
+Principals may perform Create, Read, Update or Delete operations on secured
resources. These operations are defined in the `Action` enum in the
SecurityEvaluator interface.
### Node
@@ -20,7 +20,7 @@ The permission system introduces two new
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.
-The SecurityEvaluator must implement the following methods. Any of these
methods may throw an `AuthenticationRequriedException` if there is no
authenticated user.
+The SecurityEvaluator must implement the following methods. Any of these
methods may throw an `AuthenticationRequiredException` if there is no
authenticated user.
Most of these methods have a `principal` parameter. The value of that
parameter is guaranteed to be a value returned from an earlier calls to
getPrincipal(). The `principal` parameter, not the "current user" as identified
by `getPrincipal()`, should be used for the permissions evaluation.
Modified: jena/site/trunk/content/documentation/permissions/example.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/permissions/example.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/permissions/example.mdtext (original)
+++ jena/site/trunk/content/documentation/permissions/example.mdtext Mon Oct 23
02:32:48 2017
@@ -88,7 +88,7 @@ Load the SecuredAssembler class from the
perm:Model rdfs:subClassOf ja:NamedModel .
-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.
+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.
my:baseModel rdf:type ja:MemoryModel;
ja:content [ja:externalContent <file:./example.ttl>]
@@ -111,7 +111,7 @@ Define the security evaluator. This is w
perm:evaluatorClass
"org.apache.jena.permissions.example.ShiroExampleEvaluator" .
-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
+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.
my:securedDataset rdf:type ja:RDFDataset ;
@@ -120,7 +120,7 @@ unsecured models is supported.
Define the fuseki:Server.
- my:fuskei rdf:type fuseki:Server ;
+ my:fuseki rdf:type fuseki:Server ;
fuseki:services (
my:service1
) .
@@ -135,7 +135,7 @@ Define the service for the fuseki:Servic
fuseki:serviceUpdate "update" ; # SPARQL query service
fuseki:serviceUpload "upload" ; # Non-SPARQL upload
service
fuseki:serviceReadWriteGraphStore "data" ; # SPARQL Graph store
protocol (read and write)
- # A separate ead-only graph store endpoint:
+ # A separate read-only graph store endpoint:
fuseki:serviceReadGraphStore "get" ; # SPARQL Graph store
protocol (read only)
fuseki:dataset my:securedDataset ;
.
Modified: jena/site/trunk/content/documentation/query/algebra.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/algebra.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/algebra.mdtext (original)
+++ jena/site/trunk/content/documentation/query/algebra.mdtext Mon Oct 23
02:32:48 2017
@@ -13,7 +13,7 @@ algebra within ARQ. The definition of th
found in the SPARQL specification in
[section 12](http://www.w3.org/TR/sparql11-query/#sparqlDefinition).
[ARQ can be extended](arq-query-eval.html) to modify the evaluation
-of the algebra form to access difefrent graph storage
+of the algebra form to access different graph storage
implementations.
The classes for the datastructures for the algebra resize in the
@@ -51,7 +51,7 @@ And back again.
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
@@ -108,7 +108,7 @@ solutions (called Bindings).
}
qIter.close() ;
-Operations of `CONSTRUCT`, `DESCRIBE` and `ASK` are done on on top
+Operations of `CONSTRUCT`, `DESCRIBE` and `ASK` are done on top
of algebra evaluation. Applications can access this functionality
by creating their own `QueryEngine` (see
`arq.examples.engine.MyQueryEngine`) and it's factory. A query
Modified: jena/site/trunk/content/documentation/query/construct-quad.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/construct-quad.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/construct-quad.mdtext (original)
+++ jena/site/trunk/content/documentation/query/construct-quad.mdtext Mon Oct
23 02:32:48 2017
@@ -21,7 +21,7 @@ A `CONSTRUCT` template of the SPARQL 1.1
[Turtle](http://www.w3.org/TR/turtle/) format with possible variables. The
syntax for this extension follows that style in ARQ, using
[TriG](http://www.w3.org/TR/trig/) plus variables. Just like SPARQL 1.1,
-there're 2 forms for ARQ Contruct Quad query:
+there are 2 forms for ARQ Construct Quad query:
### Complete Form
@@ -80,8 +80,8 @@ One difference of the 2 methods is:
The method of `execConstructQuads()` returns an `Iterator` of `Quad`, allowing
duplication.
But `execConstructDataset()` constructs the desired Dataset object with only
unique `Quad`s.
-In order to use these methods, it's required to swtich on the query syntax
-of ARQ beforehead, when creating the `Query` object:
+In order to use these methods, it's required to switch on the query syntax
+of ARQ before head, when creating the `Query` object:
Query query = QueryFactory.create(queryString, Syntax.syntaxARQ);
@@ -107,11 +107,11 @@ More examples can be found at `ExampleCo
## Fuseki Support
-Jena [Fuseki](http://jena.apache.org/documentation/fuseki2/index.html) is also
empowed with Construct Quad query as a built-in
-function. No more addtional configuration is required to switch it on.
+Jena [Fuseki](http://jena.apache.org/documentation/fuseki2/index.html) is also
empowered with Construct Quad query as a built-in
+function. No more additional configuration is required to switch it on.
Because
[QueryEngineHTTP](http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/http/QueryEngineHTTP.html)
-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.
@@ -123,4 +123,4 @@ previous sections, e.g.
}
...
-[ARQ documentation index](index.html)
\ No newline at end of file
+[ARQ documentation index](index.html)
Modified: jena/site/trunk/content/documentation/query/custom_aggregates.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/custom_aggregates.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/custom_aggregates.mdtext
(original)
+++ jena/site/trunk/content/documentation/query/custom_aggregates.mdtext Mon
Oct 23 02:32:48 2017
@@ -1,5 +1,5 @@
Title: ARQ - Custom aggregates
-ARQ supports custom aggretate functions as allowed by teh SPARQL 1.1
specification.
+ARQ supports custom aggregate functions as allowed by the SPARQL 1.1
specification.
See [example
code](https://github.com/apache/jena/tree/master/jena-arq/src-examples/arq/examples/aggregates).
Modified: jena/site/trunk/content/documentation/query/explain.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/explain.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/explain.mdtext (original)
+++ jena/site/trunk/content/documentation/query/explain.mdtext Mon Oct 23
02:32:48 2017
@@ -14,7 +14,7 @@ optimization occurs such as choosing the
basic graph patterns.
The effect of [high-level optimizations](#algebra-transformations) can
-be seen using `arq.qparse` and the low-level runtime optimziations can
+be seen using `arq.qparse` and the low-level runtime optimizations can
be seen by [execution logging](#execution-logging).
## Algebra Transformations
@@ -76,7 +76,7 @@ globally:
and it may also be set on an individual query execution using it's local
context.
- try(QueryExecutiuon qExec = QueryExecutionFactory.create(...)) {
+ try(QueryExecution qExec = QueryExecutionFactory.create(...)) {
qExec.getContext().set(ARQ.symLogExec, Explain.InfoLevel.ALL)Â ;
ResultSet rs = qExec.execSelect() ;
...
Modified: jena/site/trunk/content/documentation/query/group-by.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/group-by.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/group-by.mdtext (original)
+++ jena/site/trunk/content/documentation/query/group-by.mdtext Mon Oct 23
02:32:48 2017
@@ -66,7 +66,7 @@ two names can refer to the same individu
If there was no explicit `GROUP BY` clause, then it is as if the
whole of the result set forms a single group element.Â
Equivalently, it is `GROUP BY` 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.
Modified: jena/site/trunk/content/documentation/query/http-auth.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/http-auth.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/http-auth.mdtext (original)
+++ jena/site/trunk/content/documentation/query/http-auth.mdtext Mon Oct 23
02:32:48 2017
@@ -16,7 +16,7 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-After [Jena 3.1.0](#http-authentication-from-jena-311), Jena exposes the
underlying HTTP Commons functionality to support a range of authentication
mechanisms as well as [other HTTP configuration][16]. From [Jena 3.0.0 through
Jena 3.1.0](#http-authentication-from-jena-300-through-310) 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.
+After [Jena 3.1.0](#http-authentication-from-jena-311), Jena exposes the
underlying HTTP Commons functionality to support a range of authentication
mechanisms as well as [other HTTP configuration][16]. From [Jena 3.0.0 through
Jena 3.1.0](#http-authentication-from-jena-300-through-310) 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.
## HTTP Authentication from Jena 3.1.1
@@ -241,4 +241,4 @@ ARQ allows the user to configure HTTP be
[15]:
https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/HttpClient.html
[16]: https://hc.apache.org/httpcomponents-client-ga/examples.html
[17]:
https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/protocol/HttpClientContext.html
- [18]:
https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/query/QueryExecutionFactory.html
\ No newline at end of file
+ [18]:
https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/query/QueryExecutionFactory.html
Modified: jena/site/trunk/content/documentation/query/library-function.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/library-function.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/library-function.mdtext
(original)
+++ jena/site/trunk/content/documentation/query/library-function.mdtext Mon Oct
23 02:32:48 2017
@@ -21,7 +21,7 @@ ARQ supports the scalar functions and op
Functions in involving sequences are not supported.
See [XSD Support](xsd-support.html) 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>[function/StandardFunctions.java](https://github.com/apache/jena/blob/master/jena-arq/src/main/java/org/apache/jena/sparql/function/StandardFunctions.java)</tt>.
See also the [property functions](library-propfunc.html) library
@@ -56,7 +56,7 @@ These are modelled after SQL aggregate f
These, as keywords, are available in ARQ's extended SPARQL (parse using
`Syntax.syntaxARQ`).
-### Addtional Functions Provided by ARQ
+### Additional Functions Provided by ARQ
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
Modified: jena/site/trunk/content/documentation/query/logging.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/logging.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/logging.mdtext (original)
+++ jena/site/trunk/content/documentation/query/logging.mdtext Mon Oct 23
02:32:48 2017
@@ -85,7 +85,7 @@ globally:
and it may also be set on an individual query execution using its local
context.
- try(QueryExecutiuon qExec = QueryExecutionFactory.create(...)) {
+ try(QueryExecution qExec = QueryExecutionFactory.create(...)) {
qExec.getContext().set(ARQ.symLogExec, Explain.InfoLevel.ALL)Â ;
...
}
Modified: jena/site/trunk/content/documentation/query/property_paths.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/property_paths.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/property_paths.mdtext (original)
+++ jena/site/trunk/content/documentation/query/property_paths.mdtext Mon Oct
23 02:32:48 2017
@@ -233,4 +233,4 @@ so the property function for `rdf:type`
PathLib.install(RDF.type.getURI(), path) ;
-[ARQ documentation index](index.html)
\ No newline at end of file
+[ARQ documentation index](index.html)
Modified: jena/site/trunk/content/documentation/query/service.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/service.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/service.mdtext (original)
+++ jena/site/trunk/content/documentation/query/service.mdtext Mon Oct 23
02:32:48 2017
@@ -10,7 +10,7 @@ results sent back (in RDF, or an
or even a [JSON one](http://www.w3.org/TR/rdf-sparql-json-res/)).
`SERVICE` is a feature of SPARQL 1.1 that allows an executing query to
-to make a SPARQL protocol to another SPARQL endopoint.
+to make a SPARQL protocol to another SPARQL endpoint.
## Syntax
@@ -108,14 +108,14 @@ Symbol | Usage
Set the connect and read timeouts for the query.
-If a timeout occurs a QueryExceptionHTTP is thrown. The cause of that
execption will be a java.net.SocketTimeoutException.
+If a timeout occurs a QueryExceptionHTTP is thrown. The cause of that
exception will be a java.net.SocketTimeoutException.
Number: number of milliseconds for connect timeout.
-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.
+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.
Connect timeout =0
-read timout = 0
+read timeout = 0
Values of 0 indicate no timeout and service operation will wait until the
remote server responds.
Modified: jena/site/trunk/content/documentation/query/spatial-query.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/spatial-query.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/spatial-query.mdtext (original)
+++ jena/site/trunk/content/documentation/query/spatial-query.mdtext Mon Oct 23
02:32:48 2017
@@ -61,7 +61,7 @@ This query makes a spatial query for the
#### Builtin Geo Predicates
-There're mainly 2 types of RDF representation of geo data, which are both
supported by jena-spatial:
+There are mainly 2 types of RDF representation of geo data, which are both
supported by jena-spatial:
**1) Latitude/Longitude Format (in gonames, DBPedia and Linked Geo Data)**
@@ -142,7 +142,7 @@ The prefix spatial is `<http://jena.apac
| Property name | Description |
|-------------------|--------------------------------|
-|*?place* **spatial:nearby** *(latitude, longitude, radius [, units,
limit])*<br>*?place* **spatial:withinCircle** *(latitude, longitude, radius [,
units, limit])*|Query for the *?place* within the *radius* distance of the
location of *(latitude, longitude)*. The distance *units* can be:
"kilometres"/"km", "miles"/"mi", "metres"/"m", "centimetres"/"cm",
"millimetres"/"mm" or "degrees"/"de", which are delivered as the optional
strings (the default value is "kilometres"). *limit* is an optional integer
parameter for the limit of the query results (if *limilt*<0, return all query
results).|
+|*?place* **spatial:nearby** *(latitude, longitude, radius [, units,
limit])*<br>*?place* **spatial:withinCircle** *(latitude, longitude, radius [,
units, limit])*|Query for the *?place* within the *radius* distance of the
location of *(latitude, longitude)*. The distance *units* can be:
"kilometres"/"km", "miles"/"mi", "metres"/"m", "centimetres"/"cm",
"millimetres"/"mm" or "degrees"/"de", which are delivered as the optional
strings (the default value is "kilometres"). *limit* is an optional integer
parameter for the limit of the query results (if *limit*<0, return all query
results).|
|*?place* **spatial:withinBox** *(latitude_min, longitude_min, latitude_max,
longitude_max [, limit])*|Query for the *?place* within the box area of
*(latitude_min, longitude_min, latitude_max, longitude_max)*.|
|*?place* **spatial:intersectBox** *(latitude_min, longitude_min,
latitude_max, longitude_max [, limit])*|Query for the *?place* intersecting the
box area of *(latitude_min, longitude_min, latitude_max, longitude_max)*.|
|*?place* **spatial:north** *(latitude, longitude [, limit])*|Query for the
*?place* northing the location of *(latitude, longitude)*.|
@@ -245,7 +245,7 @@ The fieldType of "entityField" is `strin
<fieldType name="string" class="solr.StrField" sortMissingLast="true" />
<fieldType name="location_rpt"
class="solr.SpatialRecursivePrefixTreeFieldType" geo="true" distErrPct="0.025"
maxDistErr="0.000009" units="degrees" />
-Addtionally, in `solrconfig.xml`, there should be 2 `requestHandlers` defined
for querying and updating the spatial data and the index.
+Additionally, in `solrconfig.xml`, there should be 2 `requestHandlers` defined
for querying and updating the spatial data and the index.
<requestHandler name="/select" class="solr.SearchHandler"></requestHandler>
<requestHandler name="/update"
class="solr.UpdateRequestHandler"></requestHandler>
@@ -253,7 +253,7 @@ Addtionally, in `solrconfig.xml`, there
The above is the least required configuration to run jena-spatial in Solr.
For more information about the configuration, please check the [Lucene / Solr
4 Spatial](http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4)
documentation.
-There're also some demostrations of the usage of Solr in the [unit
tests](https://github.com/apache/jena/tree/master/jena-spatial/src/test/java/org/apache/jena/query/spatial/pfunction/solr)
of jena-spatial.
+There are also some demonstrations of the usage of Solr in the [unit
tests](https://github.com/apache/jena/tree/master/jena-spatial/src/test/java/org/apache/jena/query/spatial/pfunction/solr)
of jena-spatial.
They use a `EmbeddedSolrServer`with a `SOLR_HOME` sample
[here](https://github.com/apache/jena/tree/master/jena-spatial/src/test/resources/SolrHome).
## Working with Fuseki
Modified: jena/site/trunk/content/documentation/query/text-query.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/text-query.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/text-query.mdtext (original)
+++ jena/site/trunk/content/documentation/query/text-query.mdtext Mon Oct 23
02:32:48 2017
@@ -284,7 +284,7 @@ The following is an example of a TDB dat
text:index <#indexLucene> ;
.
- # A TDB datset used for RDF storage
+ # A TDB dataset used for RDF storage
<#dataset> rdf:type tdb:DatasetTDB ;
tdb:location "DB" ;
tdb:unionDefaultGraph true ; # Optional
Modified: jena/site/trunk/content/documentation/query/update.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/update.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/update.mdtext (original)
+++ jena/site/trunk/content/documentation/query/update.mdtext Mon Oct 23
02:32:48 2017
@@ -14,7 +14,7 @@ download in src-examples/arq/examples/up
The main API classes are:
- UpdateRequest - A list of Update to be performed.
-- UpdateFactory - Create UpdateRequest objects by poarsing
+- UpdateFactory - Create UpdateRequest objects by parsing
strings or parsing the contents of a file.
- UpdateAction - execute updates
Modified: jena/site/trunk/content/documentation/query/writing_functions.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/writing_functions.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/writing_functions.mdtext
(original)
+++ jena/site/trunk/content/documentation/query/writing_functions.mdtext Mon
Oct 23 02:32:48 2017
@@ -92,7 +92,7 @@ The standard library, in package
The query compiler finds functions based on the functions URI.Â
There is a global registry of known functions, but any query
-execution can have it's own function registry.
+execution can have its own function registry.
For each function, there is a function factory associated with the
URI. A new function instance is created for each use of a function
Modified: jena/site/trunk/content/documentation/query/writing_propfuncs.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/writing_propfuncs.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/writing_propfuncs.mdtext
(original)
+++ jena/site/trunk/content/documentation/query/writing_propfuncs.mdtext Mon
Oct 23 02:32:48 2017
@@ -117,7 +117,7 @@ The implementation of a Property Functio
`Node` and `PropFuncArg` objects allow the developer to reflect on the state
of the arguments, and choose what
bindings to generate given the intended usage of the Property Function. For
example, if the function expects a
list of three bound arguments for the object of the property, then it can
throw a `ExprEvalException`
- (or derivative) to indicate incorrect use. It is the responsability of the
developer to identify what parts
+ (or derivative) to indicate incorrect use. It is the responsibility of the
developer to identify what parts
of the argument are bound, and to respond appropriately.
For example, if `?a ex:f ?b` were a triple pattern in a query, it could be
called with `?a` bound, `?b` bound,
@@ -166,4 +166,4 @@ New Triples or Graphs can therefore be c
//Create a new Graph in the Dataset, or overwrite an existing Named
Graph.
Graph newGraph = ...
//Add data to the newGraph as retaining empty Graphs is implementation
dependent.
- datasetGraph.addGraph(otherGraphNode, newGraph);
\ No newline at end of file
+ datasetGraph.addGraph(otherGraphNode, newGraph);
Modified: jena/site/trunk/content/documentation/rdf/datasets.md
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/rdf/datasets.md?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/rdf/datasets.md (original)
+++ jena/site/trunk/content/documentation/rdf/datasets.md Mon Oct 23 02:32:48
2017
@@ -42,7 +42,7 @@ changes are lost. The same happens if th
If used outside of a transaction, the implementation provides "auto-commit"
functionality. Each triple or added or deleted is done inside an implicit
-transaction. This have a measurable peformance impact. It is better to do
+transaction. This have a measurable performance impact. It is better to do
related operations inside a single transaction explicitly in the
application code.
Modified: jena/site/trunk/content/documentation/rdf/index.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/rdf/index.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/rdf/index.mdtext (original)
+++ jena/site/trunk/content/documentation/rdf/index.mdtext Mon Oct 23 02:32:48
2017
@@ -47,7 +47,7 @@ So if RDF information is contained in a
look like? There are two distinct types of nodes: URI references and literals.
Essentially, these
denote, respectively, some resource about which we wish to make some
assertions, and concrete data values that
appear in those assertions. In the example above, `example:ijd` is a resource,
denoting a person,
-and `"Ian"` denotes the value of a property of that resource (that propertly
being first name, in this case).
+and `"Ian"` denotes the value of a property of that resource (that property
being first name, in this case).
The resource is denoted by a URI, shown in abbreviated form here (about which
more below).
What is the nature of the relationship between the resource node in the graph
(`example:ijd`) and
@@ -159,7 +159,7 @@ are defined before use.
**Note**
Jena does not treat namespaces in a special way. A `Model` will remember any
prefixes defined
-in the input RDF (see the
[`PrexixMapping`](http://jena.apache.org/documentation/javadoc/jena/org/apache/jena/shared/PrefixMapping.html)
+in the input RDF (see the
[`PrefixMapping`](http://jena.apache.org/documentation/javadoc/jena/org/apache/jena/shared/PrefixMapping.html)
interface; all Jena `Model` objects extend `PrefixMapping`), and the output
writers which
serialize a model to XML or Turtle will normally attempt to use prefixes to
abbreviate URI's.
However internally, a `Resource` URI is not separated into a namespace and
local-name pair.
@@ -181,7 +181,7 @@ Package | Description | More information
oaj.jena.rdf.model | The Jena core. Creating and manipulating RDF graphs. |
oaj.riot | Reading and Writing RDF. |
oaj.jena.datatypes | Provides the core interfaces through which datatypes are
described to Jena.| [Typed
literals](http://jena.apache.org/documentation/notes/typed-literals.html)
-oaj.jena.ontology | Abstractions and convenience classes for accessing and
manipluating ontologies represented in RDF. | [Ontology
API](http://jena.apache.org/documentation/ontology/index.html)
+oaj.jena.ontology | Abstractions and convenience classes for accessing and
manipulating ontologies represented in RDF. | [Ontology
API](http://jena.apache.org/documentation/ontology/index.html)
oaj.jena.rdf.listeners | Listening for changes to the statements in a model |
oaj.jena.reasoner| The reasoner subsystem is supports a range of inference
engines which derive additional information from an RDF model | [Reasoner
how-to](http://jena.apache.org/documentation/inference/index.html)
oaj.jena.shared | Common utility classes |
Modified: jena/site/trunk/content/documentation/rdfconnection/index.md
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/rdfconnection/index.md?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/rdfconnection/index.md (original)
+++ jena/site/trunk/content/documentation/rdfconnection/index.md Mon Oct 23
02:32:48 2017
@@ -96,7 +96,7 @@ for the transaction body.
### Remote Transactions
SPARQL does not define a remote transaction standard protocol. Each remote
-operation shuld be atomic (all happens or nothing happens) - this is the
+operation should be atomic (all happens or nothing happens) - this is the
responsibility of the remote server.
An `RDFConnection` will at least provide the client-side locking features.
@@ -141,7 +141,7 @@ with local connections, 3 isolations mod
* Copy – the models and datasets returned are independent copies.
Updates are made to the return copy only. This is most like
-a remote connectionand is useful for testing.
+a remote connection and is useful for testing.
* Read-only – the models and datasets are made read-only but any changes
to the underlying RDF data by changes by another route will be visible.
This provides a form of checking for large datasets when "copy" is impractical.
@@ -158,7 +158,7 @@ in this mode.
`CONSTRUCT`, `DESCRIBE`, `ASK`) as well as a way to get the lower level
`QueryExecution` for specialized configuration.
-When creating an `QueryExecution` explicitly, care shoud be taken to close
+When creating an `QueryExecution` explicitly, care should be taken to close
it. If the application wishes to capture the result set from a SELECT query and
retain it across the lifetime of the transaction or `QueryExecution`, then
the application should create a copy which is not attached to any external
system
@@ -179,7 +179,7 @@ with `ResultSetFactory.copyResults`.
## Update Usage
-SPARQL Update opertions can be performed and mixed with other operations.
+SPARQL Update operations can be performed and mixed with other operations.
try ( RDFConnection conn = RDFConnectionFactory.connect(...) ) {
Txn.execWrite(conn, ()-> {
@@ -210,4 +210,4 @@ operations are visible to the called cod
## Examples
See
-<a
href="https://github.com/apache/jena/tree/master/jena-rdfconnection/src/main/java/org/apache/jena/rdfconnection/examples";>here</a>
for examples.
\ No newline at end of file
+<a
href="https://github.com/apache/jena/tree/master/jena-rdfconnection/src/main/java/org/apache/jena/rdfconnection/examples";>here</a>
for examples.
Modified: jena/site/trunk/content/documentation/sdb/commands.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/sdb/commands.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/sdb/commands.mdtext (original)
+++ jena/site/trunk/content/documentation/sdb/commands.mdtext Mon Oct 23
02:32:48 2017
@@ -29,7 +29,7 @@ over [Cygwin](http://www.cygwin.com/ "ht
### Script set up
-Set the environment variable `SDBROOT` to the root of the the SDB
+Set the environment variable `SDBROOT` to the root of the SDB
installation.
A store description can include naming the class for the JDBC
Modified: jena/site/trunk/content/documentation/sdb/configuration.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/sdb/configuration.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/sdb/configuration.mdtext (original)
+++ jena/site/trunk/content/documentation/sdb/configuration.mdtext Mon Oct 23
02:32:48 2017
@@ -20,7 +20,7 @@ Options can be set globally, through out
execution basis. SDB uses the same mechanism as
[ARQ](http://jena.sf.net/ARQ "http://jena.sf.net/ARQ";).
-There is a global context, which is give to each query query
+There is a global context, which is give to each query
execution as it is created. Modifications to the global context
after the query execution is created are not seen by the query
execution. Modifications to the context of a single query execution
Modified: jena/site/trunk/content/documentation/sdb/dataset_description.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/sdb/dataset_description.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/sdb/dataset_description.mdtext
(original)
+++ jena/site/trunk/content/documentation/sdb/dataset_description.mdtext Mon
Oct 23 02:32:48 2017
@@ -7,7 +7,7 @@ A dataset assembler just points to the s
assembler points to the store and identifies the model within the
store to use (or use the default model).
-## Datatsets
+## Datasets
The example below creates an in-memory store implemented by
HSQLDB.
@@ -54,8 +54,8 @@ the same SDB dataset, or to different on
interface enables different items to be picked out.
Note that creating a general (ARQ) dataset from models/graph inside
-an SDB store is not the same as using a datase which is the query
-interface to the store. It is the the dataset for the store that
+an SDB store is not the same as using a dataset which is the query
+interface to the store. It is the dataset for the store that
triggers full SPARQL to SQL translation, not a model.
Modified: jena/site/trunk/content/documentation/sdb/db_notes.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/sdb/db_notes.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/sdb/db_notes.mdtext (original)
+++ jena/site/trunk/content/documentation/sdb/db_notes.mdtext Mon Oct 23
02:32:48 2017
@@ -20,7 +20,7 @@ internationalization support).
### Loading Restriction
Only one load operation can be active at any one time. Limitations
-on temporary tables in Derby mean the the loader tables are not
+on temporary tables in Derby mean the loader tables are not
temporary and hence are shared by all connections.
## MS SQL
Modified: jena/site/trunk/content/documentation/sdb/javaapi.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/sdb/javaapi.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/sdb/javaapi.mdtext (original)
+++ jena/site/trunk/content/documentation/sdb/javaapi.mdtext Mon Oct 23
02:32:48 2017
@@ -229,7 +229,7 @@ then the query is not efficiently execut
A Jena model can be connected to one graph in the store and used
with all the Jena API operations.
-Here, the graph for the model is the the default graph:
+Here, the graph for the model is the default graph:
Store store = SDBFactory.connectStore("sdb.ttl")Â ;
Model model = SDBFactory.connectDefaultModel(store)Â ;
Modified: jena/site/trunk/content/documentation/sdb/loading_performance.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/sdb/loading_performance.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/sdb/loading_performance.mdtext
(original)
+++ jena/site/trunk/content/documentation/sdb/loading_performance.mdtext Mon
Oct 23 02:32:48 2017
@@ -69,7 +69,7 @@ the queries in SDB/PerfTests.
### LUBM
-LUBM generates artifical datasets. To be useful one needs to apply
+LUBM generates artificial datasets. To be useful one needs to apply
reasoning, and this was done in advance of loading. The queries are
quite stressful for SDB in that they are not very ground (in many
neither subjects nor objects are present), and many produce very
Modified: jena/site/trunk/content/documentation/serving_data/index.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/serving_data/index.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/serving_data/index.mdtext (original)
+++ jena/site/trunk/content/documentation/serving_data/index.mdtext Mon Oct 23
02:32:48 2017
@@ -34,7 +34,7 @@ Binaries for Fuseki1 are available from
[maven
repositories](http://central.maven.org/maven2/org/apache/jena/jena-fuseki1/).
-The source code is available in the Apache Jena soyrce release.
+The source code is available in the Apache Jena source release.
## Getting Started With Fuseki
@@ -364,7 +364,7 @@ Initially, the dataset is empty.
fuseki:serviceUpdate "update"Â ; # SPARQL query service
fuseki:serviceUpload "upload"Â ; # Non-SPARQL upload
service
fuseki:serviceReadWriteGraphStore "data"Â ; # SPARQL Graph store
protocol (read and write)
- # A separate ead-only graph store endpoint:
+ # A separate read-only graph store endpoint:
fuseki:serviceReadGraphStore "get"Â ; # SPARQL Graph store
protocol (read only)
fuseki:dataset <#dataset-mem>Â ;
.
