[
https://issues.apache.org/jira/browse/ANY23-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967168#comment-13967168
]
Rob Vesse edited comment on ANY23-105 at 4/11/14 10:13 PM:
-----------------------------------------------------------
I already mentioned the idea briefly to [~andy.seaborne] on our mailing list
(http://mail-archives.apache.org/mod_mbox/jena-dev/201404.mbox/%[email protected]%3e)
and he had the following to say specific to this issue:
{quote}
Gora/Any23 can output to {{StreamRDF}} and then it should plug in.
Any23 is Sesame-based but the rewrite from Sesame-objects to
Jena-objects is a single copy so not too bad.
{quote}
Using the {{StreamRDF}} API is quite a good option because it is agnostic of
the ultimate destination of the data and so can be used to write to TDB, disk
or somewhere else entirely. Behind the scenes the TDB bulk loader is
implemented in terms of {{StreamRDF}}
It would likely be relatively easy to go with [~p_ansell]'s suggestion of
implementing a Sesame {{TripleHandler}} which does the conversion to Jena
objects and passes them through to a {{StreamRDF}} instance.
So between using Sesame's {{TripleHandler}} and the Jena {{StreamRDF}}
interface you would be supporting the abstract data ingest APIs of both
libraries and then end users can plug in standard/custom implementations as
they see fit.
was (Author: rvesse):
I already mentioned the idea briefly to [~andy.seaborne] on our mailing list
(http://mail-archives.apache.org/mod_mbox/jena-dev/201404.mbox/%[email protected]%3e)
and he had the following to say specific to this issue:
{quote}
Gora/Any23 can output to {{StreamRDF}} and then it should plug in.
Any23 is Sesame-based but the rewrite from Sesame-objects to
Jena-objects is a single copy so not too bad.
{/quote}
Using the {{StreamRDF}} API is quite a good option because it is agnostic of
the ultimate destination of the data and so can be used to write to TDB, disk
or somewhere else entirely. Behind the scenes the TDB bulk loader is
implemented in terms of {{StreamRDF}}
It would likely be relatively easy to go with [~p_ansell]'s suggestion of
implementing a Sesame {{TripleHandler}} which does the conversion to Jena
objects and passes them through to a {{StreamRDF}} instance.
So between using Sesame's {{TripleHandler}} and the Jena {{StreamRDF}}
interface you would be supporting the abstract data ingest APIs of both
libraries and then end users can plug in standard/custom implementations as
they see fit.
> Implement functionality to export content from Any23 service to TDB
> --------------------------------------------------------------------
>
> Key: ANY23-105
> URL: https://issues.apache.org/jira/browse/ANY23-105
> Project: Apache Any23
> Issue Type: New Feature
> Components: CLI, core, service
> Affects Versions: 0.7.0
> Reporter: Lewis John McGibbney
> Fix For: 1.0.0
>
>
> OK so I think it would be really neat to provide an export functionality
> which takes your local/remote Jena TDB instance and posts the triples
> extracted by Any23 for persistence.
> I need to be honest and say that at this stage I don't know much about how to
> implement this, but somewhere down the line I'll look forward to learning.
> There is a reasonable argument here to extend this further than TDB but a.t.m
> I think TDB but this is up for discussion I suppose.
> To finish, I think it should be mentioned (again) the webservice looks great.
> I think we should work on getting the live demo service implemented at the
> zone provided for us... this is another issue though.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
