How should you use Thing? How does this compare with using a bean and Bean Session? This small tutorial gives a basic comparison. It is intended both as a small first tutorial and as a way to evaluate which approach might better serve your needs.
The Tupelo Server Webapp is a web application that allows remote access to a Tupelo Context. This document describes how to acquire it and configure it.
Unifier is an Operator that makes it possible to execute complex, declarative, conjunctive queries against any Context implementation that supports TripleMatcher.
In some situations you may want to make sure write operations aren't performed against a Context. For instance, you may be using a UnionContext to combine metadata from a Tupelo Server with local annotations, and ensure that new annotations are stored locally instead of on the server.
To make a Context read-only, you can "wrap" it in a ReadOnlyContextFacade. Operations against the facade are performed against the wrapped Context, except for write operations, which throw OperatorUnavailableException.
Tupelo provides an implementation of the Open Provenance Model (OPM). The OPM is a way of recording information about processes as they occur which includes constructs for representing causal and dependency relationships between sub-processes and the data items or other artifacts that they use or produce. Tupelo provides a way of reading and writing OPM information to a Context as RDF metadata, as well as a high-level representation of the OPM that can be extended to support other serializations of the OPM as they become available.
For details about the OPM, please familiarize yourself with the document describing it.
OPM models causality relationships as a graph where the nodes are of several different kinds including Processes, Artifacts, and Agents. It also includes the concepts of Accounts and Roles. Tupelo's API provides representations of these OPM concepts along with representations of the arcs that connect them in OPM graphs.