intertwingly

Mihai Parparita: While developing this sharing feature, it became clear that the ultimate origin of an item in a feed is very important (i.e. I may see it because I’m subscribed to your “web-dev” label, but really it’s from QuirksBlog). We joked about the need for a “Molecule” format that would specify the aggregation of multiple Atom feeds. We even began coding a (namespaced) origin element that would contain the title, id, homepage URL, etc. of the originating site for this item. Then, while re-reading RFC 4287 for another reason, we came across the source element in Atom, which does exactly what we had set out to (re)implement.

[Via Robert Sayre, who quite appropriately attributes this idea to long time Atom Contributor Bob Wyman].

John Cowan: We all (being reasonable persons and not fanatics) are trapped by Quine’s Paradox

Thanks Tim!

jonnay: All this jazz about HTTP error messages, methods beyond GET and POST, its all just good HTTP baby. It has very little to do with actual restfulness or not. All the HTTP conformance in the world wont mean a thing if your application stores client state on the server. You still won’t be RESTful.

In all, it looks like my optimism of nearly three and a half years ago was largely unwarranted.

...