Unlike other methods, this method does not work incrementally: each time the source trace is modified, the whole computed trace is re-generated.
This method applies a SPARQL CONSTRUCT query to the source trace.
yes (see below)
origin) is not provided,
the model (resp. origin) of the source trace will be used instead.
scope parameter accepts three values:
trace(the default): the SPARQL query only has access to the obsels of the source trace.*
base: the default graph is the union of all the information contained in the base (including subbases). The GRAPH keyword can be used to filter information per graph. Note that this is concetually clean, but very inefficient with the current implementation.
store: the default graph is the entire content of the underlying triple-sore. The GRAPH keyword can be used to filter information per graph. Note that this is only safe if all users are allowed to access any stored information. For this reason, this option is disable by default. To enable it, the configuration
sparql.allow-scope-storemust be set to
inherit is set (with any value),
then the produced obsels will inherit from their source obsel
all the properties that are not explicitly set by the CONSTRUCT.
That includes properties in the
This allows to greatly simplify SPARQL queries that are mostly
filtering and or augmenting obsels, rather than synthetizing new ones.
Note however that if the obsel has several source obsels,
the behabiour is unspecified.
Note also that this mechanism can access the source obsels regardless of the
The SPARQL query can contain magic strings of the form
that will be replaced by the value of
an additional parameter named
Note that the following special parameters are automatically provided:
|special parameter name||replaced by|
||The URI of the computed trace.|
||The URI of the source trace.|