[STANBOL-332] Have OntoNet manage graphs in Clerezza natively.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.9.0-incubating
• Component/s: Ontology Manager
• Assignee: Unassigned
• Reporter: Alessandro Adamou
• Created: 29/Sep/11 18:02
• Updated: 09/May/12 13:48
• Resolved: 20/Dec/11 10:02

Description

OntoNet has been managing scopes, spaces and sessions so far, by creating OWL API objects that live throughout the whole Stanbol lifecycle, and are serialized for Web Services.

The current implementation creates OWL ontology objects that persist in memory even when they are not being used. This has the advantage to provide an axiom-oriented view on RDF graphs, which is very useful for applications and users that dig OWL(2).

However, it is also inefficient for a number of reasons:

• memory occupation with data that essentially replicate the content of the persistence layer
• no slick reaction to changes in low-level graphs. If an imported ontology is updated, or a new import is added, pre-existing axioms should be re-interpreted (e.g. for classification and other reasoning tasks). This generally doesn't happen, unless the ontologies are serialized and re-loaded in the OWL API ontology manager.
• non OWL-aware applications that use the OntoNet Java API are forced to handle OWL if they need to access RDF graphs.

An ideal solution would be to avoid loading ontologies in OWLOntologyManager objects when ontology scopes and sessions are set up. Ontology network information could be stored in the Clerezza TcManager just like every other RDF graph, and only when the content of a scope is requested as an OWL ontology it is brought up that way, to be then garbage-collected.

Issue Links

• incorporates: STANBOL-337 Clerezza converters to handle TripleCollection instead of MGraph
• is part of: STANBOL-165 Efficient storage of Ontology in Persistence Store
• supercedes: STANBOL-145 [KReS] Persistence storage management in OntoNet