Thanks Holger, my queries did not use any functions like BIND this time... I triple checked :)
There is nothing obvious about why it does not work in the latest version of TBC. The syntax checks out. In fact, I just tried it in the 4/19 version and it worked. But when I tried it in the latest it did not work. It would be difficult for you to try it out without sending you data and then you would have to be able to see how the information is set up in the XML file that I converted to RDF. If you feel like giving it a shot and don't mind my sending something off list, let me know. Best, Leonard On Thu, Oct 25, 2012 at 6:11 PM, Holger Knublauch <[email protected]>wrote: > On 10/26/2012 8:02, Leonard Jacuzzo wrote: > >> Hi list, >> As a follow up to my previous question about SPIN not working the way it >> used to, I am wondering where I can find a brief list of 'dos and don'ts' >> regarding the new syntax requirements for the SPARQL engine in TBC. >> > > I am not aware of other restrictions apart from the BIND ordering issue. > In the old days the Jena parser allowed BINDs to show up in any order > because the semantics were such that if the variable on the right side of > the BIND is already bound, then the BIND (aka LET) becomes a comparison. > This however is not what the official SPARQL 1.1 spec ended up with. > > One important change recently has been that FILTERs are more aggressively > pushed to the end of the surrounding block. This means if you had > > ?a my:property ?b . > FILTER (?b > 42) . > ?other my:other ?b . > > then this gets executed as > > ?a my:property ?b . > ?other my:other ?b . > FILTER (?b > 42) . > > In order to take more control of the ordering, you could introduce extra > blocks, e.g. > > { > ?a my:property ?b . > FILTER (?b > 42) . > } > ?other my:other ?b . > > which will be executed from the inside out and do the FILTERing before the > second BGP. This can drastically change performance and sometimes even > correctness of your queries. > > If you run into other queries that no longer work for you, please feel > free to post them to the list. > > HTH > Holger > > -- > -- You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include Enterprise > Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, > TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to > topbraid-users@googlegroups.**com <[email protected]> > To unsubscribe from this group, send email to > topbraid-users+unsubscribe@**googlegroups.com<topbraid-users%[email protected]> > For more options, visit this group at > http://groups.google.com/**group/topbraid-users?hl=en<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 Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages 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
