> > Basically what I'm trying to do is to remove triples that were > > previously inferred (based on a CONSTRUCT SPIN rule), when the triple > > which caused the inferment does not exist anymore. This should be > > quite a common use case, no? > > Why are those triples created in the first place? Why don't you just prevent > their creation by modifying the SPIN rules - make the WHERE clause of that > rule more specific, it's open source after all.
The triples are inferred (using SPIN rules) when new triples are inserted by devices connected to a triple store. As an example, consider a device inserting a sc:connectedTo relationship when it is connected to another device. When the asserted triples are later removed by these devices (e.g. a device removing its sc:connectedTo relationship when the other device disconnects), the triples that were inferred based on these triples should be removed as well. Regards, Gerrit -- 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
