[
https://issues.apache.org/jira/browse/JENA-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939632#comment-13939632
]
Andy Seaborne commented on JENA-656:
------------------------------------
[~white_gecko], thanks for the patch.
I hope you'll ask the implementers of the engine behind
http://rdf.myexperiment.org/sparql/ to implement the more exact MIME types.
I agree with [~rvesse] about encouraging sloppy practice. {{application/json}}
in particular can be sent, regardless of what was asked for, for errors in web
API requests.
The good news is that streaming results requires the format header to be seen
so any errors due to stray data coming back is likely to be caught before the
client code starts to loop if the results are being streamed.
Thinking about the dual situation for Fuseki: Does anyone know of any client
software that reacts to only {{application/json}} or {{application/xml}}, not
{{application/sparql-results+???}}?
> Doesn't send all accepted mime types in header
> ----------------------------------------------
>
> Key: JENA-656
> URL: https://issues.apache.org/jira/browse/JENA-656
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 2.11.1
> Reporter: Natanael Arndt
> Assignee: Andy Seaborne
> Attachments: 0001-Fix-JENA-656.-Improve-mime-type-handling.patch
>
>
> The Jena HTTP query engine doesn't send all the mime types it can process in
> the accept header. It would be better if it could send all of them, so
> services can send a better response.
> Currently the HTTP-Accept-Header claims that jena can only accept
> {{application/sparql-results+xml}} resp. {{application/rdf+xml}} as query
> result. In fact it can process much more types.
> Furthermore some services [1] will return a more general content-type in the
> header when answering a request (e.g. {{application/json}} instead of
> {{application/sparql-results+xml}} or {{application/xml}} instead of
> {{application/rdf+xml}}). It would be good to also try to parse such results
> and to see if the content can be interpreted as SPARQL result.
> [1] http://rdf.myexperiment.org/sparql/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
