There is a new release of the SHACL API (based on Jena) available now,
1.0.1:
https://github.com/TopQuadrant/shacl
This API can be regarded as a "reference" implementation of the W3C
SHACL standard. It followed the evolution of SHACL and now covers all
features from the specifications.
OK, I promise to update that section when I have my system working. I'm
struggling a bit with TDB + inferencing since most examples of inferencing
setup are for mem but I'm sure I'll get that after a few more plays.
Nick
From: Andy Seaborne
On 08/10/17 09:40, Laura Morales wrote:
Note: the json-ld writer is from a different project. Fuseki isn't doing
anything for JSON-LD except passing it to the writer with the same
information that is available with Turtle or any other syntax.
Which 3rd-party library is Fuseki using to
Hi Nick,
It would be great if you could write some documentation. "@@" are indeed
"to do" markers.
There are some example configurations in:
https://github.com/apache/jena/tree/master/jena-fuseki2/examples
Andy
On 08/10/17 10:24, nicholas@csiro.au wrote:
Hi all,
On the Fuseki2
Hello George,
right now it's really hard to help you. A complete query + sample data
is missing to reproduce it. In addition, the second query seems to be an
invalid SPARQL query - at least I don't see grouping by ?id and the
other values are not aggregates. I don't think this is valid in
Hi all,
On the Fuseki2 configuration page,
https://jena.apache.org/documentation/fuseki2/fuseki-configuration.html , the
section titled 'Inference' just has '@@' in it. Is this a mistake or does '@@'
mean something I don't understand?
I realise there are snippets of Fuseki inferencing config
Please - a complete, verifiable, minimal example.
Complete query, small amount of data.
Snippets remove details that may matter.
With a complete, verifiable, minimal example we can agree on what the
question is.
Indeed, it is not clear your output is even from Jena. The JSON
formatting is
By the way, I was looking at the examples... and I was wondering... Since Jena
seems to support JSON-LD output in various formats ("compacted", "expanded",
"flattened"), can this behavior be controlled from Fuseki? Either per-query, or
maybe with some global setting? Or can I only change the
> Note: the json-ld writer is from a different project. Fuseki isn't doing
> anything for JSON-LD except passing it to the writer with the same
> information that is available with Turtle or any other syntax.
Which 3rd-party library is Fuseki using to generate JSON-LD output? Maybe I can
get in
