We certainly have added our own subclasses to spin:rule to control rule execution, but I think they may be too specific to our application to add them to the general spin model.
Perhaps some kind of directional flow sub-properties (e.g. importRule, exportRule) that could be used directly or could themselves be further be subclassed would be helpful. But perhaps even that wouldn't be general enough. It's not too hard to add and mechanize such concepts locally, but perhaps you don't want too much fragmentation so the standard SPIN API can do more of the work? > -----Original Message----- > From: Holger Knublauch [mailto:[email protected]] > Sent: Tuesday, August 11, 2009 2:53 PM > To: [email protected] > Subject: [tbc-users] ANN: TopBraid SPIN API 1.0.2 > > > There is a new version of the SPIN API available from > > http://www.topquadrant.com/topbraid/spin/api/ > > New features include support for Jena 2.6 and for the ARQ > keywords NOT EXISTS and SERVICE. Note that the current > release of TBC (3.1.1) does not yet support these two > keywords in its SPIN RDF syntax. > > BTW I would appreciate input on how to improve SPIN. For > example if you have requirements for additional properties to > control the execution of rules. > > Cheers, > Holger > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
