Incremental Sparql (ISparql)¶
This method applies a SPARQL SELECT query to the source trace, and builds new obsels with the result.
yes (see below)
The SPARQL query must be a SELECT query.
Its WHERE clause must contain the magic string
which will be replaced with a subquery.
For each obsel of the source trace,
this subquery will yield its URI, begin timestamp and end timestamp as
You may then complement the WHERE clause as you see fit.
Each row returned by your SELECT query will create a new obsel in the computed trace; each variable will add information to the obsel, based on the name of the variable, as explained by the table below. Note that variables followed with a star (*) are mandatory :
||a source obsel (
||the obsel type (
||the begin timestamp (
||the end timestamp (
||the begin datetime (
||the end datetime (
||the subject of the obsel (
|(any name starting with
||an additional source obsel (
|(any other name)||an attribute built by concatenating the variable name to the namespace of the computed trace’s model|
origin) is not provided,
the model (resp. origin) of the source trace will be used instead.
The SPARQL query can contain magic strings of the form
that will be replaced by the value of
an additional parameter named
For the sake of performance, this method works incrementally:
everytime the trace is re-computed,
the subquery inserted at
magically selects only source obsels that have not been considered yet.
As a consequence,
each results of the query should not depend
on information that appears “later” in the trace than
Otherwise, the content of the computed trace may vary unpredictably,
depending on when the trace is actually computed.
If you can not guarantee the property above, then you should probably use the sparql method below instead, understanding that it will not behave as well performancewise.