SPARQL 1.1 Support with BigData

Help
2012-04-06
2014-02-19
  • Bryan Thompson

    Bryan Thompson - 2012-04-06

    Yes, BINDINGS is supported.  You have a syntax error.  Look at the examples in the 1.1 spec .

    <pre>
    PREFIX dc:   <http://purl.org/dc/elements/1.1/>
    PREFIX :     <http://example.org/book/>
    PREFIX ns:   <http://example.org/ns#>

    SELECT ?book ?title ?price
    {
       ?book dc:title ?title ;
             ns:price ?price .
    }
    BINDINGS ?book {
    (:book1)
    }
    </pre>

    The list of variables for the bindings appears before the curly braces.

    For the second query, you again have a syntax error.  You need to use BIND(COUNT(?x) as ?count) or some similar syntax.  SPARQL does not have automatic naming of variables in SELECT expressions.  Maybe you are used to a store which allows non-standard expressions? Here is a valid query:from the spec .
    <pre>
    PREFIX  dc:  <http://purl.org/dc/elements/1.1/>
    PREFIX  ns:  <http://example.org/ns#>
    SELECT  ?title (?p*(1-?discount) AS ?price)
    { ?x ns:price ?p .
      ?x dc:title ?title .
      ?x ns:discount ?discount
    }
    </pre>

    Thanks,
    Bryan

    http://www.w3.org/TR/sparql11-query/#bindings
    http://www.w3.org/TR/sparql11-query/#selectExpressions

     
  • Bryan Thompson

    Bryan Thompson - 2012-04-06

    Aggregation was supported in bigdata 1.1.  Federated Query, BINDINGS, UPDATE, and Service Description are supported in bigdata 1.2.  We still need to implement property paths,but that is the only feature not present in the 1.2 release.  There are some last call working draft issues which have not yet been resolved, but those are pretty minor things - you can see the list of these last minute changes if you look at the current Last Call Working Draft revision of the SPARQL 1.1 spec.

    Thanks,
    Bryan

     
  • zschweinfurth

    zschweinfurth - 2012-04-08

    Thanks. I appreciate the help.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks