Cassa
From the webpage:
A SPARQL 1.1 Graph Store HTTP Protocol [1] implementation for RDF and Topic Maps.
The somewhat longer announcement on topicmapmail, SPARQL 1.1 Graph Store HTTP Protocol for Topic Maps:
Last week discovered the SPARQL 1.1 Graph Store HTTP Protocol [1] and I wondered if this wouldn’t be a good alternative to SDShare [2].
The graph store protocol uses no artificial technologies like Atom but uses REST and RDF consequently. The service uses an ontology [3] to inform the client about available graphs etc.
The protocol allows creation of graphs, deletion of graphs and updating graphs and discovery of graphs (through the service description).
The protocol is rather generic, so it’s usable for Topic Maps as well (graph == topic map).
The protocol provides no fragments/snapshots like SDShare, though. Adding these functionality to the protocol would be interesting, I’d think. I.e. each graph update would trigger a new fragment. Maybe this functionality would also solve the “push problem” [4] without inventing yet another syntax. The description of the available fragments should also be done with an ontology and not solely with Atom, though.
Anyway, I wanted to mention it as a good, *dogfooding* protocol which could be used for Topic Maps.
I created an implementation (Cassa) of the protocol at [5] (no release yet). The implementation supports Topic Maps and RDF but it doesn’t provide the service description yet. And I didn’t translate the service description ontology to Topic Maps yet.
[1] <http://www.w3.org/TR/2011/WD-sparql11-http-rdf-update-20110512/>
[2] <http://www.egovpt.org/fg/CWA_Part_1b>
[3] <http://www.w3.org/TR/2011/WD-sparql11-service-description-20110512/>
[4] <http://www.infoloom.com/pipermail/topicmapmail/2010q4/008761.html>
[5] <https://github.com/heuer/cassa>