[
https://issues.apache.org/jira/browse/STANBOL-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205395#comment-13205395
]
Stephen Bayliss commented on STANBOL-426:
-----------------------------------------
Testing on svn rev 1241972:
Using the new GraphContentInputSource, passing tcManager in the constructor, is
able to handle our large graphs now.
Identifiers are now passed back by the methods adding these, which is great.
However there seems to be a secondary issue that more than one graph is created
(or two graph identifiers for the sae graph? is that even possible?). We are
seeing a graph with the identifier returned by the method, but also seeing a
graph with the identifier of the form:
org.apache.stanbol.ontologymanager.ontonet.api.io.GraphContentInputSource-1328882620149
(for reference, the graph ID returned by the method is
ontonet::http://stanbol.apache.org/1328882278969)
> 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
