jena-shacl has API calls that do imports processing as well as ones that
don't. The caller has to say they want import processed.
The Fuseki SHACL validation service that accepts a shape RDF file does
not process imports. This is so the server does not make out going HTTP
requests (SSRF).
To get that, the client need to resolve the imports and send the
combined shapes graph to Fuseki.
Andy
On 11/08/2026 14:15, Chavdar Ivanov wrote:
Dear all,
Can you confirm that it is possible to load SHACL constraints from a ttl that
is posted on the web and the import is done like this
So one .ttl is loaded and inside there is this (as an example)
test: owl:imports
<https://<https://cimbion.blob.core.windows.net/valimate/constraints/RDFS/CoreEquipmentProfile.ttl>>xyz.net/<https://cimbion.blob.core.windows.net/valimate/constraints/RDFS/CoreEquipmentProfile.ttl>>abc.ttl><https://cimbion.blob.core.windows.net/valimate/constraints/RDFS/CoreEquipmentProfile.ttl>>
The expectation is that the engine goes and fetches abc.ttl from the web and
loads the constraints that are inside. The idea is that the abc.ttl is in a
public gitHub repo
If it is possible, are there some specific settings when triggering the
validation.
Note, all works if the path to abc.ttl is local.
Best regards
Chavdar
