Now the short answer. I think I like the linked rules. If nothing else, I just find it a littler more direct and aesthetically pleasing.
Jeff Work: 314-232-1997 Cell: 636-448-5990 > -----Original Message----- > From: Holger Knublauch [mailto:[email protected]] > Sent: Tuesday, August 11, 2009 5:49 PM > To: [email protected] > Subject: [tbc-users] Re: ANN: TopBraid SPIN API 1.0.2 > > > Hi Jeff, > > this is actually an interesting idea. A generic solution > would be to assign some numeric value to the sub-properties, > e.g. triples > > my:importRule spin:weight 10 . > my:exportRule spin:weight 20 . > > where rules using properties with smaller weight would be > executed before the others. Using a sub-property of spin:rule > would provide a natural grouping of rules into categories. > Alternative to a numeric value would be an explicit > spin:executeBefore to relate two rule properties. > > Would this be sufficient for your use case, and which > solution sounds cleaner? > > Thanks, > Holger > > > On Aug 11, 2009, at 1:10 PM, Schmitz, Jeffrey A wrote: > > > > > 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 -~----------~----~----~----~------~----~------~--~---
