On Jun 16, 2011, at 9:33 AM, Holger Knublauch wrote: > > On Jun 15, 2011, at 6:29 PM, Gerrit wrote: >> Now I do have a case of not all constraint violations showing up. I >> have defined a property chain as an irreflexive property, and when >> this is violated it shows up correctly in TBC. I don't see this >> violation when using SPIN API. > > I double-checked that the SPIN API also honors spin:imports for constraint > checking (not for rules though). So I believe we need more information on > your set up to help.
BTW, another difference between your model in the SPIN API and the model in TBC might be that TBC models always include the system triples, e.g. the definition of ranges and domains of system properties such as rdf:type. This might affect results in some cases. In order to include the system triples, there is a helper class SystemTriples in the SPIN API. If this rings a bell, try to create a MultiUnion with this as a sub graph and run constraint checks over that. Holger -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion 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
