Franz Inc and I just put the AllegroGraph 3.2 Java API on github with my new
Clojure API. The clojure is a wrapper of the java client, which is an
implementation of openrdf/sesame. The wrapper is mostly to make it more
idiomatic clojure so you don't have to deal with so many java classes,
mutable objects, and resources that have to be closed. It's a
work-in-progress, of course, and any feedback is appreciated.
My future plans for this are to have more advance ways of manipulating
triples, especially having them linked up in trees rather than a flat lists
referring to each other, which is what you get back from a query.
By the way, I included the clojure-1.0.jar because I assume this will be
used by companies that need a stable release, but last I checked, the code
works fine with master, and I'm happy to officially support master if that's
what anyone wants.
I am fairly new to git, but from what I can tell, I have the agraph32
branch as current. The clojure code on the agraph32 branch still seems
to be using the AG 4.0 API. For example...
> Franz Inc and I just put the AllegroGraph 3.2 Java API on github with my new
> Clojure API. The clojure is a wrapper of the java client, which is an
> implementation of openrdf/sesame. The wrapper is mostly to make it more
> idiomatic clojure so you don't have to deal with so many java classes,
> mutable objects, and resources that have to be closed. It's a
> work-in-progress, of course, and any feedback is appreciated.
> My future plans for this are to have more advance ways of manipulating
> triples, especially having them linked up in trees rather than a flat lists
> referring to each other, which is what you get back from a query.
> By the way, I included the clojure-1.0.jar because I assume this will be
> used by companies that need a stable release, but last I checked, the code
> works fine with master, and I'm happy to officially support master if that's
> what anyone wants.
You're right, the tests have not been converted to 3.2, so they are not
running at this time. The best thing to look at is the tutorial.clj - most
of these work properly, but example6 doesn't return correct results. The
ones that don't work is where the clj code is incomplete, so I still have
some work to do. I'll get these fixed or documented in the next few days.
-Mike
On Tue, Nov 24, 2009 at 3:31 PM, patrickdlogan <patrickdlo...@gmail.com>wrote:
> I am fairly new to git, but from what I can tell, I have the agraph32
> branch as current. The clojure code on the agraph32 branch still seems
> to be using the AG 4.0 API. For example...
> You're right, the tests have not been converted to 3.2, so they are not
> running at this time. The best thing to look at is the tutorial.clj - most
> of these work properly, but example6 doesn't return correct results. The
> ones that don't work is where the clj code is incomplete, so I still have
> some work to do. I'll get these fixed or documented in the next few days.
> -Mike
> On Tue, Nov 24, 2009 at 3:31 PM, patrickdlogan <patrickdlo...@gmail.com>wrote:
> > Hi Mike - thanks for this.
> > I am fairly new to git, but from what I can tell, I have the agraph32
> > branch as current. The clojure code on the agraph32 branch still seems
> > to be using the AG 4.0 API. For example...
