Hi Rita, inference engines are typically limited to *adding* new triples from existing triples - they do not remove existing data, knowledge or facts. The inferences are "soft" in a sense, while the asserted triples (that you have entered) will always remain there as well. In terms of SPARQL, SPIN rules are CONSTRUCTing new triples. For deleting other triples, SPIN would need to support UPDATE (INSERT,DELETE) queries, but this is not the case.
So the behavior you are describing is perfectly in line with the plan. Regards, Holger On Jun 2, 2010, at 8:55 PM, Rita Marnau wrote: > Hi Scott, > > thank you for answering. It works! :) > I noticed that there is a difference between values entered by me and > inferenced values. > The spinsquare example again: Changing the widht and hight, works perfektly. > The area is computed immediately. > But look at the following use case: > only height is set. I enter an area value. I enter a width value. Now I have > two areas. My own, and the inferenced value. > > So for values computed by SPIN Constructs it is not provided to enter own > values? I would have expected that my own value disappears and will be > replaced by the inferenced one. > > Thanks again. > > Rita > > Am 01.06.2010 23:50, schrieb Scott Henninger: >> Hello Rita, and welcome! Incremental inferencing needs to be turned >> on in Composer to see the results of the changes immediately. Go to >> Inference> Configure Inferencing..., choose the TopSPIN module, and >> select Edit parameters (or double-click on the TopSPIN module), and >> make sure "Incremental Inferencing at edit time" is checked. Once >> turned on, the inferences of changes defined in SPIN will appear >> automatically. >> >> -- Scott >> >> On Jun 1, 8:29 am, Rita Marnau<[email protected]> wrote: >> >>> Hi everyone, >>> >>> I've worked with Protege so far and now I am testing the TopBraid >>> Composer the first time. >>> I am very expressed about SPIN but unfortunalety it doesn't work as >>> explained in the Webinar. >>> I opened the /spinsquare/ example (example folder). >>> >>> SPIN Construct testing (Area of a rectangle is computed via SPIN Construct): >>> I opened the /TestRectangle/ Instance of Rectangle. I changed height or >>> width. Nothing happened. (I pressed "return" or the "ok" button next to >>> the property row several times, but nothing happened) >>> I clicked on the "Run inference" button -> yeah, the area has been >>> computed. >>> I changed the height. Nothing happened. I clicked the "run inference" >>> button again: ups, a second area appears. >>> My Rectangle has now 2 areas, the first has not been deleted. >>> >>> Am I missing s.th? >>> >>> Rita >>> >> > > -- > 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 -- 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
