Hi Christoph, TopBraid never "forgets" any assertions. The triple is probably showing up in blue because TopBraid automatically makes every class that does not have any other named superclass a subclass of owl:Thing. So my guess is that the triple is not asserted in your case but inferred (automatically).
In addition to seeing inferred triples in blue, you can mouse-over the icon to the left of a triple on a form to see where it is coming from. Holger On Oct 18, 2008, at 4:41 AM, Christoph wrote: > > Thanks, Scott. How can I assert owl:Thing? It is already asserted, but > when I run the reasoner, it disappeared. So I have to reassert it > again, how can I do this? Is this an error of Topbraid, that it > "forgets" the assertions? > > Christoph > > On Oct 16, 5:47 pm, Scott Henninger <[EMAIL PROTECTED]> > wrote: >> Christoph; The solution is to assert owl:Thing for the affected >> classes in your ontology. We will look into alternatives, but this >> is >> the necessary solution for the time being. >> -- Scott >> >> On Oct 16, 4:36 am, Christoph <[EMAIL PROTECTED]> wrote: >> >> >> >>> Thanks, Scott. Is there a reason for this that not all classes are >>> shown anymore in the class tree view after reasoning? Is there a >>> solution? Because I cannot search for all classes to have a look if >>> the subclassOf owl:Thing is being lost.- Hide quoted text - >> >> - Show quoted text - > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
