Incomplete clean up of elk internal class expressions placeholders

[GoogleCodeExporter]

Hello,

we are using the new feature of elk to use anonymous class expressions. During 
that we found a problem. 
After using the isSatisfiable method for a class expression it will show up as 
a result in the next call for getEquivalentClasses with the same expression.

I assume this is a bug, due to an incomplete clean up of the previous call.

Please find attached a test project/case, to illustrate the issue.

Affected version: elk 0.4.0 using owlapi 3.4.4

Original issue reported on code.google.com by HDie...@lbl.gov on 2 Aug 2013 at 11:37

Attachments:

• elk-bug.zip

[GoogleCodeExporter]

Thanks for reporting the issue!
We have reproduced the bug.
While we are fixing it, a workaround for a moment would be not to call several 
queries consequently for the same complex class expressions (in your example, 
you first check satisfiability and then retrieve equivalent classes). 

Reproduced in ec8eb4c20e7a1a683ea43330a1043f7257be246b

Original comment by ykazako...@gmail.com on 5 Aug 2013 at 9:28

• Changed state: Accepted
• Added labels: 0.4.1, Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Thank you for your response.
The proposed work-around until a fixed version is available is very much 
appreciated.
The new support for complex class expressions is very helpful feature.

Original comment by HDie...@lbl.gov on 5 Aug 2013 at 4:43

[GoogleCodeExporter]

Fixed in 844b8114ed502c97b7ee05d3d94b41fa3821b55f

The fixed version should be available in nightly builds and will be released in 
0.4.1

Original comment by ykazako...@gmail.com on 9 Aug 2013 at 5:29

• Changed state: Fixed