Joe;  There are a number of ways to assert inferred triples.  In
Composer, you can run inferences on your SPIN model.  A Inferences
view (tab) will appear with all inferred triples.  Select all (or
whatever subset you want) then click on the up arrow in the top-right
of the view to assert into the model.

In SPARQLMotion there isn't a distinction between asserted an inferred
triples.  Each module takes a set of triples as input and returns a
set of triples.  For example, in sml:ApplyTopSPIN, the input triples
would be your SPIN model.  If you leave the sml:replace property at
its defulat (false), the triples returned will be all of the input
triples plus the inferred triples.  If you set replace=true, then the
returned triples are only those created in the module (the "inferred"
triples).  The output of the model can then be saved into a file with
RxportToRDFFile, etc.

-- Scott

On Jun 24, 11:38 am, Joe Eberle <[email protected]> wrote:
> Hi All,
>
> We have run a large number of SPIN:Constructs to assert new triples
> within our model. We are starting with approximatelty 1.6 million
> triples and are adding approximately 3x1.6 million triples inference
> with the inference engine. We are doing all of this using the TopSPIN
> inference engine.
>
> We now need to assert these triples to the model before we persist
> them. Is there a simple mechanism to perform this operation? We are
> examining using SPARQLMOTION to assert the inferences but do not know
> how to idetify the entire set of infered triples currently in memory.
>
> We are open to non sparql motion solutions as well.
>
> Best Regards,
> Joe
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
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-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to