You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by ca...@apache.org on 2012/05/13 20:52:45 UTC
svn commit: r1337964 - in /jena/site/trunk/content: about_jena/
documentation/ documentation/io/ documentation/notes/
documentation/ontology/ documentation/query/ documentation/rdf/
documentation/sdb/ documentation/serving_data/ documentation/tdb/ docu...
Author: castagna
Date: Sun May 13 18:52:44 2012
New Revision: 1337964
URL: http://svn.apache.org/viewvc?rev=1337964&view=rev
Log:
JENA-245
Modified:
jena/site/trunk/content/about_jena/architecture.mdtext
jena/site/trunk/content/about_jena/index.mdtext
jena/site/trunk/content/documentation/index.mdtext
jena/site/trunk/content/documentation/io/iohowto.mdtext
jena/site/trunk/content/documentation/io/sax.mdtext
jena/site/trunk/content/documentation/io/standalone.mdtext
jena/site/trunk/content/documentation/notes/concurrency-howto.mdtext
jena/site/trunk/content/documentation/notes/file-manager.mdtext
jena/site/trunk/content/documentation/notes/model-factory.mdtext
jena/site/trunk/content/documentation/notes/typed-literals.mdtext
jena/site/trunk/content/documentation/ontology/index.mdtext
jena/site/trunk/content/documentation/query/download.mdtext
jena/site/trunk/content/documentation/query/index.mdtext
jena/site/trunk/content/documentation/rdf/index.mdtext
jena/site/trunk/content/documentation/sdb/commands.mdtext
jena/site/trunk/content/documentation/sdb/index.mdtext
jena/site/trunk/content/documentation/serving_data/index.mdtext
jena/site/trunk/content/documentation/serving_data/soh.mdtext
jena/site/trunk/content/documentation/tdb/assembler.mdtext
jena/site/trunk/content/documentation/tdb/tdb_download.mdtext
jena/site/trunk/content/documentation/tools/eyeball-getting-started.mdtext
jena/site/trunk/content/documentation/tools/eyeball-manual.mdtext
jena/site/trunk/content/getting_started/fuseki.mdtext
jena/site/trunk/content/getting_started/index.mdtext
jena/site/trunk/content/getting_started/rdf_api.mdtext
jena/site/trunk/content/getting_started/sparql.mdtext
jena/site/trunk/content/tutorials/index.mdtext
jena/site/trunk/content/tutorials/sparql.mdtext
jena/site/trunk/content/tutorials/sparql_data.mdtext
jena/site/trunk/content/tutorials/sparql_query1.mdtext
Modified: jena/site/trunk/content/about_jena/architecture.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/about_jena/architecture.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/about_jena/architecture.mdtext (original)
+++ jena/site/trunk/content/about_jena/architecture.mdtext Sun May 13 18:52:44 2012
@@ -10,7 +10,7 @@ your code to add, remove, manipulate, st
tend to think of Jena as a number of major subsystems with clearly
defined interfaces between them. First let's start with the big picture:
-
+
RDF triples and graphs, and their various components, are accessed through Jena's
RDF API. Typical abstractions here are <code>Resource</code> representing an
Modified: jena/site/trunk/content/about_jena/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/about_jena/index.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/about_jena/index.mdtext (original)
+++ jena/site/trunk/content/about_jena/index.mdtext Sun May 13 18:52:44 2012
@@ -26,13 +26,13 @@ was approved as a top-level Apache proje
## Quick shortcuts
I would like to ...
-* ... [download Jena components](/jena/download/index.html)
-* ... [use Jena with Maven](/jena/download/maven.html)
-* ... [find out more about the Jena project](/jena/about_jena/about.html)
-* ... [see who's involved](/jena/about_jena/team.html)
-* ... [follow a tutorial](/jena/tutorials/index.html)
-* ... [see how to get started with Jena](/jena/getting_started/index.html)
-* ... [report a bug](/jena/help_and_support/bugs_and_suggestions.html)
-* ... [get help using Jena](/jena/help_and_support/index.html)
-* ... [read the Javadoc](/jena/documentation/javadoc/)
-* ... [contribute to the project!](/jena/getting_involved/index.html)
+* ... [download Jena components](/download/index.html)
+* ... [use Jena with Maven](/download/maven.html)
+* ... [find out more about the Jena project](/about_jena/about.html)
+* ... [see who's involved](/about_jena/team.html)
+* ... [follow a tutorial](/tutorials/index.html)
+* ... [see how to get started with Jena](/getting_started/index.html)
+* ... [report a bug](/help_and_support/bugs_and_suggestions.html)
+* ... [get help using Jena](/help_and_support/index.html)
+* ... [read the Javadoc](/documentation/javadoc/)
+* ... [contribute to the project!](/getting_involved/index.html)
Modified: jena/site/trunk/content/documentation/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/index.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/index.mdtext (original)
+++ jena/site/trunk/content/documentation/index.mdtext Sun May 13 18:52:44 2012
@@ -2,7 +2,7 @@ Title: Jena documentation overview
This section contains detailed information about the various Jena
sub-systems, aimed at developers using Jena. For more general introductions,
-please refer to the [Getting started](/jena/getting_started) and [Tutorial](/jena/tutorials)
+please refer to the [Getting started](/getting_started) and [Tutorial](/tutorials)
sections.
##Documentation index
Modified: jena/site/trunk/content/documentation/io/iohowto.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/io/iohowto.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/io/iohowto.mdtext (original)
+++ jena/site/trunk/content/documentation/io/iohowto.mdtext Sun May 13 18:52:44 2012
@@ -32,20 +32,20 @@ See [the RIOT documentation](riot.html)
The main I/O methods in Jena use `InputStream`s and `OutputStream`s.
These methods are found on the
-[`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) interface.
+[`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) interface.
These are:
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`read`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.io.InputStream, java.lang.String))`(java.io.InputStream in, java.lang.String base)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`read`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.io.InputStream, java.lang.String))`(java.io.InputStream in, java.lang.String base)`
<br />Add statements from an RDF/XML serialization
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`read`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.io.InputStream, java.lang.String, java.lang.String))`(java.io.InputStream in, java.lang.String base, java.lang.String lang)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`read`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.io.InputStream, java.lang.String, java.lang.String))`(java.io.InputStream in, java.lang.String base, java.lang.String lang)`
<br /> Add RDF statements represented in language `lang` to the model.
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`read`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.lang.String))`(java.lang.String url)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`read`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.lang.String))`(java.lang.String url)`
<br />Add the RDF statements from an XML document.
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.OutputStream))`(java.io.OutputStream out)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.OutputStream))`(java.io.OutputStream out)`
<br /> Write the model as an XML document.
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.OutputStream, java.lang.String))`(java.io.OutputStream out, java.lang.String lang)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.OutputStream, java.lang.String))`(java.io.OutputStream out, java.lang.String lang)`
<br />Write a serialized representation of a model in a specified language.
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.OutputStream, java.lang.String, java.lang.String))`(java.io.OutputStream out, java.lang.String lang, java.lang.String base)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.OutputStream, java.lang.String, java.lang.String))`(java.io.OutputStream out, java.lang.String lang, java.lang.String base)`
<br />Write a serialized representation of a model in a specified language.
The built-in languages are `"RDF/XML"`, `"RDF/XML-ABBREV"`,
@@ -59,9 +59,9 @@ applications, they are useful, see [belo
there is every intention to continue to support them. The RDF/XML
parser now checks to see if the `Model.read(Reader â¦)` calls
are being abused, and issues
-[`ERR_ENCODING_MISMATCH`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#ERR_ENCODING_MISMATCH)
+[`ERR_ENCODING_MISMATCH`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#ERR_ENCODING_MISMATCH)
and
-[`WARN_ENCODING_MISMATCH`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#WARN_ENCODING_MISMATCH)
+[`WARN_ENCODING_MISMATCH`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#WARN_ENCODING_MISMATCH)
errors. Most incorrect usage of `Reader`s for RDF/XML input will
result in such errors. Most incorrect usage of `Writer`s for RDF/XML
output will produce correct XML by using an appropriate XML
@@ -216,15 +216,15 @@ These do not need to be encoded and deco
does not need to be specified. Other examples are when an advanced
user explicitly wishes to correctly control the encoding.
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`read`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.io.Reader, java.lang.String))`(java.io.Reader reader, java.lang.String base)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`read`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.io.Reader, java.lang.String))`(java.io.Reader reader, java.lang.String base)`
<br />Using this method is often a mistake.
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`read`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.io.Reader, java.lang.String, java.lang.String))`(java.io.Reader reader, java.lang.String base, java.lang.String lang)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`read`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.io.Reader, java.lang.String, java.lang.String))`(java.io.Reader reader, java.lang.String base, java.lang.String lang)`
<br />Using this method is often a mistake.
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.Writer))`(java.io.Writer writer)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.Writer))`(java.io.Writer writer)`
<br />Caution! Write the model as an XML document.
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.Writer, java.lang.String))`(java.io.Writer writer, java.lang.String lang)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.Writer, java.lang.String))`(java.io.Writer writer, java.lang.String lang)`
<br /> Caution! Write a serialized representation of a model in a specified language.
-- [`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.Writer, java.lang.String, java.lang.String))`(java.io.Writer writer, java.lang.String lang, java.lang.String base)`
+- [`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) [`write`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#write(java.io.Writer, java.lang.String, java.lang.String))`(java.io.Writer writer, java.lang.String lang, java.lang.String base)`
<br /> Caution! Write a serialized representation of a model in a specified language.
Incorrect use of these `read(Reader, â¦)` methods results in
@@ -261,32 +261,32 @@ above.
The four vital calls in the `Model` interface are:
-- [`RDFReader`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
-[`getReader`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReaderF.html#getReader())`()`
+- [`RDFReader`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
+[`getReader`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReaderF.html#getReader())`()`
<br />Return an RDFReader instance for the default serialization language.
-- [`RDFReader`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
-[`getReader`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReaderF.html#getReader(java.lang.String))`(java.lang.String lang)`
+- [`RDFReader`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
+[`getReader`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReaderF.html#getReader(java.lang.String))`(java.lang.String lang)`
<br />Return an RDFReader instance for the specified serialization language.
-- [`RDFReader`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
-[`getWriter`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFWriterF.html#getWriter())`()`
+- [`RDFReader`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
+[`getWriter`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFWriterF.html#getWriter())`()`
<br />Return an RDFWriter instance for the default serialization language.
-- [`RDFReader`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
-[`getWriter`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFWriterF.html#getWriter(java.lang.String))`(java.lang.String lang)`
+- [`RDFReader`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
+[`getWriter`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFWriterF.html#getWriter(java.lang.String))`(java.lang.String lang)`
<br />An RDFWriter instance for the specified serialization language.
Each of these calls returns an `RDFReader` or `RDFWriter` that can be
used to read or write any `Model` (not just the one which created
it). As well as the necessary
-[`read`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html#read(com.hp.hpl.jena.rdf.model.Model, java.io.InputStream, java.lang.String))
+[`read`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html#read(com.hp.hpl.jena.rdf.model.Model, java.io.InputStream, java.lang.String))
and
-[`write`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFWriter.html#write(com.hp.hpl.jena.rdf.model.Model, java.io.OutputStream, java.lang.String))
+[`write`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFWriter.html#write(com.hp.hpl.jena.rdf.model.Model, java.io.OutputStream, java.lang.String))
methods, these interfaces provide:
-- [`RDFErrorHandler`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFErrorHandler.html)
-[`setErrorHandler`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html#setErrorHandler(com.hp.hpl.jena.rdf.model.RDFErrorHandler))`(` [RDFErrorHandler](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFErrorHandler.html) `errHandler )`
+- [`RDFErrorHandler`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFErrorHandler.html)
+[`setErrorHandler`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html#setErrorHandler(com.hp.hpl.jena.rdf.model.RDFErrorHandler))`(` [RDFErrorHandler](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFErrorHandler.html) `errHandler )`
<br />Set an error handler for the reader
- `java.lang.Object`
-[`setProperty`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html#setProperty(java.lang.String, java.lang.Object))`(java.lang.String propName, java.lang.Object propValue)`
+[`setProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html#setProperty(java.lang.String, java.lang.Object))`(java.lang.String propName, java.lang.Object propValue)`
<br />Set the value of a reader property.
Setting properties, or the error handler, on an `RDFReader` or an
@@ -331,17 +331,17 @@ For RDF/XML and RDF/XML-ABBREV, there ar
`RDFReader` and the `RDFWriter`. N3 has options on the `RDFWriter`. These
options are detailed below. For RDF/XML they are also found in the
JavaDoc for
-`JenaReader.`[`setProperty`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/JenaReader.html#setProperty(java.lang.String, java.lang.Object))`(String, Object)`
+`JenaReader.`[`setProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/JenaReader.html#setProperty(java.lang.String, java.lang.Object))`(String, Object)`
and
-`RDFXMLWriterI.`[`setProperty`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/xmloutput/RDFXMLWriterI.html#setProperty(java.lang.String, java.lang.Object))`(String, Object)`.
+`RDFXMLWriterI.`[`setProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/xmloutput/RDFXMLWriterI.html#setProperty(java.lang.String, java.lang.Object))`(String, Object)`.
## Advanced RDF/XML Input
For access to these advanced features, first get an `RDFReader`
object that is an instance of an ARP parser, by using the
-[`getReader`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReaderF.html#getReader())`()`
+[`getReader`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReaderF.html#getReader())`()`
method on any `Model`. It is then configured using the
-[`setProperty`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/JenaReader.html#setProperty(java.lang.String, java.lang.Object))`(String, Object)`
+[`setProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/JenaReader.html#setProperty(java.lang.String, java.lang.Object))`(String, Object)`
method. This changes the properties for parsing RDF/XML. Many of
the properties change the RDF parser, some change the XML parser.
(The Jena RDF/XML parser, ARP, implements the
@@ -350,7 +350,7 @@ over a [Xerces2-J](http://xml.apache.org
parser). However, changing the features and properties of the XML
parser is not likely to be useful, but was easy to implement.
-[`setProperty`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/JenaReader.html#setProperty(java.lang.String, java.lang.Object))`(String, Object)`
+[`setProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/JenaReader.html#setProperty(java.lang.String, java.lang.Object))`(String, Object)`
can be used to set and get:
- ARP properties
@@ -381,9 +381,9 @@ ARP property names and string values are
Property Name | Description | Value class | Legal Values
------------- | ----------- | ----------- | ------------
`iri-rules` | Set the engine for checking and resolving. `"strict"` sets the IRI engine with rules for valid IRIs, XLink and RDF; it does not permit spaces in IRIs. `"iri"`sets the IRI engine to IRI ([RFC 3986](http://www.ietf.org/rfc/rfc3986.txt), [RFC 3987](http://www.ietf.org/rfc/rfc3987.txt)) `.` The default is `"lax"`(for backwards compatibility)`,` the rules for RDF URI references only, which does permit spaces although the use of spaces is not good practice. | String | `lax`<br />`strict`<br />`iri`
-`error-mode`| [`ARPOptions.setDefaultErrorMode()`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setDefaultErrorMode()) <br />[`ARPOptions.setLaxErrorMode()`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setLaxErrorMode())<br />[`ARPOptions.setStrictErrorMode()`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setStrictErrorMode())<br />[`ARPOptions.setStrictErrorMode(int)`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setStrictErrorMode(int))<br /> This allows a coarse-grained approach to control of error handling. Setting this property is equivalent to setting many of the fine-grained error handling properties. | `String` | `default`<br />`lax`<br />`strict`<br />`strict-ignore`<br />`strict-warning`<br />`strict-error`<br />`strict-fatal`
-`embedding` | [`ARPOptions.setEmbedding(boolean)`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setEmbedding(boolean)) <br />This sets ARP to look for RDF embedded within an enclosing XML document. | `String` or `Boolean` | `true`<br />`false`
-`ERR_<XXX>` <br />`WARN_<XXX>`<br />`IGN_<XXX>` | See [`ARPErrorNumbers`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html) for a complete list of the error conditions detected. Setting one of these properties is equivalent to the method [`ARPOptions.setErrorMode(int, int)`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setErrorMode(int,%20int)). Thus fine-grained control over the behaviour in response to specific error conditions is possible.| `String` or `Integer` | [`EM_IGNORE`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#EM_IGNORE)<br />[`EM_WARNING`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#EM_WARNING)<br />[`EM_ERROR`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#EM_ERROR)<br />[`EM_FATAL`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#EM_FATAL)
+`error-mode`| [`ARPOptions.setDefaultErrorMode()`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setDefaultErrorMode()) <br />[`ARPOptions.setLaxErrorMode()`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setLaxErrorMode())<br />[`ARPOptions.setStrictErrorMode()`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setStrictErrorMode())<br />[`ARPOptions.setStrictErrorMode(int)`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setStrictErrorMode(int))<br /> This allows a coarse-grained approach to control of error handling. Setting this property is equivalent to setting many of the fine-grained error handling properties. | `String` | `default`<br />`lax`<br />`strict`<br />`strict-ignore`<br />`strict-warning`<br />`strict-error`<br />`strict-fatal`
+`embedding` | [`ARPOptions.setEmbedding(boolean)`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setEmbedding(boolean)) <br />This sets ARP to look for RDF embedded within an enclosing XML document. | `String` or `Boolean` | `true`<br />`false`
+`ERR_<XXX>` <br />`WARN_<XXX>`<br />`IGN_<XXX>` | See [`ARPErrorNumbers`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html) for a complete list of the error conditions detected. Setting one of these properties is equivalent to the method [`ARPOptions.setErrorMode(int, int)`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html#setErrorMode(int,%20int)). Thus fine-grained control over the behaviour in response to specific error conditions is possible.| `String` or `Integer` | [`EM_IGNORE`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#EM_IGNORE)<br />[`EM_WARNING`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#EM_WARNING)<br />[`EM_ERROR`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#EM_ERROR)<br />[`EM_FATAL`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#EM_FATAL)
As an example, if you are working in an environment with legacy RDF
data that uses unqualified RDF attributes such as "about" instead
@@ -418,7 +418,7 @@ The other way round does not work.
â¦
This is because in strict mode
-[`IGN_DAML_COLLECTION`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#IGN_DAML_COLLECTION)
+[`IGN_DAML_COLLECTION`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#IGN_DAML_COLLECTION)
is treated as an error, and so the second call to `setProperty`
overwrites the effect of the first.
@@ -446,7 +446,7 @@ or other IRI rule engine from `IRIFactor
ARP can be interrupted using the `Thread.interrupt()` method. This
causes an
-[`ERR_INTERRUPTED`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#ERR_INTERRUPTED)
+[`ERR_INTERRUPTED`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPErrorNumbers.html#ERR_INTERRUPTED)
error during the parse, which is usually treated as a fatal error.
Here is an illustrative code sample:
@@ -481,11 +481,11 @@ more readable XML.
For access to advanced features, first get an RDFWriter object, of
the appropriate language, by using
-[`getWriter`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFWriterF.html#getWriter(java.lang.String))`("RDF/XML")`
+[`getWriter`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFWriterF.html#getWriter(java.lang.String))`("RDF/XML")`
or
-[`getWriter`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFWriterF.html#getWriter(java.lang.String))`("RDF/XML-ABBREV")`
+[`getWriter`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFWriterF.html#getWriter(java.lang.String))`("RDF/XML-ABBREV")`
on any `Model`. It is then configured using the
-[`setProperty`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/JenaReader.html#setProperty(java.lang.String, java.lang.Object))`(String, Object)`
+[`setProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/JenaReader.html#setProperty(java.lang.String, java.lang.Object))`(String, Object)`
method. This changes the properties for writing RDF/XML.
### Properties to Control RDF/XML Output
@@ -580,22 +580,22 @@ fragment IDs from [http://www.w3.org/TR/
indicating grammar rules that will not be used. Rules that can be blocked are:
- [section-Reification](http://www.w3.org/TR/rdf-syntax-grammar#section-Reification)
- ([`RDFSyntax.sectionReification`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#sectionReification))
+ ([`RDFSyntax.sectionReification`](/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#sectionReification))
- [section-List-Expand](http://www.w3.org/TR/rdf-syntax-grammar#section-List-Expand)
- ([`RDFSyntax.sectionListExpand`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#sectionListExpand))
+ ([`RDFSyntax.sectionListExpand`](/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#sectionListExpand))
- [parseTypeLiteralPropertyElt](http://www.w3.org/TR/rdf-syntax-grammar#parseTypeLiteralPropertyElt)
- ([`RDFSyntax.parseTypeLiteralPropertyElt`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#parseTypeLiteralPropertyElt))
+ ([`RDFSyntax.parseTypeLiteralPropertyElt`](/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#parseTypeLiteralPropertyElt))
- [parseTypeResourcePropertyElt](http://www.w3.org/TR/rdf-syntax-grammar#parseTypeResourcePropertyElt)
- ([`RDFSyntax.parseTypeLiteralPropertyElt`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#parseTypeLiteralPropertyElt))
+ ([`RDFSyntax.parseTypeLiteralPropertyElt`](/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#parseTypeLiteralPropertyElt))
- [parseTypeCollectionPropertyElt](http://www.w3.org/TR/rdf-syntax-grammar#parseTypeCollectionPropertyElt)
- ([`RDFSyntax.parseTypeCollectionPropertyElt`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#parseTypeCollectionPropertyElt))
+ ([`RDFSyntax.parseTypeCollectionPropertyElt`](/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#parseTypeCollectionPropertyElt))
- [idAttr](http://www.w3.org/TR/rdf-syntax-grammar#idAttr)
- ([`RDFSyntax.idAttr`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#idAttr))
+ ([`RDFSyntax.idAttr`](/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#idAttr))
- [propertyAttr](http://www.w3.org/TR/rdf-syntax-grammar#propertyAttr)
- ([`RDFSyntax.propertyAttr`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#propertyAttr))
+ ([`RDFSyntax.propertyAttr`](/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDFSyntax.html#propertyAttr))
In addition `"daml:collection"`
-([`DAML_OIL.collection`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/DAML_OIL.html#collection))
+([`DAML_OIL.collection`](/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/DAML_OIL.html#collection))
can be blocked. Blocking
[idAttr](http://www.w3.org/TR/rdf-syntax-grammar#idAttr) also
blocks
Modified: jena/site/trunk/content/documentation/io/sax.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/io/sax.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/io/sax.mdtext (original)
+++ jena/site/trunk/content/documentation/io/sax.mdtext Sun May 13 18:52:44 2012
@@ -22,23 +22,23 @@ Jena Model.
To read an arbitrary SAX source as triples to be added into a Jena
model, it is not possible to use a
-`Model.`[`read`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.io.InputStream,%20java.lang.String))()
+`Model.`[`read`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#read(java.io.InputStream,%20java.lang.String))()
operation. Instead, you construct a SAX event handler of class
-[`SAX2Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html),
+[`SAX2Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html),
using the
-[`create`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html#create(java.lang.String,%20com.hp.hpl.jena.rdf.model.Model))
+[`create`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html#create(java.lang.String,%20com.hp.hpl.jena.rdf.model.Model))
method, install these as the handler on your SAX event source, and
then stream the SAX events. It is possible to have fine-grained
control over the SAX events, for instance, by inserting or deleting
events, before passing them to the
-[`SAX2Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html)
+[`SAX2Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html)
handler.
## Sample Code
This code uses the Xerces parser as a SAX event stream, and adds
the triple to a
-[`Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) using
+[`Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html) using
default options.
// Use your own SAX source.
@@ -73,10 +73,10 @@ default options.
## Initializing SAX event source
If your SAX event source is a subclass of `XMLReader`, then the
-[installHandlers](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#installHandlers(org.xml.sax.XMLReader,%20com.hp.hpl.jena.rdf.arp.XMLHandler))
+[installHandlers](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#installHandlers(org.xml.sax.XMLReader,%20com.hp.hpl.jena.rdf.arp.XMLHandler))
static method can be used as shown in the sample. Otherwise, you
have to do it yourself. The
-[`installHandlers`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#installHandlers(org.xml.sax.XMLReader,%20com.hp.hpl.jena.rdf.arp.XMLHandler))
+[`installHandlers`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#installHandlers(org.xml.sax.XMLReader,%20com.hp.hpl.jena.rdf.arp.XMLHandler))
code is like this:
static public void installHandlers(XMLReader rdr, XMLHandler sax2rdf)
@@ -100,11 +100,11 @@ required operations are as above.
## Error Handler
-The [SAX2Model](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html)
+The [SAX2Model](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html)
handler supports the
-[setErrorHandler](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html#setErrorHandler(com.hp.hpl.jena.rdf.model.RDFErrorHandler))
+[setErrorHandler](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html#setErrorHandler(com.hp.hpl.jena.rdf.model.RDFErrorHandler))
method, from the Jena
-[RDFReader](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
+[RDFReader](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
interface. This is used in the same way as that method to control
error reporting.
@@ -114,11 +114,11 @@ allows long jobs to be aborted on user r
## Options
-The [`SAX2Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html)
+The [`SAX2Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html)
handler supports the
-[`setProperty`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html#setProperty(java.lang.String,%20java.lang.Object))
+[`setProperty`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html#setProperty(java.lang.String,%20java.lang.Object))
method, from the Jena
-[`RDFReader`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
+[`RDFReader`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/RDFReader.html)
interface. This is used in nearly the same way to have fine grain
control over ARPs behaviour, particularly over error reporting, see
the [I/O howto](iohowto.html#arp_properties). Setting SAX or
@@ -132,13 +132,13 @@ and desirable that it knows the correct
prefixes.
There is a second version of the
-[`create`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html#create(java.lang.String,%20com.hp.hpl.jena.rdf.model.Model,%20java.lang.String))
+[`create`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2Model.html#create(java.lang.String,%20com.hp.hpl.jena.rdf.model.Model,%20java.lang.String))
method, which allows specification of the `xml:lang` value from the
outer context. If this is inappropriate it is possible, but hard
work, to synthesis an appropriate SAX event.
For the namespaces prefixes, it is possible to call the
-[`startPrefixMapping`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#startPrefixMapping(java.lang.String,%20java.lang.String))
+[`startPrefixMapping`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#startPrefixMapping(java.lang.String,%20java.lang.String))
SAX event, before passing the other SAX events, to declare each
namespace, one by one. Failure to do this is permitted, but, for
instance, a Jena Model will then not know the (advisory) namespace
@@ -150,11 +150,11 @@ events, but nothing untoward is likely i
As with ARP, it is possible to use this functionality, without
using other Jena features, in particular, without using a Jena
Model. Instead of using the class SAX2Model, you use its superclass
-[SAX2RDF](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html). The
-[create](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#create(java.lang.String))
+[SAX2RDF](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html). The
+[create](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#create(java.lang.String))
method on this class does not provide any means of specifying what
to do with the triples. Instead, the class implements the
-[ARPConfig](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html)
+[ARPConfig](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html)
interface, which permits the setting of handlers and parser
options, as described in the documentation for using
[ARP without Jena](standalone.html).
@@ -162,7 +162,7 @@ options, as described in the documentati
Thus you need to:
1. Create a SAX2RDF using
- [SAX2RDF.create()](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#create(java.lang.String))
+ [SAX2RDF.create()](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#create(java.lang.String))
2. Attach your StatementHandler and SAXErrorHandler and optionally
your NamespaceHandler and ExtendedHandler to the SAX2RDF instance.
3. Install the SAX2RDF instance as the SAX handler on your SAX
@@ -177,19 +177,19 @@ This issue has no impact on any other Je
### Using a DOM as Input to Jena
-The [`DOM2Model`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/DOM2Model.html)
+The [`DOM2Model`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/DOM2Model.html)
subclass of SAX2Model, allows the parsing of a DOM using ARP. The
procedure to follow is:
- Construct a `DOM2Model`, using a factory method such as
- [`createD2M`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/DOM2Model.html#createD2M(java.lang.String,%20com.hp.hpl.jena.rdf.model.Model)),
+ [`createD2M`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/DOM2Model.html#createD2M(java.lang.String,%20com.hp.hpl.jena.rdf.model.Model)),
specifying the xml:base of the document to be loaded, the Model to
load into, optionally the xml:lang value (particularly useful if
using a DOM Node from within a Document).
- Set any properties, error handlers etc. on the `DOM2Model`
object.
- The DOM is parsed simply by calling the
- [`load(Node)`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/DOM2Model.html#load(org.w3c.dom.Node))
+ [`load(Node)`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/DOM2Model.html#load(org.w3c.dom.Node))
method.
### Using a DOM as Input to ARP
Modified: jena/site/trunk/content/documentation/io/standalone.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/io/standalone.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/io/standalone.mdtext (original)
+++ jena/site/trunk/content/documentation/io/standalone.mdtext Sun May 13 18:52:44 2012
@@ -19,21 +19,21 @@ standalone.
To load an RDF file:
1. Create an
- [ARP](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARP.html#ARP()) instance.
+ [ARP](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARP.html#ARP()) instance.
2. Set parse options, particularly error detection control, using
- [getOptions](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#getOptions())
+ [getOptions](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#getOptions())
or
- [setOptionsWith](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#setOptionsWith(com.hp.hpl.jena.rdf.arp.ARPOptions)).
+ [setOptionsWith](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#setOptionsWith(com.hp.hpl.jena.rdf.arp.ARPOptions)).
3. Set its handlers, by calling the
- [getHandlers](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#getHandlers())
+ [getHandlers](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#getHandlers())
or
- [setHandlersWith](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#setHandlersWith(com.hp.hpl.jena.rdf.arp.ARPHandlers))
+ [setHandlersWith](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#setHandlersWith(com.hp.hpl.jena.rdf.arp.ARPHandlers))
methods, and then.
- Setting the
- [statement handler](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPHandlers.html#setStatementHandler(com.hp.hpl.jena.rdf.arp.StatementHandler)).
+ [statement handler](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPHandlers.html#setStatementHandler(com.hp.hpl.jena.rdf.arp.StatementHandler)).
- Optionally setting the other handlers.
4. Call a
- [load](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARP.html#load(java.io.InputStream,%20java.lang.String))
+ [load](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARP.html#load(java.io.InputStream,%20java.lang.String))
method
Xerces is used for parsing the XML. The SAXEvents generated by
@@ -102,22 +102,22 @@ ARP reports events concerning:
User code is needed to respond to any of these events of interest.
This is written by implementing any of the relevant interfaces:
-[StatementHandler](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/StatementHandler.html),
+[StatementHandler](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/StatementHandler.html),
org.xml.sax.ErrorHandler,
-[NamespaceHandler](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/NamespaceHandler.html),
+[NamespaceHandler](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/NamespaceHandler.html),
and
-[ExtendedHandler](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ExtendedHandler.html).
+[ExtendedHandler](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ExtendedHandler.html).
An individual handler is set by calling the
-[getHandlers](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#getHandlers())
+[getHandlers](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#getHandlers())
method on the ARP instance. This returns an encapsulation of all
the handlers being used. A specific handler is set by calling the
appropriate set...Handler method on that object, e.g.
-[setStatementHandler](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPHandlers.html#setStatementHandler(com.hp.hpl.jena.rdf.arp.StatementHandler)).
+[setStatementHandler](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPHandlers.html#setStatementHandler(com.hp.hpl.jena.rdf.arp.StatementHandler)).
All the handlers can be copied from one ARP instance to another by
using the
-[setHandlersWith](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#setHandlersWith(com.hp.hpl.jena.rdf.arp.ARPHandlers))
+[setHandlersWith](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#setHandlersWith(com.hp.hpl.jena.rdf.arp.ARPHandlers))
method:
ARP from, to;
@@ -128,7 +128,7 @@ method:
The error handler reports both XML and RDF errors, the former
detected by Xerces. See
-[ARPHandlers.setErrorHandler](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPHandlers.html#setErrorHandler(org.xml.sax.ErrorHandler))
+[ARPHandlers.setErrorHandler](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPHandlers.html#setErrorHandler(org.xml.sax.ErrorHandler))
for details of how to distinguish between them.
## Configuring ARP
@@ -144,9 +144,9 @@ whole file as RDF anyway, or to scan the
As with the handlers, there is an options object that encapsulates
these settings. It can be accessed using
-[`getOptions`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#getOptions()),
+[`getOptions`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPConfig.html#getOptions()),
and then individual settings can be made using the methods in
-[`ARPOptions`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html).
+[`ARPOptions`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ARPOptions.html).
It is also possible to copy all the option settings from one ARP
instance to another:
@@ -172,8 +172,8 @@ non-Xerces parser, or from an in-memory
tree.
Instead of an ARP instance, you create an instance of
-[SAX2RDF](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html) using
-the [newInstance](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#newInstance(java.lang.String))
+[SAX2RDF](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html) using
+the [newInstance](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/SAX2RDF.html#newInstance(java.lang.String))
method. This can be configured just like an ARP instance, following
the initialization section of the [sample code](#sample).
@@ -184,8 +184,8 @@ This is used like a SAX2Model instance a
For very large files, ARP does not use any additional memory except
when either the
-[ExtendedHandler.discardNodesWithNodeID](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ExtendedHandler.html#discardNodesWithNodeID())
+[ExtendedHandler.discardNodesWithNodeID](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/ExtendedHandler.html#discardNodesWithNodeID())
returns false or when the
-[AResource.setUserData](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/AResource.html#setUserData(java.lang.Object))
+[AResource.setUserData](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/arp/AResource.html#setUserData(java.lang.Object))
method has been used. In these cases ARP needs to remember the
`rdf:nodeID` usage through the file life time.
Modified: jena/site/trunk/content/documentation/notes/concurrency-howto.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/notes/concurrency-howto.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/notes/concurrency-howto.mdtext (original)
+++ jena/site/trunk/content/documentation/notes/concurrency-howto.mdtext Sun May 13 18:52:44 2012
@@ -28,8 +28,8 @@ There are two main cases:
(typically, a database).
Transactions are provided by persistent models: see
-the [TDB documentation](/jena/documentation/tdb/tdb_transactions.html)
-and the [SDB documentation](/jena/documenation/sdb/index.html)
+the [TDB documentation](/documentation/tdb/tdb_transactions.html)
+and the [SDB documentation](/documenation/sdb/index.html)
and for details.
This note describes the support for same-JVM, multi-threaded
Modified: jena/site/trunk/content/documentation/notes/file-manager.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/notes/file-manager.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/notes/file-manager.mdtext (original)
+++ jena/site/trunk/content/documentation/notes/file-manager.mdtext Sun May 13 18:52:44 2012
@@ -115,8 +115,8 @@ Using log4j, set the logging level of th
### See also
Javadoc:
-[FileManager](/jena/documentation/javadoc/jena/com/hp/hpl/jena/util/FileManager.html)
-[LocationMapper](/jena/documentation/javadoc/jena/com/hp/hpl/jena/util/LocationMapper.html)
+[FileManager](/documentation/javadoc/jena/com/hp/hpl/jena/util/FileManager.html)
+[LocationMapper](/documentation/javadoc/jena/com/hp/hpl/jena/util/LocationMapper.html)
Modified: jena/site/trunk/content/documentation/notes/model-factory.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/notes/model-factory.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/notes/model-factory.mdtext (original)
+++ jena/site/trunk/content/documentation/notes/model-factory.mdtext Sun May 13 18:52:44 2012
@@ -54,7 +54,7 @@ returns that model.
There are other methods, for removing models, additional control
over create *vs* open, closing the maker, and looking names up; for
those consult the
-[ModelMaker JavaDoc](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/ModelMaker.html).
+[ModelMaker JavaDoc](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/ModelMaker.html).
### File-based models
@@ -169,7 +169,7 @@ allow the reasoner to digest them before
From where do you fetch your reasoners? From the
*reasoner registry*, the class
-[ReasonerRegistry](/jena/documentation/javadoc/jena/com/hp/hpl/jena/reasoner/ReasonerRegistry.html).
+[ReasonerRegistry](/documentation/javadoc/jena/com/hp/hpl/jena/reasoner/ReasonerRegistry.html).
This allows reasoners to be looked up by name, but also provides
some predefined access methods for well-know reasoners:
@@ -194,7 +194,7 @@ in-memory and presents OWL ontologies.
- `createOntologyModel(OntModelSpec spec, Model base)` Creates an
ontology model according the
-[OntModelSpec](/jena/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntModelSpec.html)
+[OntModelSpec](/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntModelSpec.html)
`spec` which presents the ontology of `base`.
- `createOntologyModel(OntModelSpec spec, ModelMaker maker, Model base)`
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=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/notes/typed-literals.mdtext (original)
+++ jena/site/trunk/content/documentation/notes/typed-literals.mdtext Sun May 13 18:52:44 2012
@@ -57,7 +57,7 @@ typed literals whose datatype is the spe
Jena will correctly parse typed literals within RDF/XML, NTriple
and Turtle source files. The same Java object,
-[`Literal`](/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Literal.html)
+[`Literal`](/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Literal.html)
will represent "plain" and "typed" literals. Literal now supports
some new methods:
@@ -128,7 +128,7 @@ made it impossible to cache literals in
Datatypes for typed literals are represented by instances of the
interface
-[`com.hp.hpl.jena.datatypes.RDFDatatype`](/jena/documentation/javadoc/com/hp/hpl/jena/datatypes/RDFDatatype.html).
+[`com.hp.hpl.jena.datatypes.RDFDatatype`](/documentation/javadoc/com/hp/hpl/jena/datatypes/RDFDatatype.html).
Instances of this interface can be used to parse and serialized
typed data, test for equality and test if a typed or lexical value
is a legal value for this datatype.
@@ -187,7 +187,7 @@ Jena includes prebuilt, and pre-register
> gYearMonth gMonthDay
These are all available as static member variables from
-[`com.hp.hpl.jena.datatypes.xsd.XSDDatatype`](/jena/documentation/javadoc/com/hp/hpl/jena/datatypes/xsd/XSDDatatype.html).
+[`com.hp.hpl.jena.datatypes.xsd.XSDDatatype`](/documentation/javadoc/com/hp/hpl/jena/datatypes/xsd/XSDDatatype.html).
Of these types, the following are registered as the default type to
use to represent certain Java classes:
@@ -287,7 +287,7 @@ standard for how to map the datatype URI
Within Jena2 we allow new datatypes to be created and registered by
using the
-[`TypeMapper`](/jena/documentation/javadoc/com/hp/hpl/jena/datatypes/TypeMapper.html)
+[`TypeMapper`](/documentation/javadoc/com/hp/hpl/jena/datatypes/TypeMapper.html)
class.
The easiest way to define a new RDFDatatype is to subclass
Modified: jena/site/trunk/content/documentation/ontology/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/ontology/index.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/ontology/index.mdtext (original)
+++ jena/site/trunk/content/documentation/ontology/index.mdtext Sun May 13 18:52:44 2012
@@ -12,8 +12,8 @@ get full details of the capabilities of
We'll assume that you have a basic familiarity with RDF and with
Jena. If not, there are other
-[Jena help documents](/jena/getting_started) you can read for background
-on these topics, and a [collection of tutorials](/jena/tutorials).
+[Jena help documents](/getting_started) you can read for background
+on these topics, and a [collection of tutorials](/tutorials).
Jena is a programming toolkit, using the Java programming language.
While there are a few command-line tools to help you perform some
@@ -54,8 +54,8 @@ The sections are:
Hopefully, this document will be sufficient to help most readers
to get started using the Jena ontology API. For further support,
-please post questions to the [Jena support list](/jena/help_and_support),
-or [file a bug report](/jena/help_and_support/bugs_and_suggestions.html).
+please post questions to the [Jena support list](/help_and_support),
+or [file a bug report](/help_and_support/bugs_and_suggestions.html).
*Please note that we ask that you use the support list or the bug-tracker
to communicate with the Jena team, rather than send email to the team
@@ -264,10 +264,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`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/Model.html) class.
+[`Model`](/documentation/javadoc/com/hp/hpl/jena/rdf/model/Model.html) class.
The base `Model` allows access to the statements in a collection of
RDF data.
-[`OntModel`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/OntModel.html)
+[`OntModel`](/documentation/javadoc/com/hp/hpl/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.
@@ -275,7 +275,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](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/Statement.html)) stored in the RDF
+[`Statement`s](/documentation/javadoc/com/hp/hpl/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
@@ -432,7 +432,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`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/ModelFactory.html).
+[`ModelFactory`](/documentation/javadoc/com/hp/hpl/jena/rdf/model/ModelFactory.html).
The simplest way to create an ontology model is as follows:
OntModel m = ModelFactory.createOntologyModel();
@@ -474,7 +474,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`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/ProfileRegistry.html).
+[`ProfileRegistry`](/documentation/javadoc/com/hp/hpl/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
@@ -488,7 +488,7 @@ either of:
Beyond these basic choices, the complexities of configuring an
ontology model are wrapped up in a recipe object called
-[`OntModelSpec`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/OntModelSpec.html).
+[`OntModelSpec`](/documentation/javadoc/com/hp/hpl/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
@@ -521,7 +521,7 @@ RDFS\_MEM\_RDFS\_INF | RDFS | in-memory
For details of reasoner capabilities, please see the
[inference documentation](../inference) and the Javadoc
for
-[OntModelSpec](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/OntModelSpec.html).
+[OntModelSpec](/documentation/javadoc/com/hp/hpl/jena/ontology/OntModelSpec.html).
See also further discussion [below](#inference-intro).
**Note:** it is primarily the choice of reasoner, rather than the
@@ -705,7 +705,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`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/ModelFactory.html).
+[`ModelFactory`](/documentation/javadoc/com/hp/hpl/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
@@ -731,7 +731,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`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/ModelMaker.html)
+[`ModelMaker`](/documentation/javadoc/com/hp/hpl/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
@@ -762,7 +762,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`](/jena/documentation/javadoc/com/hp/hpl/jena/util/FileManager.html) to
+[`FileManager`](/documentation/javadoc/com/hp/hpl/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
@@ -799,7 +799,7 @@ with any legal URI (not necessarily reso
`altURL` is itself resolvable.
See the notes on
-[`FileManager`](/jena/tools/filemanager.html) for details of additional options.
+[`FileManager`](/tools/filemanager.html) for details of additional options.
In the following example, we use the `DocumentManager` API to declare that the ESWC
ontology is replicated locally on disk. We then load it using
@@ -848,14 +848,14 @@ by calling `clearCache()`.
All of the classes in the ontology API that represent ontology
values have
-[`OntResource`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/OntResource.html)
+[`OntResource`](/documentation/javadoc/com/hp/hpl/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`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/Resource.html)
+[`Resource`](/documentation/javadoc/com/hp/hpl/jena/rdf/model/Resource.html)
interface, so any general method that accepts a resource or an
-[`RDFNode`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/RDFNode.html)
+[`RDFNode`](/documentation/javadoc/com/hp/hpl/jena/rdf/model/RDFNode.html)
will also accept an `OntResource`, and consequently, any other
ontology value.
@@ -986,7 +986,7 @@ returned.
Classes are the basic building blocks of an ontology. A simple
class is represented in Jena by an
-[OntClass](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/OntClass.html)
+[OntClass](/documentation/javadoc/com/hp/hpl/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
@@ -1078,7 +1078,7 @@ this class among their domain classes. T
`listDeclaredProperties()` attempts to identify the properties that
are intended to apply to instances of this class. Using
`listDeclaredProperties` is explained in detail in the
-[RDF frames how-to](/jena/documentation/notes/rdf-frames.html).
+[RDF frames how-to](/documentation/notes/rdf-frames.html).
## Ontology properties
@@ -1095,11 +1095,11 @@ properties represented in an ontology mo
A property in an ontology model is an extension of the core Jena
API class
-[`Property`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/Property.html)
+[`Property`](/documentation/javadoc/com/hp/hpl/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`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/OntProperty.html).
+[`OntProperty`](/documentation/javadoc/com/hp/hpl/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`:
@@ -1170,10 +1170,10 @@ entailments, and so is useful when annot
for example.
In Jena, the Java interfaces
-[`ObjectProperty`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/ObjectProperty.html),
-[`DatatypeProperty`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/DatatypeProperty.html)
+[`ObjectProperty`](/documentation/javadoc/com/hp/hpl/jena/ontology/ObjectProperty.html),
+[`DatatypeProperty`](/documentation/javadoc/com/hp/hpl/jena/ontology/DatatypeProperty.html)
and
-[`AnnotationProperty`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/AnnotationProperty.html)
+[`AnnotationProperty`](/documentation/javadoc/com/hp/hpl/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
@@ -1194,7 +1194,7 @@ equivalent to stating that the property
of one.
Being a functional property is represented through the
-[`FunctionalProperty`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/FunctionalProperty.html)
+[`FunctionalProperty`](/documentation/javadoc/com/hp/hpl/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
@@ -1207,13 +1207,13 @@ parameter to the `createObjectProperty()
There are several additional sub-types of ObjectProperty that
represent additional capabilities of ontology properties. A
-[`TransitiveProperty`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/TransitiveProperty.html)
+[`TransitiveProperty`](/documentation/javadoc/com/hp/hpl/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`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/SymmetricProperty.html)
+[`SymmetricProperty`](/documentation/javadoc/com/hp/hpl/jena/ontology/SymmetricProperty.html)
means that if p is symmetric, and we know `:a p :b`, we can infer
`:b p :a`. An
-[`InverseFunctionalProperty`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/InverseFunctionalProperty.html)
+[`InverseFunctionalProperty`](/documentation/javadoc/com/hp/hpl/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
@@ -1266,7 +1266,7 @@ each in turn.
### Restriction class expressions
A
-[restriction](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/Restriction.html)
+[restriction](/documentation/javadoc/com/hp/hpl/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
@@ -1466,10 +1466,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`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/RDFList.html).
+[`RDFList javadoc`](/documentation/javadoc/com/hp/hpl/jena/rdf/model/RDFList.html).
Various means of constructing lists are defined in
-[`Model`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/Model.html), as
+[`Model`](/documentation/javadoc/com/hp/hpl/jena/rdf/model/Model.html), as
variants on `createList`. For example, we can construct a list of
three classes as follows:
@@ -1498,7 +1498,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`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/RDFList.html)
+[`RDFList`](/documentation/javadoc/com/hp/hpl/jena/rdf/model/RDFList.html)
methods may be used to access members of the list, iterate over the
list, and so forth. For example:
@@ -1572,7 +1572,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`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/BooleanClassDescription.html).
+[`BooleanClassDescription`](/documentation/javadoc/com/hp/hpl/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
@@ -1590,7 +1590,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](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/EnumeratedClass.html)
+[enumerated class](/documentation/javadoc/com/hp/hpl/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.
@@ -1628,7 +1628,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](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/DataRange.html)
+[`DataRange` javadoc](/documentation/javadoc/com/hp/hpl/jena/ontology/DataRange.html)
for more details.
### Listing classes
@@ -1660,7 +1660,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](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/OntTools.html)
+[OntTools](/documentation/javadoc/com/hp/hpl/jena/ontology/OntTools.html)
method `namedHierarchyRoots()`.
You should also note that it is important to close the iterators
@@ -1689,7 +1689,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`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/Individual.html),
+[`Individual`](/documentation/javadoc/com/hp/hpl/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
@@ -1741,7 +1741,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`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/OntModel.html)
+on [`OntModel`](/documentation/javadoc/com/hp/hpl/jena/ontology/OntModel.html)
for reference).
We can attach various meta-data statements to this object to
@@ -1763,7 +1763,7 @@ version information.
In the Jena API, the ontology's metadata properties can be accessed
through the
-[`Ontology`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/Ontology.html)
+[`Ontology`](/documentation/javadoc/com/hp/hpl/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:
@@ -1849,7 +1849,7 @@ and used.
For a complete and thorough description of Jena's inference
capabilities, please see the
-[reasoner documentation](/jena/documentation/inference/). This section of
+[reasoner documentation](/documentation/inference/). This section of
of the ontology API documentation is intended to serve as only a
brief guide and overview.
@@ -1866,7 +1866,7 @@ performance are.
The reasoner attached to an ontology model, if any, is specified
through the
-[`OntModelSpec`](/jena/documentation/javadoc/com/hp/hpl/jena/ontology/OntModelSpec.html).
+[`OntModelSpec`](/documentation/javadoc/com/hp/hpl/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
@@ -1895,7 +1895,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`](/jena/documentation/javadoc/com/hp/hpl/jena/rdf/model/InfModel.html)
+[`InfModel`](/documentation/javadoc/com/hp/hpl/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/download.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/download.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/download.mdtext (original)
+++ jena/site/trunk/content/documentation/query/download.mdtext Sun May 13 18:52:44 2012
@@ -1,6 +1,6 @@
Title: ARQ Downloads
-For details on downloading ARQ, please see the Jena [downloads page](/jena/download/).
+For details on downloading ARQ, please see the Jena [downloads page](/download/).
## Subversion
Modified: jena/site/trunk/content/documentation/query/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/index.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/index.mdtext (original)
+++ jena/site/trunk/content/documentation/query/index.mdtext Sun May 13 18:52:44 2012
@@ -22,12 +22,12 @@ SPARQL is the query language developed b
## Introduction
-- [A Brief Tutorial on SPARQL](/jena/tutorials/sparql.html)
+- [A Brief Tutorial on SPARQL](/tutorials/sparql.html)
- [Application API](app_api.html) - covers the majority of
application usages
- [Frequently Asked Questions](faq.html)
- [ARQ Support](support.html)
-- Application [javadoc](/jena/documentation/javadoc/arq/index.html)
+- Application [javadoc](/documentation/javadoc/arq/index.html)
- [Command line utilities](cmds.html)
- [Logging](logging.html)
- [Explaining queries](explain.html)
Modified: jena/site/trunk/content/documentation/rdf/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/rdf/index.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/rdf/index.mdtext (original)
+++ jena/site/trunk/content/documentation/rdf/index.mdtext Sun May 13 18:52:44 2012
@@ -1,7 +1,7 @@
Title: The core RDF API
This section provides some basic reference notes on the core Jena RDF API.
-For a more tutorial introduction, please see [the tutorials](/jena/tutorials).
+For a more tutorial introduction, please see [the tutorials](/tutorials).
## Core concepts
Modified: jena/site/trunk/content/documentation/sdb/commands.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/sdb/commands.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/sdb/commands.mdtext (original)
+++ jena/site/trunk/content/documentation/sdb/commands.mdtext Sun May 13 18:52:44 2012
@@ -84,7 +84,7 @@ sdb.ttl from the current directory.
--sdb=<sdb.ttl>
This store description is a
-[Jena assembler](/jena/documentation/assembler/)
+[Jena assembler](/documentation/assembler/)
file. The description consists of two parts; a store description
and a connection description.
Modified: jena/site/trunk/content/documentation/sdb/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/sdb/index.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/sdb/index.mdtext (original)
+++ jena/site/trunk/content/documentation/sdb/index.mdtext Sun May 13 18:52:44 2012
@@ -27,7 +27,7 @@ line scripts and via the Jena API.
## Downloads
SDB is distributed from the Apache Jena project. See the
-[downloads page](/jena/download/) for details.
+[downloads page](/download/) for details.
## Subversion
@@ -36,7 +36,7 @@ at Apache.
## Support
-[Support and questions](/jena/help_and_support)
+[Support and questions](/help_and_support)
## Details
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=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/serving_data/index.mdtext (original)
+++ jena/site/trunk/content/documentation/serving_data/index.mdtext Sun May 13 18:52:44 2012
@@ -34,7 +34,7 @@ See also:
## Download Fuseki
Jena builds are in the process of migrating to Apache.
-See the [downloads page](/jena/download/) for details.
+See the [downloads page](/download/) for details.
Fuseki builds will be migrating to the Apache infrastructure very soon.
Snapshot builds are
available via Apache Maven or can be [downloaded from here](https://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-fuseki/).
@@ -298,7 +298,7 @@ A general dataset is described by:
.
The models can be
-[Jena inference models](/jena/documentation/inference/).
+[Jena inference models](/documentation/inference/).
## Fuseki Configuration File
Modified: jena/site/trunk/content/documentation/serving_data/soh.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/serving_data/soh.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/serving_data/soh.mdtext (original)
+++ jena/site/trunk/content/documentation/serving_data/soh.mdtext Sun May 13 18:52:44 2012
@@ -70,7 +70,7 @@ for HTTP REST, query and update. This se
information about using SOH with some servers. See the
documentation for each server for authoritative information.
-If you have details for other servers, [get involved](/jena/getting_involved/index.html)
+If you have details for other servers, [get involved](/getting_involved/index.html)
### Fuseki
Modified: jena/site/trunk/content/documentation/tdb/assembler.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/assembler.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/assembler.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/assembler.mdtext Sun May 13 18:52:44 2012
@@ -1,6 +1,6 @@
Title: TDB Assembler
-[Assemblers](/jena/documentation/assembler/)
+[Assemblers](/documentation/assembler/)
are a general mechanism in Jena to describe objects to be built,
often these objects are models and datasets. Assemblers are used
heavily in [Fuseki](../serving_data/) for
Modified: jena/site/trunk/content/documentation/tdb/tdb_download.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/tdb_download.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/tdb_download.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/tdb_download.mdtext Sun May 13 18:52:44 2012
@@ -5,7 +5,7 @@ Title: TDB Download and Installation
Currently, TDB is a separate download from the main release of Jena.
The TDB download includes a compatible copy of Jena.
-See the [Jena downloads page](/jena/download/) for details of Jena download area.
+See the [Jena downloads page](/download/) for details of Jena download area.
TDB is distributed as a complete download and also via Apache Maven
(groupId `or.apache.jena`, artifact `jena-tdb`).
Modified: jena/site/trunk/content/documentation/tools/eyeball-getting-started.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tools/eyeball-getting-started.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tools/eyeball-getting-started.mdtext (original)
+++ jena/site/trunk/content/documentation/tools/eyeball-getting-started.mdtext Sun May 13 18:52:44 2012
@@ -9,11 +9,11 @@ for common problems. It is user-extensib
- The [brief guide](eyeball-guide.html).
- The [manual](eyeball-manual.html).
- - The [JavaDoc](/jena/documentation/javadoc/eyeball/index.html).
+ - The [JavaDoc](/documentation/javadoc/eyeball/index.html).
## Getting the Eyeball release
-<!--Please see the [downloads page](/jena/download/) for details.-->
+<!--Please see the [downloads page](/download/) for details.-->
<b>Download from SourceForge:
[Eyeball distribution](http://sourceforge.net/projects/jena/files/Eyeball/Eyeball%202.3/)
@@ -22,7 +22,7 @@ This predates the move of Jena to Apache
## Installation
-If you haven't already, download Eyeball <!--[download Eyeball](/jena/download/)-->
+If you haven't already, download Eyeball <!--[download Eyeball](/download/)-->
and unzip it into a directory of your choice. The download includes all
of Jena, so it should not require any additional `.jar` files to run.
@@ -30,7 +30,7 @@ If you have Ant installed, run the Eyeba
ant test
-If it doesn't say that the tests passed, please [file a Jira issue](/jena/help_and_support/bugs_and_suggestions.html)
+If it doesn't say that the tests passed, please [file a Jira issue](/help_and_support/bugs_and_suggestions.html)
Ensure all the jars in the Eyeball `lib` directory are on your
classpath.
Modified: jena/site/trunk/content/documentation/tools/eyeball-manual.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tools/eyeball-manual.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tools/eyeball-manual.mdtext (original)
+++ jena/site/trunk/content/documentation/tools/eyeball-manual.mdtext Sun May 13 18:52:44 2012
@@ -6,9 +6,9 @@ This document describes Eyeball, an
See
the release notes for descriptions of changes
from previous versions. Eyeball is part of the
-[Jena](/jena/) family of
+[Jena](/) family of
RDF/OWL tools. For help and support with Eyeball, please see
-[the Jena support page](/jena/help_and_support/index.html)
+[the Jena support page](/help_and_support/index.html)
Throughout this document, the prefix `eye:` stands for the URL
`http://jena.hpl.hp.com/Eyeball\#`.
Modified: jena/site/trunk/content/getting_started/fuseki.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/getting_started/fuseki.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/getting_started/fuseki.mdtext (original)
+++ jena/site/trunk/content/getting_started/fuseki.mdtext Sun May 13 18:52:44 2012
@@ -5,7 +5,7 @@ This section will shortly contain some e
using Jena for RDF processing. In the meantime, please see the following
resources for help:
- - [Fuseki overview](/jena/documentation/serving_data/index.html)
+ - [Fuseki overview](/documentation/serving_data/index.html)
## Other resources
Modified: jena/site/trunk/content/getting_started/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/getting_started/index.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/getting_started/index.mdtext (original)
+++ jena/site/trunk/content/getting_started/index.mdtext Sun May 13 18:52:44 2012
@@ -5,9 +5,9 @@ This section will shortly contain some e
using Jena for RDF processing. In the meantime, please see the following
resources for help:
- - [Jena RDF API tutorial](/jena/tutorials/rdf_api.html)
- - [SPARQL tutorial](/jena/tutorials/sparql.html)
- - [Ontology API overview](/jena/documentation/ontology)
+ - [Jena RDF API tutorial](/tutorials/rdf_api.html)
+ - [SPARQL tutorial](/tutorials/sparql.html)
+ - [Ontology API overview](/documentation/ontology)
## Other resources
Modified: jena/site/trunk/content/getting_started/rdf_api.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/getting_started/rdf_api.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/getting_started/rdf_api.mdtext (original)
+++ jena/site/trunk/content/getting_started/rdf_api.mdtext Sun May 13 18:52:44 2012
@@ -5,9 +5,9 @@ This section will shortly contain some e
using Jena for RDF processing. In the meantime, please see the following
resources for help:
- - [Jena RDF API tutorial](/jena/tutorials/rdf_api.html)
- - [SPARQL tutorial](/jena/tutorials/sparql.html)
- - [Ontology API overview](/jena/documentation/ontology)
+ - [Jena RDF API tutorial](/tutorials/rdf_api.html)
+ - [SPARQL tutorial](/tutorials/sparql.html)
+ - [Ontology API overview](/documentation/ontology)
## Other resources
Modified: jena/site/trunk/content/getting_started/sparql.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/getting_started/sparql.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/getting_started/sparql.mdtext (original)
+++ jena/site/trunk/content/getting_started/sparql.mdtext Sun May 13 18:52:44 2012
@@ -5,7 +5,7 @@ This section will shortly contain some e
using Jena for RDF processing. In the meantime, please see the following
resources for help:
- - [SPARQL tutorial](/jena/tutorials/sparql.html)
+ - [SPARQL tutorial](/tutorials/sparql.html)
## Other resources
Modified: jena/site/trunk/content/tutorials/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/index.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/index.mdtext (original)
+++ jena/site/trunk/content/tutorials/index.mdtext Sun May 13 18:52:44 2012
@@ -2,7 +2,7 @@ Title: Jena tutorials
The following tutorials take a step-by-step approach to explaining aspects of
RDF and linked-data applications programming in Jena. For a more task-oriented
-description, please see the [getting started](/jena/getting_started/) guide.
+description, please see the [getting started](/getting_started/) guide.
- [RDF core API tutorial](rdf_api.html)
- [SPARQL tutorial](sparql.html)
Modified: jena/site/trunk/content/tutorials/sparql.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/sparql.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/sparql.mdtext (original)
+++ jena/site/trunk/content/tutorials/sparql.mdtext Sun May 13 18:52:44 2012
@@ -44,4 +44,4 @@ information, in the form of a set of bin
- [SPARQL reference card](http://www.ilrt.bris.ac.uk/people/cmdjb/2005/04-sparql/)
(by [Dave Beckett](http://www.ilrt.bristol.ac.uk/people/cmdjb/))
-Detailed [ARQ documentation](/jena/documentation/query/)
+Detailed [ARQ documentation](/documentation/query/)
Modified: jena/site/trunk/content/tutorials/sparql_data.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/sparql_data.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/sparql_data.mdtext (original)
+++ jena/site/trunk/content/tutorials/sparql_data.mdtext Sun May 13 18:52:44 2012
@@ -25,7 +25,7 @@ Our example database just contains some
Graphically, the data looks like:
-
+
In triples, this might look like:
Modified: jena/site/trunk/content/tutorials/sparql_query1.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/sparql_query1.mdtext?rev=1337964&r1=1337963&r2=1337964&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/sparql_query1.mdtext (original)
+++ jena/site/trunk/content/tutorials/sparql_query1.mdtext Sun May 13 18:52:44 2012
@@ -40,7 +40,7 @@ command line applications.
## Executing the query
-There are [helper scripts](/jena/documentation/query/cmds.html) in the ARQ `bat/` and
+There are [helper scripts](/documentation/query/cmds.html) in the ARQ `bat/` and
`bin/` directories of the ARQ distribution. They may not be in a
Jena distribution. You should check these scripts before use.