Processor can validate request payloads against SPIN and SHACL. The constraints are defined as part of the LDT ontology. https://github.com/AtomGraph/Processor
On Sat, 5 Mar 2022 at 19.35, Andy Seaborne <a...@apache.org> wrote: > > > On 04/03/2022 17:24, Moritz Orth wrote: > > Hello everyone, > > > > I’m currently playing around with SHACL in Jena and just asked myself: > Can Fuseki validate data against SHACL shapes prior to inserting them into > the graph, refusing to add them when they don’t conform with the shapes? > > No, not currently. > > Andy > > > > > The docs under https://jena.apache.org/documentation/shacl/index.html < > https://jena.apache.org/documentation/shacl/index.html> show that > something like this is possible using the Java API directly, using > GraphValidation.update(). Fuseki allows for creating a SHACL validation > report after inserting some data, however I cannot see a possibility to > achieve this kind of transaction rollback behaviour that I do with the API. > > > > Is there some kind of operation mode for Fuseki that allows you to > specify some SHACL shapes on startup, and then validate all triple > insertion requests against those shapes? > > > > Thanks in advance for some guidance on the topic. > > > > Best regards > > Moritz > > > > >
