Christoph, TBC implements a few "trivial" inferences for display purposes. However, these are in place only until a "true" inference process runs. At that point, TBC will show only asserted triples and triples inferred by the inferencer. We do this to avoid confusion as to where which inferred triple came from and also to avoid potential collisions.
I would recommend that you create a SPARQL CONSTRUCT query to create ?class rdfs:subClassOf owl:Thing triple for each class that is not a subject of any triple with rdfs:subClassOf predicate. You could then run it after you run Pellet and infer created triples. Or, you can customize inferencing to have Pellet as a first step and running this query as a second step. For information on how to configure inferencing, see Help: TopBraid Composer > How to? > Run and Configure Inference Engines 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 20, 2008 5:18 PM To: TopBraid Composer Users Subject: [tbc-users] Re: Pizza Ontology, Inference Loop Hello, Sorry, I meant that before I run Pellet, a class is inferred as a subclass of owl:Thing. After reasoning with Pellet, the class does not appear in the class view anymore, since Topbraid "forgets" the inference. It does not appear as subclass of any of the other classes, either. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
