Improving SPARQL transform

The proposal is merge the functionality of SPARQLtransform and projections (pyql files). We would prefer for queries to always be expressed as SPARQL, in order not to loose any of the SPARQL expressiveness, but to keep the transform result representation capability – results from queries expressed as json. The transform syntax could be included using the transform keyword.

The .rq file would look like this:

#+ summary: Brief description of this query
#+ endpoint_in_url: False
#+ endpoint: "http://endpoint/sparql/"
#+ transform: {
#+     "id": "?id",
#+     "class": "$rdf:type$required$var:?class",
#+     "label": "$rdfs:label$required",
#+     "o": "?o"
#+   }

prefix dcterms: <http://purl.org/dc/terms/>

SELECT ?p ?o WHERE
{
  ?_s ?p ?o
}

@pasqLisena – I discussed this with @albertmeronyo and we agreed this might be the best way forward. Do you have any comments / suggestions?

[c-martinez]

Hi @pasqLisena. Nice! So this means I should be able to write something like this:

{
  "key": "?p$anchor",
  "value": "?o"
}

and get the desired result. Correct?

[pasqLisena]

Hi @c-martinez, I just released a version of ST in which you can replace that hard-coded id with any other property with a $anchor modifier. See documentation