Blog Archives

Thoughts on how to describe a PURL-​like service in RDF

by

Prob­lem: you can add (POST) any con­tent to Talis Con­tent­box but you can­not provide under which URI will end up. The URI is gen­er­ated and it looks like http://​api​.talis​.com/​s​t​o​r​e​s​/​l​g​r​i​d​i​n​o​c​-​d​e​v​1​/​i​t​e​m​s​/​6​7​7​0​4​c​3​e​-​6​786 – 4223-​8701-​db4a493e0757

A PURL–like ser­vice would be use­ful and easy to describe in RDF (stored and query-​able via Metabox), dis­cuss­ing it on #talis, an example came up: Con­tinue reading →

The neverending story of switching blog engines

by

I had this blog first as plain XHTML with hAtom micro­format (so I could gen­er­ate a feed), then I tried Word­Press (even if I hate PHP) and then I tried Pebble, now I’m on Mov­ab­le­Type. And I’m still not pleased.

What I want is real WYSIWYG author­ing with nice XHTML, a decent tem­plate lan­guage (read XSL) and no con­strains (to be detailed later).

So, I’m going to (re)write my own engine, XHTML/​DocBook + XSL + RDF on the Talis plat­form.

Briefly I need to research how to model HTTP; things to study:

The Auryn amulet