Aloson; SPIN rules by itself will not assert triples unless you use INSERT in the query. Once the INSERT has been executed, the triple is asserted permanently. That is the desired effect for SPARQL INSERT.
Using CONSTRUCT is a far more common use case for SPIN. A SPIN rule using CONSTRUCT will add triples to the inferred graph only. No triples are asserted and you cannot save the inferences unless you assert them first. Re-setting inferences should remove all inferred triples. If you have an example otherwise, we'd like to hear more details so we can reproduce. -- Scott On Sep 8, 4:44 pm, Alison Callahan <[email protected]> wrote: > Hello all, > > I am using TopBraid Composer 3.5.1, Maestro edition in Ubuntu 11.04. > > I have noticed that even after I reset inferences, triples that were created > by a spin:rule that I had previously deleted are still asserted after I > re-run TopSPIN. Is there a setting that I need to change to prevent triples > created by spin:rules from being permanently saved even after I reset > inferences? > > Thanks, > > Alison -- 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
