Warning "Ignoring the change not applicable to the current onttolgy: + change"

[GoogleCodeExporter]

Line 928 in org.semanticweb.elk.owlapi.ElkReasoner.java (r994) has the 
following:

LOGGER_.warn("Ignoring the change not applicable to the current onttolgy: + 
change");

Firstly, there is a typo "onttolgy" and the "+ change" should not occur within 
the string.

Secondly, when classifying an ontology through the OWL API as explained in the 
user page "Using ELK from OWL API", this warning is logged repeatedly during 
retrieval of inferred axioms. Is this expected? Perhaps the logging level 
should be decreased.

Original issue reported on code.google.com by frantise...@gmail.com on 18 Sep 2012 at 1:34

[GoogleCodeExporter]

Yes please change this. 
Perhaps reduce the log level to trace (as in all of the other methods in this 
class):

if(LOGGER_.isTraceEnabled()) {
    LOGGER_.trace("Ignoring the change not applicable to the current ontology: "+ change);
}

Original comment by HDie...@lbl.gov on 18 Sep 2012 at 8:23

[GoogleCodeExporter]

OK, I will look into that. I thought the situation when a different ontology is 
changed should be rare (but still should not be ignored because the changed 
ontology can be in the import), but I now see that it is quite possible, e.g., 
in the code for taxonomy construction.

Original comment by ykazako...@gmail.com on 19 Sep 2012 at 5:00

• Added labels: 0.4, Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by ykazako...@gmail.com on 19 Sep 2012 at 7:35

• Changed state: Accepted

[GoogleCodeExporter]

So there are two issues here. 

First, ELK currently ignores changes made to an ontology imported (directly or 
indirectly) from the current ontology (i.e. the one passed to the reasoner when 
it was created). I'm looking into that now. 

Second, the warning occurs because ELK receives notifications about *all* 
changes made to *all* ontologies managed by the OWLOntologyManager which loaded 
(or created) the current ontology. This is how the OWL API change notification 
mechanism works. In this particular case, the resulting ontology, which only 
contains inferred subsumptions, is managed by the same OWLOntologyManager. This 
is obviously unnecessary. I've modified the example to use another 
OWLOntologyManager so the problem is avoided. I suspect some user application 
scenarios can be similar.

Original comment by pavel.kl...@gmail.com on 5 Jun 2013 at 8:27

[GoogleCodeExporter]

Fixed in 
https://github.com/klinovp/elk/commit/c316c9d4bddb2ea5b8e927d5f09f36a8f18fa699

Original comment by pavel.kl...@gmail.com on 5 Jun 2013 at 10:25

• Changed state: Fixed