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

Problem: you can add (POST) any content to Talis Contentbox but you cannot provide under which URI will end up. The URI is generated 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​/​67704​c​3​e​-​6786 – 4223-​8701-​db4a493e0757

A PURL–like service would be useful and easy to describe in RDF (stored and query-​able via Metabox), discussing it on #talis, an example came up: (more…)

Semantic Web Logo

I don’t really love the Semantic Web logo:

W3C Semantic Web Logo

…but it provides a magnificent way to illustrate its intertwingularity of specifications:

The Semantic Web Rubik Cube

…as opposed to various versions and interpretations [1] of classical layer cake, now you can freely make your combinations.

[1] Towards a Semantic Web Layered Architecture

W3C Tech Reports and Readability

I noticed that I always print any W3C TR in order to read it… and I discovered one reason: the lack of a (good) typographic style.

Basically the issues are:

  1. the text is too wide (if you shrink the window you have to scroll horizontally for tables and code samples)
  2. the line spacing is too small, and makes difficult to follow the line, especially on lists which sometimes have mixed fonts (usually monospaced and serif)
  3. there is no vertical rhythm, and this tires your eyes (read brain)

(more…)

The neverending story of switching blog engines

I had this blog first as plain XHTML with hAtom microformat (so I could generate a feed), then I tried WordPress (even if I hate PHP) and then I tried Pebble, now I’m on MovableType. And I’m still not pleased.

What I want is real WYSIWYG authoring with nice XHTML, a decent template language (read XSL) and no constrains (to be detailed later).

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

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

The Auryn amulet