[
https://issues.apache.org/jira/browse/JENA-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949623#comment-13949623
]
Andy Seaborne commented on JENA-663:
------------------------------------
What system are you loading the prefixes from? Its the RDF/XML case that is
tricky. Prefixes vs performance end-to-end. I hope over time Turtle becomes
the normal choice. N-triples accept as application/n-triples (RDF 1.1) higher
than RDF/XML but text/plain is lower than RDF/XML. The idea is that RDF 1.1
system will use Turtle rather than RDF/XML. Older system will not set N-Triples
as application/n-triples.
> DatasetGraphAccessorHTTP should prefer turtle or rdf+xml instead of n-triples
> -----------------------------------------------------------------------------
>
> Key: JENA-663
> URL: https://issues.apache.org/jira/browse/JENA-663
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 2.11.1
> Reporter: Pascal-Nicolas Becker
> Priority: Minor
> Labels: easyfix
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> If you load a graph using the SPARQL 1.1 Graph Store HTTP Protocol with the
> class DatasetGraphAccessorHTTP used prefixes won't be loaded.
> DatasetGraphAccessorHTTP.httpGet() and
> DatasetGraphAccessorHTTP.httpGet(String) currently send
> "application/n-triples,text/turtle;q=0.9,application/rdf+xml;q=0.8,application/xml;q=0.7"
> as accept header. N-Triples doesn't support prefixes. If turtle or rdf/xml
> were prefered instead of n-triples prefixes would be loaded.
> DatasetGraphAccessorHTTP contains a private static method GetAcceptHeader
> (https://github.com/apache/jena/commit/b396e7f7c90d81d953a556cb351d12f6e7751061#diff-37822a7826d74aa4063756e063be72f1L107).
> This line should be changed. There is a comment in the source code pointing
> to org.apache.jena.riot.WebContent.defaultGraphAcceptHeader which is already
> set to prefer turtle.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
