[jira] [Comment Edited] (JENA-1490) Working with Blank Nodes with Fuseki

["Andy Seaborne (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JENA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369984#comment-16369984 ] 

Andy Seaborne edited comment on JENA-1490 at 2/20/18 12:34 PM:
---------------------------------------------------------------

It would use HTTP.  It can go to different endpoints and use different content types.

Fuseki nowadays can have additional, configurable services.

Do you make use of {{RDFConnection}}? Experiences?


was (Author: andy.seaborne):
It would use HTTP.  It can go to different endpoints and use different content types.

Fuseki nowadays can have additional, configurable services.

Do you make use of {{RFConnection}}? Experiences?

> 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)