Hi Holger, thanks for the explanation about why you dediced to design the filter this way. I now understand how you came to this decision.
I have created a new post for the inconsistency detection problem. Best wishes, Lieke On Friday, 22 August 2014 03:27:06 UTC+2, Holger Knublauch wrote: > > On 8/21/2014 16:58, Lieke Verhelst wrote: > > I also expressed some frustration about the working of the complete mode > switch. My point here is that it is often necessary to enable complete mode > to be able to see the working of inference according to the spec. While in > the documentation this is characterized as "redundant". *It seems that > the filtering of one triple* (in this case X rdfs:subClassOf X ) *causes > the filtering of other - not redundant, but desired - statements*, even > to the point of not detecting inconsistency...(I referenced above to > another thread) > > > Can you give me an example Turtle file of where inconsistencies were not > detected? This would be a bug indeed. > > I don't need to keep you any more busy. As far as I am concerned the > thread can be closed with a few comments from you regarding my following > assumption: when I run the SPIN OWL2-RL reasoner on the ontology listed in > the initial thread entry above with complete mode OFF, I see no results for > the scm-sco rule because statements are filtered out that cause the > hierarchy tree to be messed up, in particular X rdfs:subClassOf X . Because > of this, other statements like :C rdfs:subClassOf :A are also not displayed. > > > Yes this is intentional, because a A/B/C tree has all information needed > for a human user to understand what's going on. I just looked at the source > code and for each newly touched class, it will remove all transitive > superclasses of all direct superclasses, e.g. if C if inferred to be > subclass of A then this triple will be deleted if C is also subclass of B > (in your example). This happens after all other inferences have been > completed, i.e. the whole TopSPIN looping and stuff is done. There is also > code that makes sure that each named class at least has owl:Thing as its > parent, so that people can see it in the class tree. > > HTH > Holger > > -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. 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-users?hl=en --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
