[
https://issues.apache.org/jira/browse/STANBOL-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206786#comment-13206786
]
Stephen Bayliss commented on STANBOL-426:
-----------------------------------------
I think it would be useful if the ontology management API could some how manage
this and have methods that can both deal with content managed within the store
and external content (registered in scopes and spaces).
Ie the ability to both deregister an ontology from a space, and the ability to
remove the underlying graph (when deregistering, or perhaps a separate method?).
And when adding one could extend methods to cover the use-cases of replacing an
existing graph, adding a new graph (eg new version), merging with the exiting
graph, etc.
> 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
