You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by an...@apache.org on 2015/07/14 14:51:41 UTC
svn commit: r1690917 [2/2] - in /jena/site/trunk/content: about_jena/
documentation/ documentation/csv/ documentation/hadoop/
documentation/inference/ documentation/io/ documentation/jdbc/
documentation/notes/ documentation/ontology/ documentation/quer...
Modified: jena/site/trunk/content/documentation/ontology/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/ontology/index.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/ontology/index.mdtext (original)
+++ jena/site/trunk/content/documentation/ontology/index.mdtext Tue Jul 14 12:51:40 2015
@@ -246,10 +246,10 @@ profile it is `null` since RDFS does not
The profile is bound to an *ontology model*, which is an extended
version of Jena's
-[`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) class.
+[`Model`](/documentation/javadoc/jena/org/apache/jena/rdf/model/Model.html) class.
The base `Model` allows access to the statements in a collection of
RDF data.
-[`OntModel`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntModel.html)
+[`OntModel`](/documentation/javadoc/jena/org/apache/jena/ontology/OntModel.html)
extends this by adding support for the kinds of constructs expected to
be in an ontology: classes (in a class hierarchy), properties (in a
property hierarchy) and individuals.
@@ -257,7 +257,7 @@ property hierarchy) and individuals.
When you're working with an
ontology in Jena, all of the state information remains encoded as
RDF triples (accessed as Jena
-[`Statement`s](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Statement.html)) stored in the RDF
+[`Statement`s](/documentation/javadoc/jena/org/apache/jena/rdf/model/Statement.html)) stored in the RDF
model. The ontology API
doesn't change the RDF representation of ontologies. What it does
do is add a set of convenience classes and methods that make it
@@ -369,7 +369,7 @@ resource is typed as an `owl:Class`, it
facet; given other types, it can present other facets. Jena
provides the `.as()` method to efficiently map from an RDF object
to one of its allowable facets. Given a RDF object (i.e. an
-instance of `com.hp.hpl.jena.rdf.model.RDFNode` or one of its
+instance of `org.apache.jena.rdf.model.RDFNode` or one of its
sub-types), you can get a facet by invoking `as()` with an argument
that denotes the facet required. Specifically, the facet is
identified by the Java class object of the desired facet. For
@@ -414,7 +414,7 @@ API throughout the rest of this document
An ontology model is an extension of the Jena RDF model,
providing extra capabilities for handling ontologies. Ontology
models are created through the Jena
-[`ModelFactory`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/ModelFactory.html).
+[`ModelFactory`](/documentation/javadoc/jena/org/apache/jena/rdf/model/ModelFactory.html).
The simplest way to create an ontology model is as follows:
OntModel m = ModelFactory.createOntologyModel();
@@ -455,7 +455,7 @@ OWL DL | `http://www.w3.org/TR/owl-featu
OWL Lite | `http://www.w3.org/TR/owl-features/#term_OWLLite`
These URI's are used to look-up the language profile from the
-[`ProfileRegistry`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/ProfileRegistry.html).
+[`ProfileRegistry`](/documentation/javadoc/jena/org/apache/jena/ontology/ProfileRegistry.html).
The profile registry contains public constant declarations so
that you do not have to remember these URI's. Please note that the
URI's denoting OWL Lite and OWL DL are not officially sanctioned by
@@ -463,7 +463,7 @@ the OWL standard.
Beyond these basic choices, the complexities of configuring an
ontology model are wrapped up in a recipe object called
-[`OntModelSpec`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntModelSpec.html).
+[`OntModelSpec`](/documentation/javadoc/jena/org/apache/jena/ontology/OntModelSpec.html).
This specification allows complete control over the configuration
choices for the ontology model, including the language profile in
use, the reasoner, and the means of handling compound documents. A
@@ -492,7 +492,7 @@ RDFS\_MEM\_RDFS\_INF | RDFS | in-memory
For details of reasoner capabilities, please see the
[inference documentation](../inference) and the Javadoc
for
-[OntModelSpec](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntModelSpec.html).
+[OntModelSpec](/documentation/javadoc/jena/org/apache/jena/ontology/OntModelSpec.html).
See also further discussion [below](#inference-intro).
**Note:** it is primarily the choice of reasoner, rather than the
@@ -674,7 +674,7 @@ a simple interface that allows different
on demand. For the database case, this may include passing the
database user-name and password and other connection parameters.
New model makers can be created with the
-[`ModelFactory`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/ModelFactory.html).
+[`ModelFactory`](/documentation/javadoc/jena/org/apache/jena/rdf/model/ModelFactory.html).
There are two cases in which we may want to create storage for
models on-demand. The first is when creating the `OntModel` for the
@@ -700,7 +700,7 @@ programming interface (`Model`) with a s
data structure (`Graph`). Hence some potential confusion in that
Figure 4, above, refers to a structure containing graphs, but we
use a
-[`ModelMaker`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/ModelMaker.html)
+[`ModelMaker`](/documentation/javadoc/jena/org/apache/jena/rdf/model/ModelMaker.html)
to generate new stores. The document manager extracts the
appropriate graph from the containing model. Except in cases where
you are extending Jena's internal structures, you should think of
@@ -731,7 +731,7 @@ fail just because it temporarily does no
because a previously published ontology has been moved.
To alleviate these commonly
experienced problems, we can use Jena's
-[`FileManager`](/documentation/javadoc/jena/com/hp/hpl/jena/util/FileManager.html) to
+[`FileManager`](/documentation/javadoc/jena/org/apache/jena/util/FileManager.html) to
manage local indirections, so that an attempt to import a
document from a given published URL means that a local copy of the
document is loaded instead. This may be a file on the local disk, or simply a
@@ -817,14 +817,14 @@ by calling `clearCache()`.
All of the classes in the ontology API that represent ontology
values have
-[`OntResource`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntResource.html)
+[`OntResource`](/documentation/javadoc/jena/org/apache/jena/ontology/OntResource.html)
as a common super-class. This makes `OntResource` a good place to
put shared functionality for all such classes, and makes a handy
common return value for general methods. The Java interface
`OntResource` extends Jena's RDF
-[`Resource`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Resource.html)
+[`Resource`](/documentation/javadoc/jena/org/apache/jena/rdf/model/Resource.html)
interface, so any general method that accepts a resource or an
-[`RDFNode`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFNode.html)
+[`RDFNode`](/documentation/javadoc/jena/org/apache/jena/rdf/model/RDFNode.html)
will also accept an `OntResource`, and consequently, any other
ontology value.
@@ -955,7 +955,7 @@ returned.
Classes are the basic building blocks of an ontology. A simple
class is represented in Jena by an
-[OntClass](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntClass.html)
+[OntClass](/documentation/javadoc/jena/org/apache/jena/ontology/OntClass.html)
object. As [mentioned above](#rdf-polymorphism), an ontology class
is a facet of an RDF resource. One way, therefore, to get an
ontology class is to convert a plain RDF resource into
@@ -1064,11 +1064,11 @@ properties represented in an ontology mo
A property in an ontology model is an extension of the core Jena
API class
-[`Property`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Property.html)
+[`Property`](/documentation/javadoc/jena/org/apache/jena/rdf/model/Property.html)
and allows access to the additional information that can be
asserted about properties in an ontology language. The common API
super-class for representing ontology properties in Java is
-[`OntProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntProperty.html).
+[`OntProperty`](/documentation/javadoc/jena/org/apache/jena/ontology/OntProperty.html).
Again, using the pattern of add, set, get, list, has, and remove
methods, we can access the following attributes of an
`OntProperty`:
@@ -1139,10 +1139,10 @@ entailments, and so is useful when annot
for example.
In Jena, the Java interfaces
-[`ObjectProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/ObjectProperty.html),
-[`DatatypeProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/DatatypeProperty.html)
+[`ObjectProperty`](/documentation/javadoc/jena/org/apache/jena/ontology/ObjectProperty.html),
+[`DatatypeProperty`](/documentation/javadoc/jena/org/apache/jena/ontology/DatatypeProperty.html)
and
-[`AnnotationProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/AnnotationProperty.html)
+[`AnnotationProperty`](/documentation/javadoc/jena/org/apache/jena/ontology/AnnotationProperty.html)
are sub-types of `OntProperty`. However, they do not have any
behaviours (methods) particular to themselves. Their existence
allows the more complex sub-types of ObjectProperty – transitive
@@ -1163,7 +1163,7 @@ equivalent to stating that the property
of one.
Being a functional property is represented through the
-[`FunctionalProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/FunctionalProperty.html)
+[`FunctionalProperty`](/documentation/javadoc/jena/org/apache/jena/ontology/FunctionalProperty.html)
facet of an ontology property object. If a property is declared
functional (test using the `isFunctional()` method), then the
method `asFunctionalProperty()` conveniently returns the functional property
@@ -1176,13 +1176,13 @@ parameter to the `createObjectProperty()
There are several additional sub-types of ObjectProperty that
represent additional capabilities of ontology properties. A
-[`TransitiveProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/TransitiveProperty.html)
+[`TransitiveProperty`](/documentation/javadoc/jena/org/apache/jena/ontology/TransitiveProperty.html)
means that if p is transitive, and we know `:a p :b` and also
`b p :c`, we can infer that `:a p :c`. A
-[`SymmetricProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/SymmetricProperty.html)
+[`SymmetricProperty`](/documentation/javadoc/jena/org/apache/jena/ontology/SymmetricProperty.html)
means that if p is symmetric, and we know `:a p :b`, we can infer
`:b p :a`. An
-[`InverseFunctionalProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/InverseFunctionalProperty.html)
+[`InverseFunctionalProperty`](/documentation/javadoc/jena/org/apache/jena/ontology/InverseFunctionalProperty.html)
means that for any given range element, the domain value is unique.
Given that all properties are `RDFNode` objects, and therefore
@@ -1235,7 +1235,7 @@ each in turn.
### Restriction class expressions
A
-[restriction](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/Restriction.html)
+[restriction](/documentation/javadoc/jena/org/apache/jena/ontology/Restriction.html)
defines a class by reference to one of the properties of the
individuals that comprise the members of the class, and then
placing some constraint on that property. For example, in a simple
@@ -1434,10 +1434,10 @@ is even more compact:
Although lists are defined in the generic RDF model in Jena, they
are extensively used by the ontology API so we mention them here.
Full details of the methods defined are in the
-[`RDFList javadoc`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFList.html).
+[`RDFList javadoc`](/documentation/javadoc/jena/org/apache/jena/rdf/model/RDFList.html).
Various means of constructing lists are defined in
-[`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html), as
+[`Model`](/documentation/javadoc/jena/org/apache/jena/rdf/model/Model.html), as
variants on `createList`. For example, we can construct a list of
three classes as follows:
@@ -1466,7 +1466,7 @@ Finally, a resource which is a cell in a
`.as( RDFList.class )`
Once the list has been created or obtained from the model,
-[`RDFList`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFList.html)
+[`RDFList`](/documentation/javadoc/jena/org/apache/jena/rdf/model/RDFList.html)
methods may be used to access members of the list, iterate over the
list, and so forth. For example:
@@ -1540,7 +1540,7 @@ that `m` is a model into which the ESWC
Union and intersection class expressions are very similar, so
Jena defines a common super-class
-[`BooleanClassDescription`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/BooleanClassDescription.html).
+[`BooleanClassDescription`](/documentation/javadoc/jena/org/apache/jena/ontology/BooleanClassDescription.html).
This class provides access to the *operands* to the expression. In
the intersection example above, the operands are the two restrictions. The
`BooleanClassDescription` class allows us to set the operands
@@ -1558,7 +1558,7 @@ class. Recall that a class is a set of i
to define the members of the *implicitly*: for example, "the class
of UK conferences". Sometimes it is convenient to define a class
*explicitly*, by stating the individuals the class contains. An
-[enumerated class](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/EnumeratedClass.html)
+[enumerated class](/documentation/javadoc/jena/org/apache/jena/ontology/EnumeratedClass.html)
is exactly the class whose members are the given individuals. For
example, we know that the class of PrimaryColours contains exactly
red, green and blue, and no others.
@@ -1596,7 +1596,7 @@ following:
An OWL `DataRange` is similar to an enumerated class, except that the members
of the `DataRange` are literal values, such as integers, dates or strings. See the
-[`DataRange` javadoc](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/DataRange.html)
+[`DataRange` javadoc](/documentation/javadoc/jena/org/apache/jena/ontology/DataRange.html)
for more details.
### Listing classes
@@ -1628,7 +1628,7 @@ get a list of named hierarchy root class
that lie closest to the top of the hierarchy (alternatively: the
shallowest fringe of the hierarchy consisting solely of named
classes), use the
-[OntTools](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntTools.html)
+[OntTools](/documentation/javadoc/jena/org/apache/jena/ontology/OntTools.html)
method `namedHierarchyRoots()`.
You should also note that it is important to close the iterators
@@ -1657,7 +1657,7 @@ declarations. In OWL Lite and DL, the la
instance data that the application is working with are kept
separate, by definition of the language. Jena therefore supports a
simple notion of an
-[`Individual`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/Individual.html),
+[`Individual`](/documentation/javadoc/jena/org/apache/jena/ontology/Individual.html),
which is essentially an alias for `Resource`. While `Individual`s
are largely synonymous with `Resource`s, they do provide an
programming interface that is consistent with the other Java
@@ -1709,7 +1709,7 @@ the *base URI* of the document containin
URI may be stated in the document through an `xml:base` declaration
in the XML preamble. The base URI can also be specified when
reading the document via Jena's Model API (see the `read()` methods
-on [`OntModel`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntModel.html)
+on [`OntModel`](/documentation/javadoc/jena/org/apache/jena/ontology/OntModel.html)
for reference).
We can attach various meta-data statements to this object to
@@ -1731,7 +1731,7 @@ version information.
In the Jena API, the ontology's metadata properties can be accessed
through the
-[`Ontology`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/Ontology.html)
+[`Ontology`](/documentation/javadoc/jena/org/apache/jena/ontology/Ontology.html)
interface. Suppose we wish to know the list of URI's that the
ontology imports. First we must obtain the resource representing the
ontology itself:
@@ -1767,7 +1767,7 @@ useful to list the ontology resources in
A common practice is also to use the Ontology element to attach
[Dublin Core metadata](http://dublincore.org/)
to the ontology document. Jena provides a copy
-of the Dublin Core vocabulary, in `com.hp.hpl.jena.vocabulary.DCTerms`.
+of the Dublin Core vocabulary, in `org.apache.jena.vocabulary.DCTerms`.
To attach a statement saying that the ontology was authored by John
Smith, we can say:
@@ -1834,7 +1834,7 @@ performance are.
The reasoner attached to an ontology model, if any, is specified
through the
-[`OntModelSpec`](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntModelSpec.html).
+[`OntModelSpec`](/documentation/javadoc/jena/org/apache/jena/ontology/OntModelSpec.html).
The methods `setReasoner()` and `setReasonerFactory()` on the model
spec are used to specify a reasoner. The setReasoner variant is
intended for use on a specification which will only be used to
@@ -1863,7 +1863,7 @@ considerably.
Jena's inference machinery defines some specialised services that
are not exposed through the addition of extra triples to the model.
These are exposed by the
-[`InfModel`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/InfModel.html)
+[`InfModel`](/documentation/javadoc/jena/org/apache/jena/rdf/model/InfModel.html)
interface; for convenience OntModel extends this interface to make
these services directly available to the user. Please note that
calling inference-specific methods on an ontology model that does
Modified: jena/site/trunk/content/documentation/query/algebra.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/algebra.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/algebra.mdtext (original)
+++ jena/site/trunk/content/documentation/query/algebra.mdtext Tue Jul 14 12:51:40 2015
@@ -17,7 +17,7 @@ of the algebra form to access difefrent
implementations.
The classes for the datastructures for the algebra resize in the
-package `com.hp.hpl.jena.sparql.algebra` in the `op` subpackage.Â
+package `org.apache.jena.sparql.algebra` in the `op` subpackage.Â
All the classes are names "`Op...`"; the interface that they all
offer is "`Op`".
@@ -68,7 +68,7 @@ even dataset and graphs.
Op op = SSE.readOp("filename.sse") ; // Read a file
The SSE class simply calls the appropriate builder operation from
-the `com.hp.hpl.jena.sparql.sse.builder` package.
+the `org.apache.jena.sparql.sse.builder` package.
To go with this, there is a collection of writers for many of the
Java structures in ARQ.Â
@@ -80,7 +80,7 @@ Writers default to writing to `System.ou
output stream (it manages the conversion to UTF-8) and ARQ own
`IndentedWriter`s form for embedding in structured output. Again,
SSE is simply passing the calls to the writer operation from the
-`com.hp.hpl.jena.sparql.sse.writer` package.
+`org.apache.jena.sparql.sse.writer` package.
## Creating an algebra expression programmatically
Modified: jena/site/trunk/content/documentation/query/app_api.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/app_api.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/app_api.mdtext (original)
+++ jena/site/trunk/content/documentation/query/app_api.mdtext Tue Jul 14 12:51:40 2015
@@ -1,6 +1,6 @@
Title: ARQ - Application API
-The application API is in the package `com.hp.hpl.jena.query`.
+The application API is in the package `org.apache.jena.query`.
Other packages contain various parts of the system (execution
engine, parsers, testing etc). Most applications will only need to
@@ -10,7 +10,7 @@ use the others packages directly.
## Key Classes
-The package `com.hp.hpl.jena.query` is the main application
+The package `org.apache.jena.query` is the main application
package.
- `Query` - a class that represents the application query. It is
@@ -38,7 +38,7 @@ of a query execution. `QueryExecution` o
and can be used in try-resource. Result are handled in a loop and finally the
query execution is closed.
- import com.hp.hpl.jena.query.* ;
+ import org.apache.jena.query.* ;
Model model = ... ;
String queryString = " .... " ;
Query query = QueryFactory.create(queryString) ;
@@ -70,7 +70,7 @@ following is also a way to process the r
The step of creating a query and then a query execution can be
reduced to one step in some common cases:
- import com.hp.hpl.jena.query.* ;
+ import org.apache.jena.query.* ;
Model model = ... ;
String queryString = " .... " ;
try (QueryExecution qexec = QueryExecutionFactory.create(queryString, model)) {
Modified: jena/site/trunk/content/documentation/query/architecture.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/architecture.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/architecture.mdtext (original)
+++ jena/site/trunk/content/documentation/query/architecture.mdtext Tue Jul 14 12:51:40 2015
@@ -26,15 +26,15 @@ ARQ consists of the following parts:
Package | Use
------- | ---
-`com.hp.hpl.jena.query` | The application API
-`com.hp.hpl.jena.sparql.syntax` | Abstract syntax tree
-`com.hp.hpl.jena.sparql.algebra`| SPARQL algebra
-`com.hp.hpl.jena.sparql.lang` | The parsers: SPARQL, ARQ, RDQL
-`com.hp.hpl.jena.sparql.expr` | Expression code.
-`com.hp.hpl.jena.sparql.serializer` | Output in SPARQL, ARQ forms, in SPARQL syntax, in an abstract form (useful in debugging) and in XML.
-`com.hp.hpl.jena.sparql.engine` | The abstraction of a query engine.
-`com.hp.hpl.jena.sparql.engine.main` | The usual query engine.
-`com.hp.hpl.jena.sparql.engine.ref` | The reference query engine (and quad version)
+`org.apache.jena.query` | The application API
+`org.apache.jena.sparql.syntax` | Abstract syntax tree
+`org.apache.jena.sparql.algebra`| SPARQL algebra
+`org.apache.jena.sparql.lang` | The parsers: SPARQL, ARQ, RDQL
+`org.apache.jena.sparql.expr` | Expression code.
+`org.apache.jena.sparql.serializer` | Output in SPARQL, ARQ forms, in SPARQL syntax, in an abstract form (useful in debugging) and in XML.
+`org.apache.jena.sparql.engine` | The abstraction of a query engine.
+`org.apache.jena.sparql.engine.main` | The usual query engine.
+`org.apache.jena.sparql.engine.ref` | The reference query engine (and quad version)
## Key Execution Classes
Modified: jena/site/trunk/content/documentation/query/explain.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/explain.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/explain.mdtext (original)
+++ jena/site/trunk/content/documentation/query/explain.mdtext Tue Jul 14 12:51:40 2015
@@ -62,11 +62,11 @@ Execution logging at level `ALL` can cau
query execution speeds but the order of operations logged will be
correct.
-The logger used is called `com.hp.hpl.jena.arq.exec`. Message are sent
+The logger used is called `org.apache.jena.arq.exec`. Message are sent
at level "info". So for log4j, the following can be set in the
log4j.properties file:
- log4j.logger.com.hp.hpl.jena.arq.exec=INFO
+ log4j.logger.org.apache.jena.arq.exec=INFO
The context setting is for key (Java constant) `ARQ.symLogExec`. To set
globally:
Modified: jena/site/trunk/content/documentation/query/extension.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/extension.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/extension.mdtext (original)
+++ jena/site/trunk/content/documentation/query/extension.mdtext Tue Jul 14 12:51:40 2015
@@ -115,7 +115,7 @@ ad localname parts to variables (if the
bound, not constants are used, `splitIRI` will check the values).
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
- PREFIX apf: <java:com.hp.hpl.jena.query.pfunction.library.>
+ PREFIX apf: <java:org.apache.jena.query.pfunction.library.>
SELECT ?namespace ?localname {
xsd:string apf:splitIRI (?namespace ?localname)
}
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=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/http-auth.mdtext (original)
+++ jena/site/trunk/content/documentation/query/http-auth.mdtext Tue Jul 14 12:51:40 2015
@@ -156,8 +156,8 @@ Note that the default authenticator may
[6]: http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/FormsAuthenticator.html
[7]: https://httpd.apache.org/docs/2.4/mod/mod_auth_form.html
[8]: http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/PreemptiveBasicAuthenticator.html
- [9]: http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.html
- [10]: http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/modify/UpdateProcessRemoteBase.html
+ [9]: http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/http/QueryEngineHTTP.html
+ [10]: http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/modify/UpdateProcessRemoteBase.html
[11]: http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/web/DatasetGraphAccessorHTTP.html
[12]: http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/DelegatingAuthenticator.html
[13]: http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/riot/web/HttpOp.html
Modified: jena/site/trunk/content/documentation/query/java-uri.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/java-uri.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/java-uri.mdtext (original)
+++ jena/site/trunk/content/documentation/query/java-uri.mdtext Tue Jul 14 12:51:40 2015
@@ -32,7 +32,7 @@ All code loading is performed via the `M
actually loading the code, the mapped loader applies any
transformation of URIs. For example, the ARQ function library has a
namespace of `<http://jena.hpl.hp.com/ARQ/function#>` and resides
-in the Java package com.hp.hpl.jena.sparql.function.library. The
+in the Java package org.apache.jena.sparql.function.library. The
mapped loader includes a partial rewrite rule turning http URLs
starting with that namespace into java: URIs using the package
name.
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=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/library-function.mdtext (original)
+++ jena/site/trunk/content/documentation/query/library-function.mdtext Tue Jul 14 12:51:40 2015
@@ -20,7 +20,7 @@ Applications can also
The prefix `afn` is `<http://jena.hpl.hp.com/ARQ/function#>`.
Direct loading using a URI prefix of
-`<java:com.hp.hpl.jena.sparql.function.library.>` (note the final
+`<java:org.apache.jena.sparql.function.library.>` (note the final
dot) is deprecated.
The prefix `fn` is `<http://www.w3.org/2005/xpath-functions#>` (the
Modified: jena/site/trunk/content/documentation/query/library-propfunc.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/library-propfunc.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/library-propfunc.mdtext (original)
+++ jena/site/trunk/content/documentation/query/library-propfunc.mdtext Tue Jul 14 12:51:40 2015
@@ -16,7 +16,7 @@ Applications can also [provide their own
Prefix `apf:` which is `<http://jena.hpl.hp.com/ARQ/property#>`.
Direct loading using a URI prefix of
-`<java:com.hp.hpl.jena.sparql.pfunction.library.>` (note the final
+`<java:org.apache.jena.sparql.pfunction.library.>` (note the final
dot) also works.
The prefix `list:` is `http://jena.hpl.hp.com/ARQ/list#`.
Modified: jena/site/trunk/content/documentation/query/logging.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/logging.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/logging.mdtext (original)
+++ jena/site/trunk/content/documentation/query/logging.mdtext Tue Jul 14 12:51:40 2015
@@ -13,9 +13,9 @@ normal operation. Output below INFO can
intended mainly to help debug ARQ. WARN and FATAL messages are only
used when something is wrong.
-The root of all the loggers is `com.hp.hpl.jena`.
-`com.hp.hpl.jena.query` is the application API.Â
-`com.hp.hpl.jena.sparql` is the implementation and extensions
+The root of all the loggers is `org.apache.jena`.
+`org.apache.jena.query` is the application API.Â
+`org.apache.jena.sparql` is the implementation and extensions
points.
If using in Tomcat, or other system that provides complex class
@@ -29,8 +29,8 @@ command execution.
Logger Names | Name | Constant | Logger | Use
------------ | ---- | -------- | ------ | ---
-`com.hp.hpl.jena.arq.info` | `ARQ.logInfoName` | `ARQ.getLoggerInfo()` | General information
-`com.hp.hpl.jena.arq.exec` | `ARQ.logExecName` | `ARQ.getLoggerExec()` | Execution information
+`org.apache.jena.arq.info` | `ARQ.logInfoName` | `ARQ.getLoggerInfo()` | General information
+`org.apache.jena.arq.exec` | `ARQ.logExecName` | `ARQ.getLoggerExec()` | Execution information
There is some code to cover simple situations. See the [log4j
documentation](http://logging.apache.org/log4j/1.2/manual.html)
@@ -49,11 +49,11 @@ Example log4j.properties file:
log4j.appender.stdlog.layout.ConversionPattern=%d{HH:mm:ss} %-5p %-25c{1} :: %m%n
# Execution logging
- log4j.logger.com.hp.hpl.jena.arq.info=INFO
- log4j.logger.com.hp.hpl.jena.arq.exec=INFO
+ log4j.logger.org.apache.jena.arq.info=INFO
+ log4j.logger.org.apache.jena.arq.exec=INFO
# Other
- log4j.logger.com.hp.hpl.jena=WARN
+ log4j.logger.org.apache.jena=WARN
log4j.logger.org.apache.jena=WARN
A [Fuseki](../serving/data/index.html)
@@ -71,11 +71,11 @@ logger level controls.
Explanatory messages are controlled by the `Explain.InfoLevel` level in
the execution context.
-The logger used is called `com.hp.hpl.jena.arq.exec`. Message are sent
+The logger used is called `org.apache.jena.arq.exec`. Message are sent
at level "info". So for log4j, the following can be set in the
log4j.properties file:
- log4j.logger.com.hp.hpl.jena.arq.exec=INFO
+ log4j.logger.org.apache.jena.arq.exec=INFO
The context setting is for key (Java constant) `ARQ.symLogExec`. To set
globally:
Modified: jena/site/trunk/content/documentation/query/parameterized-sparql-strings.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/parameterized-sparql-strings.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/parameterized-sparql-strings.mdtext (original)
+++ jena/site/trunk/content/documentation/query/parameterized-sparql-strings.mdtext Tue Jul 14 12:51:40 2015
@@ -68,7 +68,7 @@ Note that the state of the instance retu
does is check that your command is not subject to SPARQL injection attacks so in some cases where a possible
injection is detected an `ARQException` will be thrown.
-[1]: http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/query/ParameterizedSparqlString.html
+[1]: http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/query/ParameterizedSparqlString.html
### Injecting Values
Modified: jena/site/trunk/content/documentation/query/sparql-remote.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/sparql-remote.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/sparql-remote.mdtext (original)
+++ jena/site/trunk/content/documentation/query/sparql-remote.mdtext Tue Jul 14 12:51:40 2015
@@ -19,7 +19,7 @@ The `QueryExecutionFactory` has methods
`QueryExecutionFactory.sparqlService`
These methods build a query execution object that uses the query
-engine in `com.hp.hpl.jena.sparql.engine.http`.
+engine in `org.apache.jena.sparql.engine.http`.
The remote request is made when the `execSelect`, `execConstruct`,
`execDescribe` or `execAsk` method is called.
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=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/spatial-query.mdtext (original)
+++ jena/site/trunk/content/documentation/query/spatial-query.mdtext Tue Jul 14 12:51:40 2015
@@ -177,7 +177,7 @@ The following is an example of a TDB dat
@prefix spatial: <http://jena.apache.org/spatial#> .
# TDB
- [] ja:loadClass "com.hp.hpl.jena.tdb.TDB" .
+ [] ja:loadClass "org.apache.jena.tdb.TDB" .
tdb:DatasetTDB rdfs:subClassOf ja:RDFDataset .
tdb:GraphTDB rdfs:subClassOf ja:Model .
Modified: jena/site/trunk/content/documentation/query/support_request.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/support_request.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/support_request.mdtext (original)
+++ jena/site/trunk/content/documentation/query/support_request.mdtext Tue Jul 14 12:51:40 2015
@@ -22,7 +22,7 @@ If you are reporting a failure that prod
include the message, exception and the stack trace. Only if it is
very long, should you truncate the trace but please include the
whole trace to the point where it indicates it is entering ARQ (a
-package name starting `com.hp.hpl.jena.query`) and then one level
+package name starting `org.apache.jena.query`) and then one level
which is your code.
### Unexpected results
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=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/text-query.mdtext (original)
+++ jena/site/trunk/content/documentation/query/text-query.mdtext Tue Jul 14 12:51:40 2015
@@ -184,7 +184,7 @@ The following is an example of a TDB dat
## Example of a TDB dataset and text index
## Initialize TDB
- [] ja:loadClass "com.hp.hpl.jena.tdb.TDB" .
+ [] ja:loadClass "org.apache.jena.tdb.TDB" .
tdb:DatasetTDB rdfs:subClassOf ja:RDFDataset .
tdb:GraphTDB rdfs:subClassOf ja:Model .
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=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/writing_functions.mdtext (original)
+++ jena/site/trunk/content/documentation/query/writing_functions.mdtext Tue Jul 14 12:51:40 2015
@@ -12,10 +12,10 @@ language that allows URI to name a funct
processor.
In the ARQ engine, code to implement function must implement the
-interface `com.hp.hpl.jena.sparql.function.Function` although it is
+interface `org.apache.jena.sparql.function.Function` although it is
easier to work with one of the abstract classes for specific
numbers of arguments like
-`com.hp.hpl.jena.sparql.function.FunctionBase1` for one argument
+`org.apache.jena.sparql.function.FunctionBase1` for one argument
functions. Functions do not have to have a fixed number of
arguments.
@@ -86,7 +86,7 @@ This throws an evaluation exception if i
not a URI.
The standard library, in package
-`com.hp.hpl.jena.sparql.function.library`, contains many examples.
+`org.apache.jena.sparql.function.library`, contains many examples.
## Registering Functions
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=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/writing_propfuncs.mdtext (original)
+++ jena/site/trunk/content/documentation/query/writing_propfuncs.mdtext Tue Jul 14 12:51:40 2015
@@ -21,7 +21,7 @@ Notice: Licensed to the Apache Softwa
See also [Writing Filter Functions](writing_functions.html).
Applications can add SPARQL property functions to the query engine. This is done by first implementing the
- [`PropertyFunction`](http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/pfunction/PropertyFunction.html)
+ [`PropertyFunction`](http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropertyFunction.html)
interface, and then either registering that function or using the fake `java:` URI scheme to dynamically
load the function.
@@ -32,7 +32,7 @@ Similar to SPARQL Filter Functions, a SP
generate new bindings.
Just like
- [com.hp.hpl.jena.sparql.function.Function](http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/function/Function.html)
+ [org.apache.jena.sparql.function.Function](http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/function/Function.html)
there are various utility classes provided to simplify the creation of a Property Function. The selection of
one depends on the 'style' of the desired built-in. For example, `PFuncSimple` is expected to be the predicate
of triple patterns `?such ex:as ?this`, where neither argument is an `rdf:list`, and either may be a variable.
@@ -54,8 +54,8 @@ Just like
The choice of extension point determines the function signature that the developer will need to implement, and
primarily determines whether some of the arguments will be
- [`com.hp.hpl.jena.graph.Node`](https://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/graph/Node.html)s or
- [`com.hp.hpl.jena.sparql.pfunction.PropFuncArg`](http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/pfunction/PropFuncArg.html)s.
+ [`org.apache.jena.graph.Node`](https://jena.apache.org/documentation/javadoc/jena/org/apache/jena/graph/Node.html)s or
+ [`org.apache.jena.sparql.pfunction.PropFuncArg`](http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropFuncArg.html)s.
In the latter case, the programmer can determine whether the argument is a list as well as how many
arguments it consists of.
@@ -63,13 +63,13 @@ The choice of extension point determines
**Registration**
Every property function is associated with a particular
- [`com.hp.hpl.jena.sparql.util.Context`](http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/util/Context.html).
+ [`org.apache.jena.sparql.util.Context`](http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/util/Context.html).
This allows you to limit the availability of the function to be global or associated with a particular dataset.
For example, a custom Property Function may expose an index which only has meaning with respect to some set
of data.
Assuming you have an implementation of
- [`com.hp.hpl.jena.sparql.pfunction.PropertyFunctionFactory`](http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/pfunction/PropertyFunctionFactory.html)
+ [`org.apache.jena.sparql.pfunction.PropertyFunctionFactory`](http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropertyFunctionFactory.html)
(shown later), you can register a function as follows:
@@ -86,7 +86,7 @@ The only difference between global and d
PropertyFunctionRegistry.set(ds.getContext(), reg);
Note that
- [`com.hp.hpl.jena.sparql.pfunction.PropertyFunctionRegistry`](http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/pfunction/PropertyFunctionRegistry.html)
+ [`org.apache.jena.sparql.pfunction.PropertyFunctionRegistry`](http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropertyFunctionRegistry.html)
has other `put` methods that allow registration by passing a `Class` object, as well.
**Implementation**
@@ -127,14 +127,14 @@ easy to support typical use cases.
Of particular note:
- - [`QueryIterNullIterator`](https://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/engine/iterator/QueryIterNullIterator.html) - to indicate that there are no valid solutions/bindings for the given values
- - [`QueryIterSingleton`](https://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/engine/iterator/QueryIterSingleton.html) - to provide a single solution/binding for the given values
- - [`QueryIterPlainWrapper`](http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/engine/iterator/QueryIterPlainWrapper.html) - to provide multiple solutions/bindings for the given values
+ - [`QueryIterNullIterator`](https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/iterator/QueryIterNullIterator.html) - to indicate that there are no valid solutions/bindings for the given values
+ - [`QueryIterSingleton`](https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/iterator/QueryIterSingleton.html) - to provide a single solution/binding for the given values
+ - [`QueryIterPlainWrapper`](http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/iterator/QueryIterPlainWrapper.html) - to provide multiple solutions/bindings for the given values
The second two cases require instances of `Binding` objects which can be obtained through static methods of
- [`BindingFactory`](http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/engine/binding/BindingFactory.html).
- Creation of `Binding` objects will also require references to [`Var`](https://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/core/Var.html)
- and [`NodeFactory`](https://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/graph/NodeFactory.html)
+ [`BindingFactory`](http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/binding/BindingFactory.html).
+ Creation of `Binding` objects will also require references to [`Var`](https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/core/Var.html)
+ and [`NodeFactory`](https://jena.apache.org/documentation/javadoc/jena/org/apache/jena/graph/NodeFactory.html)
Note that it can make a lot of sense to generate the `Iterator<Binding>` for `QueryIterPlainWrapper` by means of
Jena's `ExtendedIterator`. This can allow domain-specific value to be easily mapped to `Binding` objects in
Modified: jena/site/trunk/content/documentation/rdf/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/rdf/index.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/rdf/index.mdtext (original)
+++ jena/site/trunk/content/documentation/rdf/index.mdtext Tue Jul 14 12:51:40 2015
@@ -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/com/hp/hpl/jena/shared/PrefixMapping.html)
+in the input RDF (see the [`PrexixMapping`](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.
@@ -174,22 +174,17 @@ of that resource, as above, but also as
## Jena packages
As a guide to the various features of Jena, here's a description of the main Java packages.
-For brevity, we shorten `com.hp.hpl` to `chh` and `org.apache.jena` to `oaj`.
-
-**Important note** At some future point, now that Jena has become a project under the Apache
-Software Foundation, the package names beginning `com.hpl.hpl` will change to `org.apache`.
-We will provide transition packages to help Jena users adapt to this
-change when it occurs.
+For brevity, we shorten `org.apache.jena` to `oaj`.
Package | Description | More information
------- | ----------- | ----------------
-chh.jena.rdf.model | The Jena core. Creating and manipulating RDF graphs. |
+oaj.jena.rdf.model | The Jena core. Creating and manipulating RDF graphs. |
oaj.riot | Reading and Writing RDF. |
-chh.jena.datatypes | Provides the core interfaces through which datatypes are described to Jena.| [Typed literals](http://jena.apache.org/documentation/notes/typed-literals.html)
-chh.jena.ontology | Abstractions and convenience classes for accessing and manipluating ontologies represented in RDF. | [Ontology API](http://jena.apache.org/documentation/ontology/index.html)
-chh.jena.rdf.listeners | Listening for changes to the statements in a model |
-chh.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)
-chh.jena.shared | Common utility classes |
-chh.jena.vocabulary | A package containing constant classes with predefined constant objects for classes and properties defined in well known vocabularies. |
+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.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 |
+oaj.jena.vocabulary | A package containing constant classes with predefined constant objects for classes and properties defined in well known vocabularies. |
-chh.jena.xmloutput | Writing RDF/XML. | [I/O index](http://jena.apache.org/documentation/io/index.html)
+oaj.jena.xmloutput | Writing RDF/XML. | [I/O index](http://jena.apache.org/documentation/io/index.html)
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=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/sdb/dataset_description.mdtext (original)
+++ jena/site/trunk/content/documentation/sdb/dataset_description.mdtext Tue Jul 14 12:51:40 2015
@@ -19,7 +19,7 @@ HSQLDB.
@prefix ja: <http://jena.hpl.hp.com/2005/11/Assembler#> .
@prefix sdb: <http://jena.hpl.hp.com/2007/sdb#> .
- [] ja:loadClass "com.hp.hpl.jena.sdb.SDB" .
+ [] ja:loadClass "org.apache.jena.sdb.SDB" .
sdb:DatasetStore rdfs:subClassOf ja:RDFDataset .
Modified: jena/site/trunk/content/documentation/sdb/fuseki_integration.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/sdb/fuseki_integration.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/sdb/fuseki_integration.mdtext (original)
+++ jena/site/trunk/content/documentation/sdb/fuseki_integration.mdtext Tue Jul 14 12:51:40 2015
@@ -9,7 +9,7 @@ Fuseki configuration file needs to conta
SDB:
## Initialize SDB.
- [] ja:loadClass "com.hp.hpl.jena.sdb.SDB" .
+ [] ja:loadClass "org.apache.jena.sdb.SDB" .
## Declare that sdb:DatasetStore is an implementation of ja:RDFDataset .
sdb:DatasetStore rdfs:subClassOf ja:RDFDataset .
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=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/serving_data/index.mdtext (original)
+++ jena/site/trunk/content/documentation/serving_data/index.mdtext Tue Jul 14 12:51:40 2015
@@ -232,7 +232,7 @@ and a database in the directory DB, an a
@prefix ja: <http://jena.hpl.hp.com/2005/11/Assembler#> .
@prefix tdb: <http://jena.hpl.hp.com/2008/tdb#> .
- [] ja:loadClass "com.hp.hpl.jena.tdb.TDB" .
+ [] ja:loadClass "org.apache.jena.tdb.TDB" .
tdb:DatasetTDB rdfs:subClassOf ja:RDFDataset .
tdb:GraphTDB rdfs:subClassOf ja:Model .
@@ -344,7 +344,7 @@ objects. Set up any assembler extensions
support.
# Declaration additional assembler items.
- [] ja:loadClass "com.hp.hpl.jena.tdb.TDB" .
+ [] ja:loadClass "org.apache.jena.tdb.TDB" .
# TDB
tdb:DatasetTDB rdfs:subClassOf ja:RDFDataset .
Modified: jena/site/trunk/content/documentation/tdb/assembler.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/assembler.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/assembler.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/assembler.mdtext Tue Jul 14 12:51:40 2015
@@ -33,7 +33,7 @@ A dataset can be constructed in an assem
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix ja: <http://jena.hpl.hp.com/2005/11/Assembler#> .
- [] ja:loadClass "com.hp.hpl.jena.tdb.TDB" .
+ [] ja:loadClass "org.apache.jena.tdb.TDB" .
tdb:DatasetTDB rdfs:subClassOf ja:RDFDataset .
tdb:GraphTDB rdfs:subClassOf ja:Model .
@@ -60,7 +60,7 @@ this case the jena assembler system chec
statements before any attempt to assemble an object is made, having
it early in the file is helpful to any person looking at the file.
- [] ja:loadClass "com.hp.hpl.jena.tdb.TDB" .
+ [] ja:loadClass "org.apache.jena.tdb.TDB" .
And finally there is the description of the TDB dataset itself:
@@ -99,7 +99,7 @@ A single graph from a TDB dataset can be
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ja: <http://jena.hpl.hp.com/2005/11/Assembler#> .
- [] ja:loadClass "com.hp.hpl.jena.tdb.TDB" .
+ [] ja:loadClass "org.apache.jena.tdb.TDB" .
<#dataset> rdf:type tdb:DatasetTDBÂ ;
tdb:location "DB"Â ;
@@ -129,7 +129,7 @@ below:
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix ja: <http://jena.hpl.hp.com/2005/11/Assembler#> .
- [] ja:loadClass "com.hp.hpl.jena.tdb.TDB" .
+ [] ja:loadClass "org.apache.jena.tdb.TDB" .
tdb:DatasetTDB rdfs:subClassOf ja:RDFDataset .
tdb:GraphTDB rdfs:subClassOf ja:Model .
Modified: jena/site/trunk/content/documentation/tdb/configuration.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/configuration.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/configuration.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/configuration.mdtext Tue Jul 14 12:51:40 2015
@@ -68,7 +68,7 @@ See [TDB/Datasets](datasets.html "TDB/Da
## Logging Query Execution
If the symbol "`tdb:logExec`" is set to "true", and also the logger
-`com.hp.hpl.jena.tdb.exec` is enabled fro level "info", then each
+`org.apache.jena.tdb.exec` is enabled fro level "info", then each
basic graph patterns is logged before execution. This pattern
logged is after substitution of variable values and after
optimization by the
@@ -100,7 +100,7 @@ Configuration Symbols
Symbol | Java Constant | Effect | Default
------ | ------------- | ------ | -------
-`tdb:logExec` | `TDB.symLogExec` | Log execution of BGPs. Set to "true" to enable. Must also enable the logger "com.hp.hpl.jena.tdb.exec". e.g. log4j.properties `log4j.logger.com.hp.hpl.jena.tdb.exec=INFO` | unset
+`tdb:logExec` | `TDB.symLogExec` | Log execution of BGPs. Set to "true" to enable. Must also enable the logger "org.apache.jena.tdb.exec". e.g. log4j.properties `log4j.logger.org.apache.jena.tdb.exec=INFO` | unset
`tdb:unionDefaultGraph` | `TDB.symUnionDefaultGraph` | Query patterns on the default graph match against the union of the named graphs. | unset
`tdb:fileMode` | `SystemTDB.fileMode` | Force use of memory mapped files (`"mapped"`) or direct file caching (`"direct"`). See discussion of TDB on 32 or 64 bit hardware, especially limitations of memory mapped files on 32 bit Java. | Set by the system based on 32 or 64 bit java.
Modified: jena/site/trunk/content/documentation/tdb/optimizer.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/optimizer.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/optimizer.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/optimizer.mdtext Tue Jul 14 12:51:40 2015
@@ -88,17 +88,17 @@ TDB can optionally log query execution d
by two setting: the logging level and a context setting. Having two
setting means it is possible to log some queries and not others.
-The logger used is called `com.hp.hpl.jena.arq.exec`. Message are
+The logger used is called `org.apache.jena.arq.exec`. Message are
sent at level "info". So for log4j, the following can be set in the
log4j.properties file:
# Execution logging
- log4j.logger.com.hp.hpl.jena.arq.info=WARN
- log4j.logger.com.hp.hpl.jena.arq.exec=WARN
+ log4j.logger.org.apache.jena.arq.info=WARN
+ log4j.logger.org.apache.jena.arq.exec=WARN
In versions of TDB before 0.8.7, this is:
- log4j.logger.com.hp.hpl.jena.tdb.exec=INFO
+ log4j.logger.org.apache.jena.tdb.exec=INFO
The context setting is for key (Java constant) `ARQ.symLogExec`. To
set globally:
@@ -160,9 +160,9 @@ the query execution.
log4j.appender.stdlog.layout=org.apache.log4j.PatternLayout
log4j.appender.stdlog.layout.ConversionPattern=%d{HH:mm:ss} %-5p %-25c{1} :: %m%n
# the query execution logger
- log4j.logger.com.hp.hpl.jena.arq.exec=INFO
+ log4j.logger.org.apache.jena.arq.exec=INFO
-It is important to create a `log4j.logger.com.hp.hpl.jena.arq.exec` logger,
+It is important to create a `log4j.logger.org.apache.jena.arq.exec` logger,
as otherwise the command won't output the query execution details.
The command output will be similar to this one.
Modified: jena/site/trunk/content/documentation/tools/schemagen.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tools/schemagen.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tools/schemagen.mdtext (original)
+++ jena/site/trunk/content/documentation/tools/schemagen.mdtext Tue Jul 14 12:51:40 2015
@@ -116,7 +116,7 @@ to produce the following generated class
/* CVS $Id: schemagen.html,v 1.16 2010-06-11 00:08:23 ian_dickinson Exp $ */
- import com.hp.hpl.jena.rdf.model.*;
+ import org.apache.jena.rdf.model.*;
/**
* Vocabulary definitions from deputy.rdf
@@ -165,8 +165,8 @@ to get:
/* CVs $Id: schemagen.html,v 1.16 2010-06-11 00:08:23 ian_dickinson Exp $ */
- import com.hp.hpl.jena.rdf.model.*;
- import com.hp.hpl.jena.ontology.*;
+ import org.apache.jena.rdf.model.*;
+ import org.apache.jena.ontology.*;
/**
* Vocabulary definitions from deputy.rdf
* @author Auto-generated by schemagen on 01 May 2003 22:03
Modified: jena/site/trunk/content/tutorials/rdf_api.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/rdf_api.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/rdf_api.mdtext (original)
+++ jena/site/trunk/content/tutorials/rdf_api.mdtext Tue Jul 14 12:51:40 2015
@@ -610,7 +610,7 @@ adding a whole group of mappings at once
<p>Jena is a Java API for semantic web applications. The key RDF package for
the application developer is
-<code>com.hp.hpl.jena.rdf.model</code>. The API has been defined
+<code>org.apache.jena.rdf.model</code>. The API has been defined
in terms of interfaces so that application code can work with different
implementations without change. This package contains interfaces for
representing models, resources, properties, literals, statements and all the
@@ -619,10 +619,10 @@ application code remains independent of
the implementation, it is best if it uses interfaces wherever possible, not
specific class implementations.</p>
-<p>The <code>com.hp.hpl.jena.tutorial</code> package contains the
+<p>The <code>org.apache.jena.tutorial</code> package contains the
working source code for all the examples used in this tutorial.</p>
-<p>The <code>com.hp.hpl.jena...impl</code> packages contains
+<p>The <code>org.apache.jena...impl</code> packages contains
implementation classes which may be common to many implementations. For
example, they defines classes <code>ResourceImpl</code>,
<code>PropertyImpl</code>, and <code>LiteralImpl</code> which may be
@@ -782,7 +782,7 @@ method <code>model.listStatements(Select
iterator over all the statements in the model 'selected' by <code>s</code>.
The selector interface is designed to be extensible, but for now, there is
only one implementation of it, the class <code>SimpleSelector</code> from the
-package <code>com.hp.hpl.jena.rdf.model</code>. Using
+package <code>org.apache.jena.rdf.model</code>. Using
<code>SimpleSelector </code>is one of the rare occasions in Jena when it is
necessary to use a specific class rather than an interface. The
<code>SimpleSelector</code> constructor takes three arguments:</p>
@@ -984,9 +984,9 @@ should be reasonably clear that the Mode
intersection and difference of the Models can be computed in a similar
manner, using the methods <code>.intersection(Model)</code> and
<code>.difference(Model)</code>; see the
-<a href="/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#difference(com.hp.hpl.jena.rdf.model.Model)">difference</a>
+<a href="/documentation/javadoc/jena/org/apache/jena/rdf/model/Model.html#difference(org.apache.jena.rdf.model.Model)">difference</a>
and
-<a href="/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#intersection(com.hp.hpl.jena.rdf.model.Model)">intersection</a>
+<a href="/documentation/javadoc/jena/org/apache/jena/rdf/model/Model.html#intersection(org.apache.jena.rdf.model.Model)">intersection</a>
Javadocs for more details.
</p>
Modified: jena/site/trunk/content/tutorials/rdf_api_pt.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/rdf_api_pt.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/rdf_api_pt.mdtext (original)
+++ jena/site/trunk/content/tutorials/rdf_api_pt.mdtext Tue Jul 14 12:51:40 2015
@@ -464,11 +464,11 @@ Você verá que os prefixos da entra
<h2 id="ch-Jena RDF Packages">Pacotes Jena RDF</h2>
<p>Jena é uma API JAVA para aplicações de web semântica. O pacote RDF chave para o desenvolvedor é
-<code>com.hp.hpl.jena.rdf.model</code>. A API tem sido definida em termos de interfaces, logo o código da aplicação pode trabalhar com diferentes implementações sem causar mudanças. Esse pacote contém interfaces para representar modelos, recursos, propriedades, literais, sentenças e todos os outros conceitos chaves de RDF, e um ModelFactory para criação de modelos. Portanto, o código da aplicação permanece independente da implementação, o melhor é usar interfaces onde for possÃvel e não implementações especÃficas de classes.</p>
+<code>org.apache.jena.rdf.model</code>. A API tem sido definida em termos de interfaces, logo o código da aplicação pode trabalhar com diferentes implementações sem causar mudanças. Esse pacote contém interfaces para representar modelos, recursos, propriedades, literais, sentenças e todos os outros conceitos chaves de RDF, e um ModelFactory para criação de modelos. Portanto, o código da aplicação permanece independente da implementação, o melhor é usar interfaces onde for possÃvel e não implementações especÃficas de classes.</p>
-<p>O pacote <code>com.hp.hpl.jena.tutorial</code> contém o código fonte funcional de todos os exemplos usados neste tutorial.</p>
+<p>O pacote <code>org.apache.jena.tutorial</code> contém o código fonte funcional de todos os exemplos usados neste tutorial.</p>
-<p>Os pacotes <code>com.hp.hpl.jena...impl</code> contêm a implementação de classes que podem ser comuns a várias implementações. Por exemplo, eles definem as classes <code>ResourceImpl</code>,
+<p>Os pacotes <code>org.apache.jena...impl</code> contêm a implementação de classes que podem ser comuns a várias implementações. Por exemplo, eles definem as classes <code>ResourceImpl</code>,
<code>PropertyImpl</code>, e <code>LiteralImpl</code> que podem ser usadas diretamente ou então herdadas por diferentes implementações. As aplicações devem raramente usar essas classes diretamente. Por exemplo, em vez de criar um nova instância de <code>ResourceImpl</code>, é melhor usar o método <code>createResource</code> do modelo que estiver sendo usado. Desta forma, se a implementação do modelo usar uma implementação otimizada de <code>Resource</code>, então não serão necessárias conversões entre os dois tipos.</p>
@@ -566,7 +566,7 @@ while (iter.hasNext()) {
}</code></pre>
</blockquote>
-<p>Todos esses métodos de consulta são acuçar sintático sobre o método primitivo de consulta <code>model.listStatements(Selector s)</code>. Esse método retorna um iterador sobre todas as sentenças no modelo 'selecionado' por <code>s</code>. A interface de selector foi feita para ser extensÃvel, mas por hora, só há uma implementação dela, a classe <code>SimpleSelector</code> do pacote <code>com.hp.hpl.jena.rdf.model</code>. Usar <code>SimpleSelector </code> é uma das raras ocasiões em Jena onde é necessário usar uma classe especifica em vez de uma interface. O construtor de <code>SimpleSelector</code> recebe três argumentos:</p>
+<p>Todos esses métodos de consulta são acuçar sintático sobre o método primitivo de consulta <code>model.listStatements(Selector s)</code>. Esse método retorna um iterador sobre todas as sentenças no modelo 'selecionado' por <code>s</code>. A interface de selector foi feita para ser extensÃvel, mas por hora, só há uma implementação dela, a classe <code>SimpleSelector</code> do pacote <code>org.apache.jena.rdf.model</code>. Usar <code>SimpleSelector </code> é uma das raras ocasiões em Jena onde é necessário usar uma classe especifica em vez de uma interface. O construtor de <code>SimpleSelector</code> recebe três argumentos:</p>
<blockquote>
<pre><code>Selector selector = new SimpleSelector(subject, predicate, object)
@@ -740,9 +740,9 @@ model.write(system.out, "RDF/XML-ABBREV"
<p>Mesmo que você não seja familiarizado com os detalhes da sintaxe RDF/XML, deve ser relativamente claro que os modelos foram unidos como esperado A interseção e a diferença de modelos podem ser computados de maneira semelhante, usando os métodos <code>.intersection(Model)</code> e
<code>.difference(Model)</code>; veja a documentação de
-<a href="/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#difference(com.hp.hpl.jena.rdf.model.Model)">difference</a>
+<a href="/documentation/javadoc/jena/org/apache/jena/rdf/model/Model.html#difference(org.apache.jena.rdf.model.Model)">difference</a>
e
-<a href "/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#intersection(com.hp.hpl.jena.rdf.model.Model)">intersection</a>
+<a href "/documentation/javadoc/jena/org/apache/jena/rdf/model/Model.html#intersection(org.apache.jena.rdf.model.Model)">intersection</a>
para mais detalhes.
</p>
Modified: jena/site/trunk/content/tutorials/using_jena_with_eclipse_pt.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/using_jena_with_eclipse_pt.mdtext?rev=1690917&r1=1690916&r2=1690917&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/using_jena_with_eclipse_pt.mdtext (original)
+++ jena/site/trunk/content/tutorials/using_jena_with_eclipse_pt.mdtext Tue Jul 14 12:51:40 2015
@@ -126,7 +126,7 @@ O código de Java fica em arquivos que
OK, agora vamos escrever algum código em Jena.
A primeira coisa que eu precisarei para trabalhar é um `Model` (modelo):
um container para comandos RDF. A classe `Model` está no pacote (*package*)
- `com.hp.hpl.jena.rdf.model`, então primeiro eu irei importar (*import*) a
+ `org.apache.jena.rdf.model`, então primeiro eu irei importar (*import*) a
classe e só então criar uma instância dela.
<p align="center">
@@ -135,7 +135,7 @@ classe e só então criar uma instÃ
Certo, então por que o código está sublinhando em vermelho? Este é o jeito do
Eclipse de indicar que existe um problema no código. Se eu tentasse compilar
este código usando `javac` na linha de comando, eu receberia uma mensagem de
- erro dizendo que o pacote `com.hp.hpl.jena.rdf.model` não pôde ser encontrado,
+ erro dizendo que o pacote `org.apache.jena.rdf.model` não pôde ser encontrado,
e que a classe `Model` não foi definida. Na linha de comando, eu consertaria
isto configurando o `Java classpath`. Essencialmente, isso é o que eu faço no
Eclipse também, mas o Eclipse torna isto muito mais fácil. Note que eu não