intertwingly

Clay Shirkey: A LazyWeb item in RDF has only four elements, set by the Trackback spec -- title, link, description, and date. Thus almost all the onus on filtering the feed is on the subscriber, not the producer. An RDF format with optional but recommended tags (type: feature, schema, application, etc; domain: chat, blog, email, etc.) might allow for higher-quality syndication, but would be hard with the current version of Trackback

Trackback 1.0 used HTTP GET to transfer state data from the client to the server, a no-no from a REST perspective. I noticed this, suggested to Paul Prescod that he work with Ben, and they did all the hard work.  The result was Trackback 1.1. A model of RESTitude.

Now along comes another application which would like to extend this API. Wouldn't It Be Nice If instead of URL encoded parameters, one could simply POST the RSS item that contains all the yummy goodies that one could imagine and let the server decide what pieces it wanted to keep and what pieces it chooses to ignore?

This is how the RESTLog API works today...