All Classes and Interfaces
Class
Description
Interface for accumulating a JSON object from a stream of triples (edges in a graph).
This class implements the driver for accumulating (json) objects from a sequence of edges (triples/quads).
An accumulator for a set of fields.
An accumulator for a conditional transition to the fragment body.
Base interface for objects and fragment bodies, i.e. accumulators for a fixed set of fields.
Common base class for accumulators of Objects and Fragments.
Accumulator for the values of an (objectId, propertyId) pair.
A data model for RDF tree structures akin to gson's JsonElement.
A literal simply wraps a node.
An RDF counterpart to a JSON object.
A restricted graph implementation for traversal over object structures.
Interface for mapping RDF graphs to tree structures.
A mutable sub view of all JSON compatible values of an RdfObject
Abstraction akin to JSONPath's JsonProvidere.
The motivation for this abstraction was to have a JsonWriter which can assemble JsonObjects.
Object notation writers support objects (aka "associative arrays", "dictionaries", "maps")
and arrays.
Deprecated.
Writer with an in-memory destination.
A data model for RDF tree structures akin to gson's JsonElement.
Idea: Instead of accessing fields directly - which may be null - return an API that can create those if desired.
Base class for RDF elements which correspond to resources in an RDF graph -
namely objects and arrays.
If rdfTermMode is true, then all json literals will be strings that
contain RDF terms in n-triples syntax.
Json-NT is simply json where keys and literals are all strings that contain
RDF terms in n-triples serialization.
Visitor the writes out a RON structure in JSON
A literal simply wraps a node.
An RDF counterpart to a JSON object.
Abstraction akin to JSONPath's JsonProvidere.