Andy Seaborne wrote: > On 13/01/12 17:19, Paolo Castagna wrote: >> Paolo Castagna wrote: >>> Or, the SPARQL specs explicitly forbid that... probably here, isn't it? >>> http://www.w3.org/TR/sparql11-query/#rIRI_REF >>> >>> Luckily, QueryEngineHTTP has an addParam(...) method. However, I did >>> not find >>> a way do go around this within a SPARQL query using SERVICE. >> >> This isn't as friendly as using SERVICE directly within the SPARQL >> queries. >> >> Would it be possible to change Service.java [1] and allow developers >> to set >> custom/additional query string parameters on a per service URI basis? >> Or, alternatively, HTTP request parameters? >> >> Paolo >> >> [1] >> http://svn.apache.org/repos/asf/incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/Service.java >> > > It's a ordering/%-encoding issue. Which version is this? trunk?
Hi Andy, I think it was the arq.query command from ARQ included in the Fuseki SNAPSHOT. But, I had a look at the QueryEngineHTTP and QueryHTTP code in ARQ trunk and the same exception will trigger if someone attempts to use SERVICE and a URI with some parameters already set (which I think it is forbidden by the spec). Isn't it? Paolo
