> I installed BigOWLIM 3.4 (on Windows 7) within Sesame as explained in the 
> manual using the default settings
> Repository ID [bigowlimTest]:
> Repository title [BigOWLIM Test store]:
> Set of rules [owl-max]:
> No Persistence (true|false) [true]:
> Storage folder [owlimTest-storage]:
> entity index size [200000]:
> imports(';' delimited) [./ontology/owl.rdfs]:
> defaultNS(';' delimited) [ http://www.w3.org/2002/07/owl#]:
> Repository created
> 
> I loaded my collection of triples in bigowlimTest using the open-rdf 
> workbench interface.
> So far so good.
> 
> Now I want to put Joseki in front of the same bigowlimTest database to be 
> able to use some SPARQL 1.1 aggregate functions.
> 
> I know I need to edit the Joseki configuration file (have been doing this 
> before to connect to a TDB repository).
> 
> This is what I find in the manual.
> <#service1>
> rdf:type joseki:Service ;
> rdfs:label "service point" ;
> joseki:dataset otjena:bridge ;
> joseki:serviceRef "sparql" ;
> joseki:processor joseki:ProcessorSPARQL ;
> .
> 
> [] ja:loadClass "com.ontotext.jena.SesameVocab" .
> otjena:DatasetSesame rdfs:subClassOf ja:RDFDataset .
> otjena:bridge rdf:type otjena:DatasetSesame ;
> rdfs:label "BigOWLIM repository" ;
> otjena:datasetParam "./location" .
> 
> which I'm able to understand except for the datasetParam part of which I 
> expect that it needs to point to the location of the repository.
> Is this the case?
> If yes, I do not seem to be able to find the location.
> I expected it to be in C:/Users/paul/AppData/Roaming/Aduna/OpenRDF 
> Sesame/repositories, but I don't see it.


I meanwhile discovered the repositories at 
C:\windows\system32\config\systemprofile\AppData\Roaming\Aduna\OpenRDF 
Sesame\repositories

What does this mean for
> otjena:bridge otjena:datasetParam "./location" . ?

otjena:bridge otjena:datasetParam "./bigowlimItest". ???


Paul


















_______________________________________________
OWLIM-discussion mailing list
[email protected]
http://ontotext.com/mailman/listinfo/owlim-discussion

Reply via email to