for consideration: * Inference > Configure Inferencing... It would be helpful here if the TopSPIN engine offered the same sml:predicate option as does the sml:ApplyTopSPIN SM module. Two or more TopSPIN blocks could then be sequenced together to evaluate different rules sames.
* Instances > Select column properties... The "group by namespace" feature would be helpful here. * Make SPIN WHERE clauses reusable. An example use case is for transformer scripts that process the same input and have multiple output formats, the triple parsing that occurs in the WHERE clause is often constant (some exception when URIs have to be constructed). Perhaps SPIN templates could allow only the sp:where to be defined and then employed by other templates that add the construct part, etc. A mechanism to allow additions to a re-used WHERE clause would also be helpful here. thanks, -Daniel -- 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
