Jim; There are two separate pieces here. The problem I believe you are experiencing is that, independent of the replace property or anything else, the triples are not passed through the sm:body property. I.e. the iteration body is where your triples are being "erased" and none of the iterations have access to those triples.
ApplyConstruct takes a set of triples as input and returns a set of triples (most SM modules do this). If relplace=true, then only those triples constructed in the module are passed on via sm:next. The other triples are "erased" for the remainder of the script. So, yes, replace=true does erase all of the triples from the input to ApplyConstruct. <...a subsequent iteration pass will still have the data from the initial load?> No, unlike sm:next, sm:body does not pass triples to the module. -- Scott On May 11, 2:39 pm, James A Miller <james_a_mil...@raytheon.com> wrote: > So, the replace=true does not erase all of the triples already known? That > is, if I load data outside of (prior to) the iteration, then I do > something with "replace=true" inside the loop, a subsequent iteration pass > will still have the data from the initial load? > > Jim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to topbraid-composer-users@googlegroups.com To unsubscribe from this group, send email to topbraid-composer-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
