Uses of Package
org.apache.jena.graph

Packages that use org.apache.jena.graph
Package
Description
This package defines the enhanced node and graph classes; an enhanced node is one embedded in a particular enhanced graph.
This package defines the Graph and Node family of classes, which form the underlying datatypes of the Jena system.
This package defines simple composite graphs - union, intersection, difference, and update-tracking.
This package provides basic implementations of Graph interfaces such as EventManager and Capabilities.
Various memory-based implementations of interfaces, specifically GraphMem for memory-based Graphs.
Provides a set of abstractions and convenience classes for accessing and manipluating ontologies represented in RDF.
Provides default implementations for the abstractions defined in the org.apache.jena.ontology package.
A package for creating and manipulating RDF graphs.
This package contains implementations of the interfaces defined in the .model package, eg ModelCom for Model, ResourceImpl for Resource, and so on.
A parser for RDF/XML.
The Jena2 reasoner subsystem is designed to allow a range of inference engines to be plugged into Jena.
Provides a selection of simple rule engines for Jena inference models.
Implementations of the Builtin class which provides primitive operations to the rule engines.
Internal implementation objects used by the rule system interpreters and compilers.
This package contains a reasoner which supports transitive-reflexive closure of subPropertyOf and subClassOf relations.
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.
 
 
 
Miscellaneous collection of utility classes.
A package containing constant classes with predefined constant objects for classes and properties defined in well known vocabularies.
  • Class
    Description
    HasNode - interface for objects that front a Node in some context.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
  • Class
    Description
    System identifier for a blank node.
    Interface for expressing capabilities.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    The component of a graph responsible for managing events and listeners.
    GraphEvents is the base class for Jena general graph events.
    Interface for listening to graph-level update events.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and 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.
    RDF blank nodes, ie nodes with identity but without URIs.
    This is the class of "concrete" nodes, ie those which correspond to actual RDF data - URIs, blank nodes, and literals.
    Extension to the RDF Data model.
    This is the subclass of "fluid" nodes, ie nodes that are "holes" in pattern matching.
    RDF Graphs as RDF terms.
    An RDF node holding a literal value.
    RDF triples as RDF terms for RDF-star embedded triples.
    RDF nodes with a global identity given by a URI.
    "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.
    The NodeVisitor interface is used by Node::visitWith so that an application can have type-dispatch on the class of a Node.
    Preliminary interface for graphs supporting transactions.
    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.
    A Field is a selector from Triples; it allows selectors to be passed around as if they were functions, hooray.
    An interface for expressing a stopping condition on triples, such as in sub-graph extraction.
  • Class
    Description
    Interface for expressing capabilities.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    Preliminary interface for graphs supporting transactions.
    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
    Description
    Interface for expressing capabilities.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    The component of a graph responsible for managing events and listeners.
    Interface for listening to graph-level update events.
    A factory for providing instances of named graphs with appropriate storage models.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    Preliminary interface for graphs supporting transactions.
    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
    Description
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    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.
    A Field is a selector from Triples; it allows selectors to be passed around as if they were functions, hooray.
  • Class
    Description
    HasNode - interface for objects that front a Node in some context.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
  • Class
    Description
    HasNode - interface for objects that front a Node in some context.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
  • Class
    Description
    System identifier for a blank node.
    HasNode - interface for objects that front a Node in some context.
    FrontsTriple (see also FrontsNode) is an interface for things that can be seen as wrappers round triples.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A factory for providing instances of named graphs with appropriate storage models.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    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.
    An interface for expressing a stopping condition on triples, such as in sub-graph extraction.
  • Class
    Description
    HasNode - interface for objects that front a Node in some context.
    FrontsTriple (see also FrontsNode) is an interface for things that can be seen as wrappers round triples.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    Interface for listening to graph-level update events.
    A factory for providing instances of named graphs with appropriate storage models.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    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
    Description
    The interface to be satisfied by implementations maintaining collections of RDF triples.
  • Class
    Description
    Interface for expressing capabilities.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    Preliminary interface for graphs supporting transactions.
    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
    Description
    Interface for expressing capabilities.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    This is the subclass of "fluid" nodes, ie nodes that are "holes" in pattern matching.
    "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.
    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
    Description
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
  • Class
    Description
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    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
    Description
    Interface for expressing capabilities.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    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
    Description
    Interface for expressing capabilities.
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    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
    Description
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    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
    Description
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    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
    Description
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
  • Class
    Description
    The interface to be satisfied by implementations maintaining collections of RDF triples.
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.
    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
    Description
    A Node has five subtypes: Node_Blank, Node_Anon, Node_URI, Node_Variable, and Node_ANY.