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 [email protected] on 8 Aug 2012 at 10:56

• Blocked on: Incremental reasoning #9

[GoogleCodeExporter]

Original comment by [email protected] on 8 Aug 2012 at 10:57

• Now blocked on: Incremental reasoning #9

[GoogleCodeExporter]

Issue 17 has been merged into this issue.

Original comment by [email protected] on 3 Jun 2013 at 10:40

[GoogleCodeExporter]

Pushed to 0.5

Original comment by [email protected] on 5 Jun 2013 at 10:26

• Added labels: 0.5
• Removed labels: 0.4

[GoogleCodeExporter]

Fixed in v. 0.4.0 using incremental reasoning

Original comment by [email protected] on 19 Jul 2013 at 2:37

• Changed state: Fixed
• Added labels: 0.4
• Removed labels: 0.5