After I posted Reification is a red herring (and you don’t need property graphs to assign data to individual relationships) last month, I had an amusingly difficult time explaining to my wife how that would generate so much Twitter activity. This month I wanted to make it clear that I’m not opposed to reification in and of itself, and I wanted to describe the fun I’ve been having playing with Olaf Hartig and Bryan Thompson’s RDF* and and SPARQL* extensions to these…

I’ve been hearing more about the Blazegraph triplestore (well, “graph database with RDF support”), especially its support for running on GPUs, and because they also advertise some degree of RDFS and OWL support, I wanted to see how quickly I could try that after downloading the community edition. It was pretty quick.

A little over a year ago, in a blog entry titled SPARQL and Big Data (and NoSQL), I wrote this:

I thought it was pretty big news for the semantic web world when IBM announced that release 10.1 of their venerable DB2 database manager could function as an RDF triplestore, but it seems that few others—not even, apparently, IBM staff responsible for marketing semantic technology—agreed with me. More on this below.

One of the new SPARQL 1.1 specifications is the SPARQL 1.1 Graph Store HTTP Protocol, which is currently still a W3C Working Draft. According to its abstract, it “describes the use of HTTP operations for the purpose of managing a collection of graphs in the REST architectural style.” Recent releases of Sesame support it, so I used that to try out some of the operations described by this spec. I managed to do GET, PUT, POST, and DELETE operations with individual named graphs, so that…

After writing a few paid articles and doing a lot of blogging about various issues, features, and trends surrounding the Semantic Web, Linked Data, RDF, RDFa, SPARQL, OWL, and related tools and implementations, I thought it would be nice if I could tie them together into something resembling a cohesive whole. So, I wrote a short essay titled RDF, The Semantic Web, and Linked Data with over 70 footnote links to these various pieces. It will be a handy reference for me in the future, and I hope it…

Open Anzo is the third disk-based triplestore that I managed to set up, load with a few files of RDF data, and query with SPARQL. Its home page describes it as “an open source enterprise-featured RDF store and service oriented middleware platform that provides support for multiple users, distributed clients, offline work, real-time notification, named-graph modularization, versioning, access controls, and transactions with preconditions”.