On Apr 8, 2011, at 6:32 PM, Gerrit wrote: > In reality my SPIN rule is also > dependent on two property chain axioms that need to be inferred first > (not shown in my example below). This means that I had to change the > spin:rulePropertyMaxIterationCount to 2. Now I'm just wondering if it > is guaranteed that the property chain axioms will fire on the first > pass.
You can specify the order of rules in SPIN as well. The cleanest way is to define different sub-properties of spin:rule, and then link them together using spin:nextRuleProperty. For example, define my:prepRule and my:postRule and use them to group your rules that depend on each other. Otherwise, SPIN will use the "alphabetical" ordering of rules, and you can specify this by putting comments such as # Rule1 above the CONSTRUCT clauses. But the latter option is rather fragile, even if it's tempting for quick hacks. Holger -- 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
