- This optional configuration step is only applicable to VIVO installations - running in RDB mode (See section Choose Triple Store - for details). - VIVO uses the Pellet engine to perform reasoning, which runs in the - background at startup and also when the knowledge base is edited. VIVO - continues serving pages while the reasoner continues working; when the - reasoner finishes, the new inferences appear. Inferred statements are - cached in a database graph so that they are available immediately when - VIVO is restarted. -
-- By default, Pellet is fed only an incomplete view of your ontology - and only certain inferences are materialized. These include rdf:type, - rdfs:subClassOf, owl:equivalentClass, and owl:disjointWith. This mode - is typically suitable for ontologies with a lot of instance data. If - you would like to keep the default mode, skip to the next step. -
-- To enable "complete" OWL inference (materialize all significant - entailed statements), open "vitro-core/webapp/config/web.xml" and - search for PelletReasonerSetup. -
-- Then change the name of the listener class to - PelletReasonerSetupComplete. Because "complete" reasoning can be very - resource intensive, there is also an option to materialize nearly all - inferences except owl:sameAs and owl:differentFrom. -
-- This is enabled by specifying PelletReasonerSetupPseudocomplete. - For ontologies with large numbers of individuals, this mode can offer - enormous performance improvements over the "complete" mode. -
-- Finally, a class called - PelletReasonerSetupPseudocompleteIgnoreDataproperties is provided to - improve performance on ontologies with large literals where data - property entailments are not needed. -
-