On Aug 30, 2011, at 6:12 PM, Gerrit wrote: > Holger, > > Thanks, I was wondering how you achieve such behaviour in TBC. For my > current scenario I will then just use removeAll() on my inferred Model > before running SPINInferences.run(). Keeping previous inferences would > have been nice, but are not essential to my scenario. Are there plans > to include BufferingGraph in the SPIN API in future?
We have no current plans to include incremental inferencing into the open source edition of the API. I haven't seen enough use cases to justify that, given that the incremental inferencing itself is limited to certain use cases. Meanwhile resetting inferences and re-applying them will work. (Without a lot of extra thought I am wondering if you could simply add an extra rule so that the WHERE clause of the inferences becomes a DELETE, and the CONSTRUCT becomes the WHERE. Then run that rule with ?this bound to the to-be-deleted resources. This pattern may work for many rules that only include basic graph patterns, to undo previous inferences. It would be possible to automate the creation of such DELETE rules from the SPIN syntax.) 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
