You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Alessandro Adamou (JIRA)" <ji...@apache.org> on 2012/11/15 13:24:12 UTC

[jira] [Resolved] (STANBOL-305) Anonymous ontology management policies

     [ https://issues.apache.org/jira/browse/STANBOL-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessandro Adamou resolved STANBOL-305.
---------------------------------------

    Resolution: Implemented
      Assignee: Alessandro Adamou

With an algorithm for generating public keys in place, and unit-tested support for manual and automatic overrides, this ticket can now be closed.
                
> Anonymous ontology management policies
> --------------------------------------
>
>                 Key: STANBOL-305
>                 URL: https://issues.apache.org/jira/browse/STANBOL-305
>             Project: Stanbol
>          Issue Type: Improvement
>          Components: Ontology Manager
>            Reporter: Alessandro Adamou
>            Assignee: Alessandro Adamou
>
> OntoNet currently works effectively with named ontologies. On the other hand, the way anonymous ontologies are managed is not uniform and sub-optimal. 
> For example, when adding an anonymous ontology to a space, its axioms are copied into the space top ontology, because import statements cannot be generated. This way, removing an anonymous ontology from a scope or space becomes extremely awkward.
> Design and implement a policy that works for named and anonymous ontologies alike.
> One solution could be to treat physical locations as logical identifers for anonymous ontologies, since they are also unique references.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira