jena

We use Apache Jena and some related Apache projects as our main SW stack, and it works pretty well.

Plop it all into Neo4J / Jena / rdflib (etc etc) and have at it.

Would this optimization be required always get better performance than Jena or Pellet?

Oh, and we created our datastores by editing Google Sheets, because our wrapper around Jena also had the ability to parse Google Sheets as RDF stores.

We are using Jena as our triplestore, but we don't touch the dbpedia triples directly, but rely on Stanbol to do the entity extraction processing for us.

We just used a godawful custom-written wrapper around Jena (we open-sourced it, and I thought about linking it, but I'm hesitant to tie this account to my real-life identity).

And then this: > Additionally, a drawback of SWI-Prolog speci?cally, against Jena and Pellet, is that since it is not written in Java, it is not as portable (i.e.

I managed to build a reasonably scalable product with the Java based tooling from the Jena project, along with the Python bindings - also the Clark and Parsia tools like Stardog are quite workable.

But as can be seen from figure 15, both prolog versions beat Jena and Pellet by a large margin, though the "shorter" version did so well that it is even hard to notice an increase of the running time linear to the number of triples in the triplestore, in the diagram.

Bismarck predicted: "Jena came twenty years after the death of Frederick the Great; the crash will come twenty years after my departure if things go on like this" "One day the great European War will come out of some damned foolish thing in the Balkans".

The ones I've spent most time with were Jena/TDB, Virtuoso, 3store, along with a couple of proprietary engines.

Go look to Jena, Germany with about 100.000 people.

This company makes some very aggressive claims that allegrograph, Jena, Oracle (with Spatial), sesame and others (including the korean arm of my current company) have also made.