dichotic noise

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​/​6​7​7​0​4​c​3​e​-​6​786 – 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…)

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:

• A vocabulary for HTTP headers
• Resource and Representation Relationship Vocabulary
• Web Architecture Vocabulary 1.0
• Semantic Web Architecture Vocabulary 1.0
• HTTP Vocabulary in RDF
• Evaluation and Report Language (EARL) 1.0 Guide
• Internet Data Service HTTP Request Schema