Arthur; I'm still not entirely clear about the question, but I think the overall behavior you describe is a consequence of the underlying RDF graph structure. When you execute the series of constructors, you seem to be creating a set of graphs that all intersect at your :Project class. When you delete :Project, Composer will delete all depending triples as well. These include the instances. This is basically the "cascading" effect you describe. It is not a SPIN feature, but how delete works in Composer/RDF.
<<I noticed a TBC file got created for my model, but did not check the contents>> The .tbc file holds information about preference settings, such as for layout, instance column setup, and inference engine configuration. The file was probably created to hold your TopSPIN configuration. No other data information is contained in this model - which you can open and view as an RDF file (n3). <<What happens if subsequent changes are made to the structure that was created by the constructor?>> As stated above, the behavior you describe is really a core feature an ontology editor. So if structures are created and added to the triples added by the constructor rules, they will be treated like any other triple when performing a delete, etc. operation. <<How do you use it in Ensemble/Live? >> This is really a core Live feature. Ensemble and Composer both use this core, so the effects will be the same. There could be more to your question than this. If so, a detailed example may be necessary to fully understand what you are experiencing. -- Scott On Jun 11, 7:59 am, Arthur Keen <[email protected]> wrote: > Yes, the structure consists of blank nodes. > > The structure is > > Project--(tasks)-->Task----+ > ^ |(next) > +------+ > > The constructor on Project and builds a default task network of blank nodes > and the tasks have constructors that set default task status. When I delete > the project instance the tasks appear to delete as well. Why does this > happen? > > Arthur > > On Jun 11, 2010, at 1:39 AM, Holger Knublauch wrote: > > > Hi Arthur, > > > I am not sure if I understand your question. > > > On Jun 11, 2010, at 1:21 PM, Arthur Keen wrote: > > >> When I first tried spin:constructors last year, I noticed (in TBCME) that > >> graph created by a cascade of spin constructors deleted when you deleted > >> the root (initiating) object in a spin constructor cascade. > > > Could you clarify this a bit? Are your constructors creating a blank node > > structure that it then dangling from the root object? These blank node > > trees would indeed be deleted, but this has nothing to do with > > constructors. I am not aware of other magic here. > > > 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 -- 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
