Shared publicly  - 
New blog post "Storing and querying RDF in Neo4j" 

Please add any comments about it here.
In the typical classification of NoSQL databases, the "graph" category is one that was not covered in the "NoSQL Databases for RDF: An Empirical Evaluation" paper that I described in my last blog entry. (Several were "column-oriented" databases, which I always thought sounded like triple ...
Roger Sacilotto's profile photoSam Y's profile photoTimothy W. Cook's profile photoRicardo Pietrobon's profile photo
Bob, were you able to test execution time of queries?
Thanks Peter! Juan: Execution time tests wouldn't be worthwhile without larger amounts of data to query, and the part I mentioned about inserting one quad a time and the inability, for now, to just upload an RDF file made that enough trouble that I didn't follow through. I did begin a perl script that converted an NTriples file to insert_quad URLs, but finishing and testing that would have meant putting off the posting of the blog entry longer than I wanted to. 
As far as I can tell, graph databases just are triple stores.  The access path is via S only, so when you fetch an S, you get all triples with that S.  (Also they typically don't support all the XML Schema simple datatypes.)
Thanks for the post, very interesting. FYI the distribution file for the SPARQL plugin isn't available on github anymore, but I'll try to build it from source. 
I had trouble building the sparql plugin because the maven license check plugin was complaining that the Copyright notices were out of date (need to be inclusive of 2015).  Also, could not get unit tests working out of the box.  However, I skipped the tests and the plugin works with the community edition of neo4j, but the limitations of the plugin make it not really usable.  On a different note, Bob, love "Learning SPARQL"!
Add a comment...