Re: [topbraid-users] SHACL validation report from ModelConstraintValidator example - Questions

2016-08-15 Thread Holger Knublauch
On 16/08/2016 10:07, Jack Hodges wrote: I removed the SPIN content from my validation. I removed the instances from my graphs to a new graph. I changed the validateShapes flag to false. Locally in TBC I am still seeing different response (albeit a bit different now that validateShapes is set

Re: [topbraid-users] SHACL validation report from ModelConstraintValidator example - Questions

2016-08-15 Thread Jack Hodges
The SPINModuleRegistry.get().init() problem was a Siemens security issue which I got rid of but it didn't change the result I posted, which suggests that the SPIN functions are not available in the SPARQL queries in my SHACL templates. On Mon, Aug 15, 2016 at 5:07 PM, Jack Hodges

Re: [topbraid-users] SHACL validation report from ModelConstraintValidator example - Questions

2016-08-10 Thread Jack Hodges
Right, I forgot about that. I always hit the blue button. I'll try setting validateShapes to false. Thank you! Jack Sent from my iPad > On Aug 10, 2016, at 12:34 AM, Holger Knublauch wrote: > > > >> On 10/08/2016 12:53, Jack Hodges wrote: >> That is what I am

Re: [topbraid-users] SHACL validation report from ModelConstraintValidator example - Questions

2016-08-10 Thread Holger Knublauch
On 10/08/2016 12:53, Jack Hodges wrote: 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. TBC has a green and a blue button

Re: [topbraid-users] SHACL validation report from ModelConstraintValidator example - Questions

2016-08-09 Thread Jack Hodges
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

Re: [topbraid-users] SHACL validation report from ModelConstraintValidator example - Questions

2016-08-09 Thread Holger Knublauch
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

Re: [topbraid-users] SHACL validation report from ModelConstraintValidator example - Questions

2016-08-09 Thread Jack Hodges
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

Re: [topbraid-users] SHACL validation report from ModelConstraintValidator example - Questions

2016-08-08 Thread GMAIL
We separate our schemes and vocabularies normally. Thank you for the clarifications Holger! Sent from my Siemens iPhone > On Aug 8, 2016, at 4:49 PM, Holger Knublauch wrote: > > > >> On 9/08/2016 9:31, Jack Hodges wrote: >> I have looked at and run the

Re: [topbraid-users] SHACL validation report from ModelConstraintValidator example - Questions

2016-08-08 Thread Holger Knublauch
On 9/08/2016 9:31, Jack Hodges wrote: I have looked at and run the ValidationExample from the github archive and have looked carefully at the SHACL archive ModelConstraintValidator. These are very helpful and I encourage anyone playing with SHACL to look at them. This said, I have run into

[topbraid-users] SHACL validation report from ModelConstraintValidator example - Questions

2016-08-08 Thread Jack Hodges
I have looked at and run the ValidationExample from the github archive and have looked carefully at the SHACL archive ModelConstraintValidator. These are very helpful and I encourage anyone playing with SHACL to look at them. This said, I have run into a bit of a problem trying to extend the