[
https://issues.apache.org/jira/browse/STANBOL-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433248#comment-13433248
]
Alessandro Adamou commented on STANBOL-681:
-------------------------------------------
A Tight (aggressive) connectivity policy has been implemented for sessions and
spaces. This is enough for closing this ticket. For more sophisticated policies
please open a new one.
> Tighter ontology import schemes for ontology collectors
> -------------------------------------------------------
>
> Key: STANBOL-681
> URL: https://issues.apache.org/jira/browse/STANBOL-681
> Project: Stanbol
> Issue Type: Improvement
> Components: Ontology Manager
> Reporter: Alessandro Adamou
> Assignee: Alessandro Adamou
>
> The shape of import graphs in ontology network can affect the way axioms are
> interpreted by libraries and tools such as the OWL API.
> For example, if we have:
> :O1 owl:imports :O2 .
> :O1 owl:imports :O3 .
> and in :O2 the triple <:A myvoc:loves :B>
> and in :O3 the triple <myvoc:loves rdf:type owl:ObjectProperty>
> then a library that parses import subgraphs in pre-order visit will interpret
> the triple <:A myvoc:loves :B> as an Annotation instead of an Object Property
> Assertion. As a consequence, OWL reasoners will ignore that triple. This
> happens e.g. in the OWL API and Protégé.
> If the import graph had an additional import statement
> :O2 owl:imports :O3 .
> then <:A myvoc:loves :B> would be interpretred correctly.
> We should make sure that Scopes, Spaces and Sessions in the Stanbol Ontology
> Manager provide import statements that minimize the risk of erroneous axiom
> interpretations.
--
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
