| Package | Description |
|---|---|
| org.apache.jena.enhanced |
This package defines the enhanced node and graph classes; an enhanced
node is one embedded in a particular enhanced graph.
|
| org.apache.jena.graph |
This package defines the Graph and Node family of classes, which
form the underlying datatypes of the Jena system.
|
| org.apache.jena.graph.compose |
This package defines simple composite graphs - union, intersection,
difference, and update-tracking.
|
| org.apache.jena.graph.impl |
This package provides basic implementations of Graph interfaces
such as EventManager and Capabilities.
|
| org.apache.jena.mem |
Various memory-based implementations of interfaces,
specifically GraphMem for memory-based Graphs.
|
| org.apache.jena.ontology |
Provides a set of abstractions and convenience classes for accessing and manipluating ontologies
represented in RDF.
|
| org.apache.jena.ontology.impl |
Provides default implementations for the abstractions defined in the
org.apache.jena.ontology package. |
| org.apache.jena.rdf.model |
A package for creating and manipulating RDF graphs.
|
| org.apache.jena.rdf.model.impl |
This package contains implementations of the interfaces defined
in the .model package, eg ModelCom for Model, ResourceImpl
for Resource, and so on.
|
| org.apache.jena.rdfxml.xmlinput |
A parser for RDF/XML.
|
| org.apache.jena.reasoner |
The Jena2 reasoner subsystem is designed to allow a range of inference
engines to be plugged into Jena.
|
| org.apache.jena.reasoner.rulesys |
Provides a selection of simple rule engines for Jena inference models.
|
| org.apache.jena.reasoner.rulesys.builtins |
Implementations of the Builtin class which provides primitive operations to the rule
engines.
|
| org.apache.jena.reasoner.rulesys.impl |
Internal implementation objects used by the rule system interpreters
and compilers.
|
| org.apache.jena.reasoner.transitiveReasoner |
This package contains a reasoner which supports transitive-reflexive closure
of subPropertyOf and subClassOf relations.
|
| org.apache.jena.shared |
This package defines some classes common to the Jena API
and SPI levels, in particular the JenaException class from which
all Jena-specific exceptions hang, and the interface PrefixMapping
for translation to and from QNames.
|
| org.apache.jena.sys | |
| org.apache.jena.util |
Miscellaneous collection of utility classes.
|
| org.apache.jena.vocabulary |
A package containing constant classes with predefined constant objects
for classes and properties defined in well known vocabularies.
|
| Class and Description |
|---|
| FrontsNode
HasNode - interface for objects that front a Node in some context.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Class and Description |
|---|
| BlankNodeId
System identifier for a blank node.
|
| Capabilities
Interface for expressing capabilities.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| GraphEventManager
The component of a graph responsible for managing events and listeners.
|
| GraphEvents
GraphEvents is the base class for Jena general graph events.
|
| GraphListener
Interface for listening to graph-level update events.
|
| GraphStatisticsHandler
A graph's StatisticsHandler offers access to some statistics about that
graph's contents that might be useful for optimisation.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Node_ANY
A Node_ANY (there should be only one) is a meta-node that is used to stand
for any other node in a query.
|
| Node_Blank
RDF blank nodes, ie nodes with identity but without URIs.
|
| Node_Concrete
This is the class of "concrete" nodes, ie those which correspond
to actual RDF data - URIs, blank nodes, and literals.
|
| Node_Ext
Extension to the RDF Data model.
|
| Node_Fluid
This is the subclass of "fluid" nodes, ie nodes that are "holes" in pattern
matching.
|
| Node_Literal
An RDF node holding a literal value.
|
| Node_URI
RDF nodes with a global identity given by a URI.
|
| Node_Variable
"variable" nodes; these are outside the RDF2003 specification, but are
used internally for "placeholder" nodes where blank nodes would be
wrong, most specifically in Query.
|
| NodeVisitor
The NodeVisitor interface is used by Node::visitWith so that an application
can have type-dispatch on the class of a Node.
|
| TransactionHandler
Preliminary interface for graphs supporting transactions.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Triple.Field
A Field is a selector from Triples; it allows selectors to be passed
around as if they were functions, hooray.
|
| TripleBoundary
An interface for expressing a stopping condition on triples, such as in
sub-graph extraction.
|
| Class and Description |
|---|
| Capabilities
Interface for expressing capabilities.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| GraphStatisticsHandler
A graph's StatisticsHandler offers access to some statistics about that
graph's contents that might be useful for optimisation.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| TransactionHandler
Preliminary interface for graphs supporting transactions.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Class and Description |
|---|
| Capabilities
Interface for expressing capabilities.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| GraphEventManager
The component of a graph responsible for managing events and listeners.
|
| GraphListener
Interface for listening to graph-level update events.
|
| GraphMaker
A factory for providing instances of named graphs with appropriate storage models.
|
| GraphStatisticsHandler
A graph's StatisticsHandler offers access to some statistics about that
graph's contents that might be useful for optimisation.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| TransactionHandler
Preliminary interface for graphs supporting transactions.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Class and Description |
|---|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Triple.Field
A Field is a selector from Triples; it allows selectors to be passed
around as if they were functions, hooray.
|
| Class and Description |
|---|
| FrontsNode
HasNode - interface for objects that front a Node in some context.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Class and Description |
|---|
| FrontsNode
HasNode - interface for objects that front a Node in some context.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Class and Description |
|---|
| BlankNodeId
System identifier for a blank node.
|
| FrontsNode
HasNode - interface for objects that front a Node in some context.
|
| FrontsTriple
FrontsTriple (see also FrontsNode) is an interface for things that can
be seen as wrappers round triples.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| GraphMaker
A factory for providing instances of named graphs with appropriate storage models.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| TripleBoundary
An interface for expressing a stopping condition on triples, such as in
sub-graph extraction.
|
| Class and Description |
|---|
| FrontsNode
HasNode - interface for objects that front a Node in some context.
|
| FrontsTriple
FrontsTriple (see also FrontsNode) is an interface for things that can
be seen as wrappers round triples.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| GraphListener
Interface for listening to graph-level update events.
|
| GraphMaker
A factory for providing instances of named graphs with appropriate storage models.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Class and Description |
|---|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Class and Description |
|---|
| Capabilities
Interface for expressing capabilities.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| TransactionHandler
Preliminary interface for graphs supporting transactions.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Class and Description |
|---|
| Capabilities
Interface for expressing capabilities.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Node_Fluid
This is the subclass of "fluid" nodes, ie nodes that are "holes" in pattern
matching.
|
| Node_Variable
"variable" nodes; these are outside the RDF2003 specification, but are
used internally for "placeholder" nodes where blank nodes would be
wrong, most specifically in Query.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Class and Description |
|---|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Class and Description |
|---|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Class and Description |
|---|
| Capabilities
Interface for expressing capabilities.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Class and Description |
|---|
| Capabilities
Interface for expressing capabilities.
|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Class and Description |
|---|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Class and Description |
|---|
| Graph
The interface to be satisfied by implementations maintaining collections
of RDF triples.
|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
| Triple
Triples are the basis for RDF statements; they have a subject, predicate, and
object field (all nodes) and express the notion that the relationship named
by the predicate holds between the subject and the object.
|
| Class and Description |
|---|
| Node
A Node has five subtypes: Node_Blank, Node_Anon, Node_URI,
Node_Variable, and Node_ANY.
|
Licenced under the Apache License, Version 2.0