If I had three OntModels, each with their own OntDocumentManager,
FileManager, and choice of reasoner,
OntModel ontoA
OntModel ontoB
OntModel ontoCommon
and I then do the following
ontoA.addSubModel(ontoCommon)
ontoB.addSubModel(ontoCommon)
how is
Many thank's Andy.
I missed the page
https://jena.apache.org/documentation/fuseki2/data-access-control#graph-acl
I will explore the possibilities offered by a graph by graph control.
For my original problem, I found a solution by avoiding the standard UI of
fuseki.
I installed Yasgui as UI and
On 24/11/2019 11:51, Claude Warren wrote:
If you want to restrict access to datasets alone you can probably do that
in Fuseki. If you want to grant access to specific models within a dataset
you will probably need to use the Permissions layer.
The permissions layer will allow you to restrict
If you want to restrict access to datasets alone you can probably do that
in Fuseki. If you want to grant access to specific models within a dataset
you will probably need to use the Permissions layer.
The permissions layer will allow you to restrict access to graphs or even
down to the triple
Marc,
An RDF Model can not hold quads. That is what a Dataset is for.
TriG is a dataset format, so is N-Quads.
The only design choice Jena has made is that reading TriG into a unnamed
graph is that it takes the default graph from the dataset. Implicitly
merging data is a bad idea. If you
Thanks Andy for your very informative email. We are using trig precisely
because we are dealing with quads (i.e named graphs).
As I said earlier, I am going to use DatasetGraph for now, as suggested by
Martynas, but I think that something should be done in Jena so there is a Jena
reader for
