If a magic property is not resolving, have you tried renaming its file
to something like .spin.ttl - this should have the system register all
SPIN functions and magic properties globally.
Holger
On 25/07/2019 04:25, Jack Hodges wrote:
I was debugging this problem with Steve and we found that
I was debugging this problem with Steve and we found that the
IterateOverSelect is not executing because it has two magic property calls
referenced and they are not being resolved. Their graphs 'are' being
imported, and everything in them can be seen in the 'query' tab in SPARQL
MOTION and, eve
I am attaching a script that looks as in the screenshot:
You need to make sure that the PerformUpdate specifies the target
graphs, using the GRAPH keyword. Otherwise it doesn't know where the
triples shall go.
The Merge step is just there as a dummy placeholder for some module that
handles t
I have a question. Does anyone have an example of an IterateOverSelect that
has a body that performs an insert on the results of the IterateOverSelect
variables?
My Intent: execute a IterateOnSelect SELECT that produces multiple rows of
several bindings, use body of IterateOnSelect to INSERT ea