Thank you for the links. Very informative.
--
You received this message because you are subscribed to the Google Group
"TopBraid Suite Users", the topics of which include the TopBraid Suite family
of products and its base technologies such as SPARQLMotion, SPARQL Web Pages
and SPIN.
To post
On 24/09/2016 0:34, Jack Hodges wrote:
We got it working and even in Jena. I am not sure what the problem was
because I am bucking a deadline but am relieved nonetheless. The new
SHACL violations have removed the subject predicate object violation
parameters from the SHACL violations display.
We got it working and even in Jena. I am not sure what the problem was
because I am bucking a deadline but am relieved nonetheless. The new SHACL
violations have removed the subject predicate object violation parameters
from the SHACL violations display. When I run the validator I am only
I will check to make sure that my inheritance is correct. I think that what I
need is better and more complete documentation of SHACL and SPARQL and SPIN
interactions.
--
You received this message because you are subscribed to the Google Group
"TopBraid Suite Users", the topics of which
Holger,
Interestingly your file doesn't follow the naming conventions you suggested
that I use when I first mentioned the:
WARN [ModalContext] (E_Function.java:89) - URI <...> has no registered
function factory
error. It would be better, for me, if you could enumerate all of the
contexts in
This scenario seems to work fine for me, see the attached files. I would
need a copy of your files or comparable details to reproduce this.
Holger
On 21/09/2016 6:09, Jack Hodges wrote:
I have SHACL (SPARQL) constraints that worked 'fine' under TBCME
5.1.3. In these constraints I am using
