On 07/10/13 10:22, Peter Ansell wrote:
Sorry, I pointed to mine as you never pulled my changes into your repository
and they are relevant here. :)
I was waiting for the copyright clarification - you said it was
copyright was the university and were going to get that signed off. As
that didn't arrive, I hadn't merged the changes because it would end up
with code with uncertain provenance.
Andy
--
Peter
On 05/10/2013, at 7:47 PM, Andy Seaborne <[email protected]> wrote:
On 04/10/13 21:38, Peter Ansell wrote:
From memory I think it is a Repository wrapper but I haven't looked at it for
a while.
I am on mobile only for the next week but I think the following is the url:
https://github.com/ansell/jenasesame
Forked from https://github.com/afs/JenaSesame (the file name AFS.txt is a bit
of a give away!)
I hadn't done the Sesame API over Jena storge, only the other way round; Jena
API over Sesame storage. It's not a project I'm working on.
IMO A better way would be to modularize the backends with SPARQL over HTTP or
over an API. . Then you can use a wide range of backends without needing
customization for each (HHTP) or little customization (API). A tiered
architecture, using SPARQL/HTTP for the conenction to the database layer.
Andy
--
Peter
On 05/10/2013, at 12:06 AM, Sergio Fernández
<[email protected]> wrote:
That refresh me the question (which maybe Andy or Peter could answer): is there
any Sesame Sail implementation for Jena?
Add a Jena TDB backend would be cool!
