[
https://issues.apache.org/jira/browse/JENA-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988911#comment-15988911
]
Andy Seaborne commented on JENA-1331:
-------------------------------------
Mechanism exist for a purpose. People will ask about their usage of it :
"why does this not work with Fuseki?" but also "why does this not work with
GraphDB?" and we are seen to be picking favourites.
We get a little of this with DBPedia already (more so on StackOverflow) though
as a public resource that's contributing to the vision of semantic web.
A mock endpoint encodes the expected responses and effects yet those are being
defined by a 3rd party who may change the details yet users end up on
users@jena because it is a "jena mechanism". I really think the 3rd party needs
to be involved and not have us second-guess. We can not do everything.
PR#247 supports query string on the service name (and I tested it); the new
feature request is changing that during a connection's lifetime for individual
operation. {{RDFConnection}} is general (in as far it can be) - only the setup
is implementation-driven. Local datasets don't have HTTP query parameters.
It happens to mean the name of the service is changing - the query string is
part of the URL and (webarch) the name of a resource is the URL excluding the
fragment. By the time a specific operation is added for, say, query, it amounts
to calling {{QueryExecutionFactory.sparqlService}} directly. I think this is
better handled by a specialised subclass of
{{RDFConnection}}/{{RDFConnectionRemote}} that makes it clear is it specific to
one system.
> RDFConnectionRemote does not handle additional query string items in GSP
> operations.
> ------------------------------------------------------------------------------------
>
> Key: JENA-1331
> URL: https://issues.apache.org/jira/browse/JENA-1331
> Project: Apache Jena
> Issue Type: Bug
> Affects Versions: Jena 3.2.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
>
> Some systems have optional query string parameters. Calculating the correct
> operation URL needs to take these into account. The Graph Store Protocol gets
> broken operations get broken.
> Report:
> https://lists.apache.org/thread.html/bd56999dc75bb223b0707e06f958c0579e0a2e04f59a72183168ae95@%3Cusers.jena.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
