Hi Gerrit, no, the smf functions are currently native to TopBraid. We have factored out most of them into another stand-alone library for 3.5, and we yet need to decide on how this will be available to customers (i.e. it may be commercial for some users at least). That extended Java library also contains functions such as smf:parseDate, and all those functions have been moved into a separate namespace called http://spinrdf.org/spif# to clarify that they will work independently of TopBraid (Composer or Live).
In the case of buildURI, you have the option of using fn:concat in your own function, but even then you may need to wait for 3.5 which has better SPARQL 1.1 support - I am not sure whether the function IRI that turns strings into URI resources was already in 3.4. Also, to emulate buildURI you will need to do string functions that escape special characters. As usual you seem to catch us at the bleeding edge, just in time for the next release :) Regards, Holger On Apr 8, 2011, at 7:47 PM, Gerrit wrote: > It seems that smf:buildURI works inside TBC, but not through the SPIN > API? I'm getting the following warning: > > 11:20:06 WARN (ALog.java:48) - URI <http://topbraid.org/ > sparqlmotionfunctions#buildURI> has no registered function factory > > Only when I replace it with a fixed URI does it infer the expected > triples. > > Regards, > Gerrit > > On Apr 8, 10:38 am, Holger Knublauch <[email protected]> wrote: >> 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 -- 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
