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 2011/07/05 14:12:16 UTC

[jira] [Created] (STANBOL-250) Avoid reloading the target ontology before reasoning in Classify REST service

Avoid reloading the target ontology before reasoning in Classify REST service
-----------------------------------------------------------------------------

                 Key: STANBOL-250
                 URL: https://issues.apache.org/jira/browse/STANBOL-250
             Project: Stanbol
          Issue Type: Improvement
          Components: KReS
            Reporter: Alessandro Adamou
            Priority: Minor


In r1142637 a temporary quick fix/hack was introduced in the reasoners.web Classify RESTful service. It causes the ontology to classify to be serialized in-memory and be reloaded before classification, lest OWL properties be erroneously marked as annotation properties.

Whether this is a consequence of ontology scope management in Session Spaces, it is to be investigated.

This ticket could be a part of a major issue where all reasoning services are overhauled.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (STANBOL-250) Avoid reloading the target ontology before reasoning in Classify REST service

Posted by "Alessandro Adamou (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/STANBOL-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessandro Adamou resolved STANBOL-250.
---------------------------------------

    Resolution: Fixed
    
> Avoid reloading the target ontology before reasoning in Classify REST service
> -----------------------------------------------------------------------------
>
>                 Key: STANBOL-250
>                 URL: https://issues.apache.org/jira/browse/STANBOL-250
>             Project: Stanbol
>          Issue Type: Improvement
>          Components: Ontology Manager, Reasoners
>            Reporter: Alessandro Adamou
>            Priority: Minor
>
> In r1142637 a temporary quick fix/hack was introduced in the reasoners.web Classify RESTful service. It causes the ontology to classify to be serialized in-memory and be reloaded before classification, lest OWL properties be erroneously marked as annotation properties.
> Whether this is a consequence of ontology scope management in Session Spaces, it is to be investigated.
> This ticket could be a part of a major issue where all reasoning services are overhauled.

--
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

        

[jira] [Updated] (STANBOL-250) Avoid reloading the target ontology before reasoning in Classify REST service

Posted by "Alessandro Adamou (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/STANBOL-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessandro Adamou updated STANBOL-250:
--------------------------------------

    Component/s:     (was: KReS)
                 Reasoners
                 Ontology Manager

> Avoid reloading the target ontology before reasoning in Classify REST service
> -----------------------------------------------------------------------------
>
>                 Key: STANBOL-250
>                 URL: https://issues.apache.org/jira/browse/STANBOL-250
>             Project: Stanbol
>          Issue Type: Improvement
>          Components: Ontology Manager, Reasoners
>            Reporter: Alessandro Adamou
>            Priority: Minor
>
> In r1142637 a temporary quick fix/hack was introduced in the reasoners.web Classify RESTful service. It causes the ontology to classify to be serialized in-memory and be reloaded before classification, lest OWL properties be erroneously marked as annotation properties.
> Whether this is a consequence of ontology scope management in Session Spaces, it is to be investigated.
> This ticket could be a part of a major issue where all reasoning services are overhauled.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira