Reformatted so you can actually tell who said what:
On 4/2/13 9:30 AM, "Rob Vesse" <[email protected]> wrote: >Comments inline: > >From: Claude Warren <[email protected]<mailto:[email protected]>> >Date: Tuesday, April 2, 2013 5:13 AM >To: Rob Vesse <[email protected]<mailto:[email protected]>>, >"[email protected]<mailto:[email protected]>" ><[email protected]<mailto:[email protected]>> >Subject: jdbc4sparql > >Rob, > >I took a quick look at your JDBC experimental project. I didn't see >where it provided a SQL interface. Am I missing something? Nope it intentionally doesn't have one, the aim of my design is to provide a JDBC wrapper around SPARQL and not to try and present any kind of fake SQL abstraction layer on top of it. > > >I have a JDBC4SPARQL project as well -- due to the SQL parser it is not >entirely Apache licensed -- the instance I have talks so SPARQL endpoints >or any Jena readable RDF format file. It presents a compliant JDBC >driver that allows BI tools and other JDBC consumers to view the graph as >a relational database. The mechanism for creating virtual tables is >pluggable -- currently is assumes that all "class" instances are tables >and all properties of the instances are columns. > >If you want to take a look it is at: >https://github.com/Claudenw/jdbc4sparql > >I would be more than happy to contribute it to the JDBC experimental >project if you think it would help. > Adding some sort of layer on top of what I am building to provide the SQL abstraction on top of it might be a nice future extension but right now I am trying to concentrate on getting a solid basic implementation of JDBC to SPARQL going Rob > > >-- Claude > >-- >I like: Like Like - The likeliest place on the >web<http://like-like.xenei.com> >Identity: https://www.identify.nu/[email protected] >LinkedIn: http://www.linkedin.com/in/claudewarren
