[ 
https://issues.apache.org/jira/browse/JENA-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189368#comment-13189368
 ] 

Paolo Castagna commented on JENA-195:
-------------------------------------

> So I'm unclear what the design policy is in this area and think it might get 
> confusing. 

Ack.

I see three options:
1/ no checks
2/ we check and throws an exception if the "query" parameter is present
3/ we check and throws an exception if any of the parameters used by the SPARQL 
protocol is present

Probably, 2/ is the best thing to do. 

If that seems reasonable, I'll do that and make sure the two ways behave the 
same.
Indeed, now that I tried both ways, perhaps the solution via context is not as 
easy to use and it should be removed.
                
> Allow users to specify query parameters when they use SERVICE 
> <...?name=value> in their SPARQL queries
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JENA-195
>                 URL: https://issues.apache.org/jira/browse/JENA-195
>             Project: Jena
>          Issue Type: Improvement
>          Components: ARQ
>            Reporter: Paolo Castagna
>            Assignee: Paolo Castagna
>            Priority: Minor
>         Attachments: JENA-195.patch, 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.
> Service.java 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.
> OpService.java probably needs to change (to keep the parameters separate from 
> the SERVICE endpoint URL).
> See also this thread on jena-users: 
> http://markmail.org/thread/wc5hvr3b3uzy2mrk

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to