[
https://issues.apache.org/jira/browse/STANBOL-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Adamou updated STANBOL-304:
--------------------------------------
Description:
The root ontology of each ontology space (e.g. {scopeid}/core/root.owl and
{scopeid}/custom/root.owl) is managed as an actual OWLOntology object just like
actual ontologies loaded in the scope.
However this does not bring any benefit and creates clutter when managing
import statements and serialization of ontology scopes and spaces for RESTful
services.
Root ontologies can be generated on-the-fly for GET services on scopes and
spaces, so that import statements can be swiftly moved across spaces without
worrying about reloading the whole imports closure. Also, since they do not map
to actual files, we can remove .owl extensions (which should be reserved for
included ontologies).
As a consequence, OntologySpace#setTopOntology() methods would no longer make
sense and should be deprecated in the API, then removed altogether.
was:
The root ontology of each ontology space (e.g. {scopeid}/core/root.owl and
{scopeid}/custom/root.owl) is managed as an actual OWLOntology object just like
actual ontologies loaded in the scope.
However this does not bring any benefit and creates clutter when managing
import statements and serialization of ontology scopes and spaces for RESTful
services.
Root ontologies can be generated on-the-fly for GET services on scopes and
spaces, so that import statements can be swiftly moved across spaces without
worrying about reloading the whole imports closure. Also, since they do not map
to actual files, we can remove .owl extensions (which should be reserved for
included ontologies).
As a consequence, OntologySpace#setTopOntology() methods would no longer make
sense and should be deprecated then removed.
> Make root ontology management implicit in ontology spaces
> ---------------------------------------------------------
>
> Key: STANBOL-304
> URL: https://issues.apache.org/jira/browse/STANBOL-304
> Project: Stanbol
> Issue Type: Improvement
> Components: Ontology Manager
> Reporter: Alessandro Adamou
> Assignee: Alessandro Adamou
>
> The root ontology of each ontology space (e.g. {scopeid}/core/root.owl and
> {scopeid}/custom/root.owl) is managed as an actual OWLOntology object just
> like actual ontologies loaded in the scope.
> However this does not bring any benefit and creates clutter when managing
> import statements and serialization of ontology scopes and spaces for RESTful
> services.
> Root ontologies can be generated on-the-fly for GET services on scopes and
> spaces, so that import statements can be swiftly moved across spaces without
> worrying about reloading the whole imports closure. Also, since they do not
> map to actual files, we can remove .owl extensions (which should be reserved
> for included ontologies).
> As a consequence, OntologySpace#setTopOntology() methods would no longer make
> sense and should be deprecated in the API, then removed altogether.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
