Arthur; BINDINGS is a SPARQL 1.1 feature, one of the few that we do not support because the syntax is still evolving - albeit more slowly now that SPARQL 1.1 is in final call. In a TBS release shortly after SPARQL 1.1 is announced as a recommendation we will announce SPARQL 1.1 compliance.
-- Scott On Oct 5, 11:19 am, Arthur Keen <[email protected]> wrote: > David Beckett's "Learn about SPARQL 1.1" presentation > (http://www.dajobe.org/talks/201105-sparql-11/) has a description of the > BINDINGS clause in the section on Federation Extensions in slides 12 and 13. > I was not aware of BINDINGS clause, so I decided to experiment with it in > the Composer's SPARQL editor: > > The SPARQL editor accepts the query syntax of David Beckett's examples, but > it does not return results when executed. Is there an issue with the > queries, or does the Composer SPARQL editor not process BINDINGS? > > Arthur > > From presentation: > > This can optionally use BINDINGS to pre-bind some variables in a SELECT: > SELECT ?a > { > ?a ?b ?c .} BINDINGS ?a { > ( :value1 ) > } > > Returns 1 row with ?a bound to :value > > This also makes SPARQL into a new syntax to build result sets with no data > source or query: > > SELECT * { } BINDINGS ?var1 ?var2 { > ( "var1-value1" "var2-value1" ) > ( "var1-value2" "var2-value2" ) > > } -- 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
