[
https://issues.apache.org/jira/browse/STANBOL-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Adamou resolved STANBOL-384.
---------------------------------------
Resolution: Fixed
Assignee: Alessandro Adamou
Import management policy (with options for flattening, merging or preserving
the import tree) is now implemented.
> GET calls on managed ontology resources do not include import statements
> ------------------------------------------------------------------------
>
> Key: STANBOL-384
> URL: https://issues.apache.org/jira/browse/STANBOL-384
> Project: Stanbol
> Issue Type: Bug
> Components: Ontology Manager
> Reporter: Alessandro Adamou
> Assignee: Alessandro Adamou
> Labels: import
>
> Suppose an ontology X.owl imports Y.owl and Z.owl
> if POSTing X.owl to a Scope or a Session via e.g.
> curl -d @X.owl -H "Content-type: application/rdf+xml"
> http://localhost:8080/ontonet/ontology/Scope1
> or
> curl -d @X.owl -H "Content-type: application/rdf+xml"
> http://localhost:8080/ontonet/session/alessandro-20111123145420
> when GETting the corresponding resources (scopeId/ontologyId or
> sessionId/ontologyId), the imports to Y.owl and Z.owl are not included, and
> so are the interpretations of their referenced entities (e.g. object and data
> properties described in Y become annotation properties).
> Import statements are included correctly if the GET is performed directly on
> a Scope or Space resource.
> This could be a bug of the OntoNet offline mode implementation kicking in
> even if tha Stanbol offline mode is not set.
--
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
