[
https://issues.apache.org/jira/browse/STANBOL-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212714#comment-13212714
]
Alessandro Adamou commented on STANBOL-426:
-------------------------------------------
Ok so I am setting the following conditions for this ticket to be resolved:
1. Implement garbage-collection for managed ontologies : Stanbol could be
configured to remove a graph from the Clerezza backend when (a) there are no
more "handles" to it (scopes, sessions etc.) and (b) the graph was created at
the same time as its addition to a scope or session.
2. A smart policy for handling updates
3. Full support for OWL version IRI (might actually solve 1 and 2 if version
IRIs are forged properly)
> Ability to manage identifiers of ontologies added to spaces
> -----------------------------------------------------------
>
> Key: STANBOL-426
> URL: https://issues.apache.org/jira/browse/STANBOL-426
> Project: Stanbol
> Issue Type: Story
> Components: Ontology Manager
> Reporter: Stephen Bayliss
> Priority: Minor
>
> We have a use case which involves synchronising ontologies stored in a KReS
> custom space with content from an external system, which itself identifies
> units of content (ie the ontology being added to KReS) using URIs.
> When adding an ontology using an OntologyInputSource there doesn't seem to be
> any way of reconciling the identity of the ontology in the custom space with
> the content identifier URI from the external system.
> This means that when content in the external system is modified or deleted,
> there is no easy way to determine which ontology in the custom space should
> be updated/deleted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
