Querying with complex class expressions

[GoogleCodeExporter]

Right now ELK does not well support retrieving all instances of classes which 
are not named (atomic) classes. A common workaround is to introduce a fresh 
class name, make it equivalent to the class expression, and query for its 
instances.

However, this isn't ideal since it leads to a technically non-equivalent 
ontology.

A way to improve it is to hide all these steps from the user and avoid 
re-classification via incremental reasoning (issue 9). The ontology should 
remain intact after the querying is done, i.e., it should not contain new class 
names or axioms.

Original issue reported on code.google.com by pavel.kl...@gmail.com on 8 Aug 2012 at 10:56

• Blocked on: Incremental reasoning #9