[
https://issues.apache.org/jira/browse/JENA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367510#comment-16367510
]
Andy Seaborne commented on JENA-1490:
-------------------------------------
The main setting is {{Accept:}} and {{Content-Type:}} and having them available
for {{RDFConnection}} helps anyway - not all other triple stores support or
prefer the same RDF syntaxes.
RDF Thrift is a normal, non-standard, content type.
Additional operations outside HTTP would be in {{RDFConnectionFuseki}} only.
> Working with Blank Nodes with Fuseki
> ------------------------------------
>
> Key: JENA-1490
> URL: https://issues.apache.org/jira/browse/JENA-1490
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 3.6.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
>
> Be able to work with blank nodes between client and Fuseki server.
> This ticket is mainly about pulling together existing mechanisms.
> This would be a new {{RDFConnectionFactory}} function to return a
> {{RDFConnection}} with the right settings for presevring blank node id.
> Having a new {{RDFConnectionFuseki}}, subclass of {{RDFConnectionRemote}}, to
> handle the right settings and not simply option for {{RDFConnectionRemote}},
> because it is than a place for future Fuseki-specific operations.
>
> When working with a Fuseki remote:
> * Use RDF Thrift (RDF and Result set forms) for efficiency
> * Preserve blank node ids.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
