incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paolo Castagna (Updated) (JIRA)" <>
Subject [jira] [Updated] (JENA-195) Allow users to specify query parameters when they use SERVICE <...?name=value> in their SPARQL queries
Date Mon, 16 Jan 2012 20:35:39 GMT


Paolo Castagna updated JENA-195:

    Attachment: JENA-195.patch

Thank you Andy.

This patch improves the javadoc and provides an additional example (i.e.
which needs a Kasabi API key to be run. Maybe not a good idea to include this as an example,
but this is the real use case where this issue come from.
A QueryExecException is thrown if someone overrides a SPARQL protocol query parameter via
I'll further improve the documentation, as the code settles. 

Things I am not sure about are: encoding policy and Explain.explain.

QueryEngineHTTP.addParam doesn't encode values, I followed the same approach for consistency.
Is this the right thing to do?
I need to look more at Explain.explain and find out what's the best way to report logging

> Maybe it's time to have a page on the website for all-things-remote, including this feature

If/when a page for all-things-remote is added to the website, I'll add a section there when
this issue is closed. I am not sure if I know all of the all-things-remote.
> Allow users to specify query parameters when they use SERVICE <...?name=value>
in their SPARQL queries
> ------------------------------------------------------------------------------------------------------
>                 Key: JENA-195
>                 URL:
>             Project: Jena
>          Issue Type: Improvement
>          Components: ARQ
>            Reporter: Paolo Castagna
>            Assignee: Paolo Castagna
>            Priority: Minor
>         Attachments: JENA-195.patch, JENA-195.patch
>   Original Estimate: 8h
>  Remaining Estimate: 8h
> SPARQL endpoints might require or allow additional query parameters, if we want to use
those endpoints with SERVICE <...> in SPARQL queries we must support query parameters
and allow users to use SERVICE <...?name=value> in their SPARQL queries.
> can look in the Context for additional parameters. 
> Parameters need to be kept separate and grouped on a per SERVICE endpoint basis (in order
to avoid exposing parameter values to wrong places).
> A Map<String, Map<String,List<String>>> can be uses to map SERVICE
endpoint URLs to parameter-->values.
> probably needs to change (to keep the parameters separate from the SERVICE
endpoint URL).
> See also this thread on jena-users:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message