All Classes and Interfaces

Class
Description
 
 
 
 
 
 
 
 
 
A concept combines a SPARQL graph pattern (element) with a variable.
 
 
 
 
 
 
 
 
 
 
 
 
Expression visitor that generates a SPARQL concept from a concept expression
 
 
A fragment together with a distinguished list of variables which can be used to "connect" fragments.
 
Expression that can be used to refer to the set of values appearing as the filler of a certain property restriction
Combines a fragment (graph pattern plus exposed variables) with additional information about which of the underlying graph pattern's visible variables form a composite key for entities.
 
 
 
 
 
Collection of utils for creating expressions
A (SPARQL) fragment is a unifying abstraction for queries and graph patterns which allows treating both as tables.
 
 
This is a binary relation used to relate two concepts to each other
 
A ternary relation - it can e.g.
 
 
 
 
A relation with multiple source and target variables
 
Interface with several default methods for working which an object that holds an Element.
Not yet used - Interface for sparql-based objects that are partitioned by certain variables
A relation with an additional mapping of variables to custom objects
 
 
 
 
 
 
 
 
A SPARQL concept with a defined ordering
A query where a subset of the mentioned vars are used to partition its result set.
Special case of a query partitioned by a single variable
 
 
 
The projection builder is used to specify which attributes to fetch.
A relation that in addition has a variable for the property
Execution of this kind of queries always returns (jena) ressources whose .getModel() method has the corresponding micrograph attached.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
There are multiple ways to represent a relation: - as a path of property uris (TODO we could extend this with a propery path language), "foaf:knows" - as two variables, followed by a '|' and a graph pattern, e.g.
TODO What if we want to express mandatory attributes in the projection? In that case, this actually translates to a restriction on the concept - i.e.
 
 
 
A triple-based virtual predicate.
FIXME This class is indended to be analoguous to the Fragment hierachy.