I need SPIN because my SHACL sh:constraint sh:sparql SPARQL query calls
SPIN functions (some stock and some custom).
I flattened as suggested into a single turtle file.
I had some test values in the schema so I piped the schema back in as the
test data and got some results (yay!).
Now the
Has anyone else noticed the following problem. I define an sh:constraint on
a class and all is well. If I define a second one on the same class all is
fine until I reload the graph, and then one of them 'disappears'. TBC knows
that I had a second one, because it now tells me that I have an
I am not aware of a glitch that would remove sh:constraint triples.
Usually TBC leaves such triples in the files untouched. Could you send
me a file with instructions on what exactly made the triples disappear?
Also, it rather sounds like the sh:sparql (now: sh:select) triple may
have
On 10/08/2016 2:51, Jack Hodges wrote:
I need SPIN because my SHACL sh:constraint sh:sparql SPARQL query
calls SPIN functions (some stock and some custom).
The SPIN functions can be registered with the SPARQL engine separately
and do not need to be in the same graph as the SHACL data. The
That is what I am saying. The validation example is reporting violations on
classes (focus nodes are all classes) while TBC is reporting violations on
instances. I am trying to reproduce the results that TBC shows.
Jack
Sent from my iPad
> On Aug 9, 2016, at 6:17 PM, Holger Knublauch
