If class A is equivalent to class B, it means that class A is subclass of B and class B is subclass of A.
Since the class tree shows the subclass relationship, it is showing SpicyPizza as a subclass of SpicyPizzaEquivalent and SpicyPizzaEquivalent as a subclass of SpicyPizza. This is normal and works as intended. Regards, Irene Polikoff Executive Partner, TopQuadrant tel: 914-777-0888/ cell: 914-329-8576 www.topquadrant.com -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Christoph Sent: Monday, October 13, 2008 12:17 PM To: TopBraid Composer Users Subject: [tbc-users] Pizza Ontology, Inference Loop I used the Pellet reasoner for the Pizza ontology. Its output is the following: SpicyPizzaEquivalent - SpicyPizza - SpicyPizzaEquivalent - SpicyPizza - etc..... There is an endless loop. What is the problem in this case? I also have another ontology, that defines the class accommodation as equivalent to accommodation_service. Both are subclasses of Thing. If I run the reasoner, those classes are not listed anymore in the classes tree view under thing. They actually have disappeared, I can find them using the search, but if I add them to the basket and click on them to view their position in the tree view, they do not appear.... Are there any problems with the equivalent classes in Topbraid Composer? Why is there an endless loop? In Protege, both ontologies work without any problems. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
