[STANBOL-384] GET calls on managed ontology resources do not include import statements

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0-incubating
• Component/s: Ontology Manager
• Labels: import
• Assignee: Alessandro Adamou
• Reporter: Alessandro Adamou
• Created: 22/Nov/11 22:55
• Updated: 09/May/12 13:48
• Resolved: 09/Jan/12 17:44

Description

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.

Issue Links

• blocks: STANBOL-247 More robust OntoNet session management
• blocks: STANBOL-196 Dynamic ontology scope IRI naming
• is related to: STANBOL-178 Rule management must support an offline mode