triplestores

IBM's DB2 as a triplestore

Surprisingly easy to set up and use, but requiring lots of Java coding for any real application development.

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.

Playing with SPARQL Graph Store HTTP Protocol

GETting, POSTing, PUTting, and DELETEing named graphs.

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…

Writing about the Semantic Web

And Linked Data, and RDF, and RDFa, and SPARQL, and OWL, and...

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…

Getting started with Open Anzo

Don't miss the exciting command line video demo!

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”.