On 03/01/17 14:41, james anderson wrote:
good evening;
On 2017-01-03, at 15:34, Martynas Jusevičius wrote:
[…]
As for the original Sesame protocol, it's hard to find the spec these
days (maybe it is deprecated?), but here's a short note about variable
bindings with
good evening;
> On 2017-01-03, at 15:34, Martynas Jusevičius wrote:
>
> […]
>
> As for the original Sesame protocol, it's hard to find the spec these
> days (maybe it is deprecated?), but here's a short note about variable
> bindings with N-Triples-encoded values:
>
On 03/01/17 14:34, Martynas Jusevičius wrote:
On Sun, Jan 1, 2017 at 6:59 PM, Andy Seaborne wrote:
On 01/01/17 12:53, Martynas Jusevičius wrote:
I am wondering if there is a way to "intercept"
Any thing can be intercepted with a custom OpExecutor.
Any examples? What
good afternoon;
> On 2017-01-01, at 18:59, Andy Seaborne wrote:
>
> […]
>
>>
>> As you might know, some triplestores (RDF4J, Dydra) provide an
>> extension of the SPARQL protocol that allows sending query bindings
>> separately from the query string. (Too bad it's not
Just a bit more on how SERVICE-specific HTTP action is managed:
https://jena.apache.org/documentation/query/service.html#configuration-from-jena-version-311
The code is here:
On 01/01/17 12:53, Martynas Jusevičius wrote:
Hey,
happy 2017 :)
I am wondering if there is a way to "intercept"
Any thing can be intercepted with a custom OpExecutor.
the HTTP request that
is being generated by the SERVICE clause?
See Service.configureQuery for the use of
Hey,
happy 2017 :)
I am wondering if there is a way to "intercept" the HTTP request that
is being generated by the SERVICE clause?
As you might know, some triplestores (RDF4J, Dydra) provide an
extension of the SPARQL protocol that allows sending query bindings
separately from the query string.