|
Henrik; The scenario you describe is actually a common pattern for
SPARQLMotion. The overall objective is to create "streams" of
triples and combine them as needed. Therefore: Two or more sm:next properties coming into a module means that the union of the triple streams will be available to the module ...and Two or more triple properties going out of a module means that the triples from that module are being used by two or more modules. -- Scott On 12/4/2014, 9:04 AM, Henrik Alstad
wrote:
-- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages 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 Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. |
- [topbraid-users] Sparqlmotion script with multiple sm:next Henrik Alstad
- Re: [topbraid-users] Sparqlmotion script with multipl... Scott Henninger
