CODEWITHSUNDEEP
owlsesame
JasperTack
JasperTack

Reputation: 4447

owlim library use of configuration file

I am trying to work with the owlim library to edit the owl ontology file. I started with the 'getting-started' example code included in the owl library. When I use the library with this example code it all works perfect. It uses de owlim.ttl file to configure the repository and this contains the path to this repository too:

(owlim.ttl:)

@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix rep: <http://www.openrdf.org/config/repository#>.
@prefix sr: <http://www.openrdf.org/config/repository/sail#>.
@prefix sail: <http://www.openrdf.org/config/sail#>.
@prefix owlim: <http://www.ontotext.com/trree/owlim#>.

[] a rep:Repository ;
   rep:repositoryID "owlim" ;
   rdfs:label "OWLIM Getting Started" ;
   rep:repositoryImpl [
     rep:repositoryType "openrdf:SailRepository" ;
     sr:sailImpl [
       owlim:ruleset "owl-horst-optimized" ;
       owlim:entity-index-size "5000000" ;
       owlim:cache-memory "180m" ; 
       sail:sailType "swiftowlim:Sail" ; 
       owlim:noPersist "false" ;
       owlim:storage-folder "storage" ;
       owlim:base-URL "http://example.org/owlim#" ;
       owlim:repository-type "in-memory-repository" ;
       owlim:imports "./sesame/example.rdfs" ;
       owlim:defaultNS "http://example.org/owlim#" ;
      ]
   ].

On the documentation site they explicitly say that:

'With the example set up, OWLIM-Lite loads two ontologies at start up as specified by the imports parameter in the repository configuration file, i.e. owlim.ttl',

but when I change that path to another file, I still get the same output like before. Even when I try to change something in this example.rdfs repository, the results of the queries don't change. Does anybody know what the problem could be? Is the path specified somewhere else?

Upvotes: 1

Views: 647

Answers (1)

Barry
Barry

Reputation: 71

The imports configuration parameter is used for once only initialisation of the repository with read-only schema. Once created, these statements can not be changed, so when you later modify this parameter and restart using an old repository, you will not see any differences.

In order to use a different imported schema, you must create a new repository.

Upvotes: 2

Related Questions