2009

My own little Twitter client

No AJAX, Flash, or AIR; just HTML, but arranged the way I want it.

I’ve tried various Twitter clients, but usually just went back to the twitter.com web-based interface that people hate so much. My main complaint with it—and I saw no other clients that did any better—was that it showed tweets in reverse chronological order. Conversations and the multi-tweet mini-essays that some people write are difficult to read that way, so I decided to write my own little client.

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

Some use cases to implement using SPARQL graphs

Or not; I'm open to suggestions.

As I wrote in my last entry, I’ve recently figured out how to assign metadata to RDF graphs and to perform SPARQL queries on sets of those graphs. I’m working a bit backwards here, because I’m now moving on to the use cases that got me thinking about this in the first place. It’s easier to think about them now that I know that I can implement them using standard syntax and multiple open source implementations of that standard. I wanted to outline my ideas about how to…

Querying a set of named RDF graphs without naming the graphs

A big step toward using named graphs to track provenance.

I’d like to thank everyone who added comments to my last post, Some questions about RDF named graphs. Lee Feigenbaum wrote an entire blog post addressing the issues I raised, and it looks like his Open Anzo triplestore (which I’ll write up in its own post soon) has some nice support for versioning, access control, and replication.

Some questions about RDF named graphs

Trying to connect the data structure to real-world use.

Most triplestores support named graphs, and from a high level I can see how they’d be useful, but as I think about using named graphs to address specific application needs, some questions come to mind, so I thought I’d throw them out there.