Aziza; In particular, you can define an AllegroGraph back-end for your data and save your SPIN queries in it. E.g. when specifying a query using any property or subproperty of spin:query, such as spin:rule or spin:constraint, the query is saved in RDF in the data store used to define the data. Therefore, if you create an AllegroGraph triple store for your data, then open .allegro connector file and add your SPIN queries to the classes and save, the queries are saved in the AllegroGraph data store file pointed to by the .allegro connector. No extra files are needed to represent the queries.
When executing SPIN inferences, functions, templates, etc., TopBraid will pass the SPARQL queries to AllegroGraph via its API and collect results for processing in Composer/Live. -- Scott On Mar 14, 10:30 pm, Holger Knublauch <[email protected]> wrote: > Not natively, but every triple store with a Jena interface (incl AG) > does support the full expressivity of SPIN. Performance depends on the > use case and set up, and some databases will have better SPIN > performance than others. > > Holger > > On 15/03/2011 1:07 PM, aziza wrote: > > > Hey,all! > > Does AllegroGraph support SPIN? > > Thanks,Aziza -- 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
