Simon Willison’s Weblog

Subscribe
Atom feed for atom Random

52 posts tagged “atom”

2008

HTTP Cache Channels (via) Interesting extension to the HTTP caching model by Mark Nottingham: caches can be told to subscribe to an Atom feed which alerts them to cached data that has gone stale. Group invalidation is also supported.

# 4th January 2008, 12:48 pm / atom, cachechannels, caching, http, mark-nottingham, squid

2007

Updates to template_utils. James Bennett’s Django template_utils library now provides tags for consuming external RSS and Atom feeds. Combine with template fragment caching for an instant mashup written just using templates.

# 10th December 2007, 3:25 pm / atom, django, feeds, james-bennett, python, rss, templateutils, universalfeedparser

Atom Models. Building Python classes that act as utility wrappers around data stored in an lxml DOM object.

# 7th August 2007, 4:02 pm / atom, dom, ian-bicking, lxml, python, xml

Google AJAX Feed API (via) Simple cross-domain proxy to allow JavaScript to access any publically addressable syndication feed, with the same logic as Google Reader providing normalisation.

# 18th April 2007, 5:29 pm / ajax, atom, crossdomain, feed, google, google-reader, javascript, rss, syndication

Triplr. Ultra simple GET-based web service for converting RSS / Atom / RDF / Microformats+GRDDL to HTML / ntriples / RDF / RSS / JSON / Turtle. Small pieces, loosely joined.

# 30th March 2007, 3:30 pm / atom, grddl, html, json, microformats, ntriples, rdf, rss, semanticweb, triplr, turtle

Pipes. New Yahoo! service for combining and remixing Atom/RSS feeds using a really sophisticated drag-and-drop UI.

# 8th February 2007, 7:52 am / atom, draganddrop, pipes, rss, syndication

Gmail Atom feeds. Could be useful as a pipe for creating an e-mail interface to an existing Atom-consuming application.

# 16th January 2007, 2:50 pm / atom, gmail

Atom API for AOL Journals. AOL are doing some really cool things with the Atom Publishing Protocol.

# 10th January 2007, 11:06 pm / aol, app, atom

2006

Atom as a Case Study. Notes from one of my favourite talks at ETech.

# 21st March 2006, 8:20 am / atom

2004

XML.com: Identifying Atom. The hidden complexity of URIs is fascinating.

# 19th August 2004, 4:08 am / atom

Introducing dbagg3, an Atom-powered client/server aggregator. Way smart aggregator built on top of Atom and XSLT.

# 6th August 2004, 4:08 pm / atom, xslt

Atom discussion minutes

The minutes from the Atom/W3C discussion in New York have been posted online. Unfortunately the default formatting is pretty difficult to follow. I found it a lot easier to figure out who was saying what after applying the following CSS (using the test styles bookmarklet):

[... 81 words]

Why the W3C wants Atom. Matt May explains all.

# 13th May 2004, 11:45 pm / atom

W3C proposes an Atom working group. Can you smell the flames yet?

# 13th May 2004, 5:56 pm / atom

Mark Pilgrim’s Atom feed (via) Atom + XSL + CSS = a self explanatory feed that functions in a browser.

# 4th May 2004, 5:39 pm / atom, mark-pilgrim, xslt

Hypocrisy: RDF and the Atom API. Russell really doesn’t like PUT and DELETE.

# 19th February 2004, 3:58 am / atom

RSS vs Atom, condensed

Jeremy Zawodny:

[... 63 words]

2003

Atom autodiscovery test suite

Mark Pilgrim has released the Atom autodiscovery test suite, comprising 148 tests:

[... 130 words]

Atom API

Mark Pilgrim has posted an extensively documented demonstration of the current draft of the Atom API, a REST style web service interface for posting to and editing weblogs. It looks like it will be a fun standard to implement; the basic idea (as with all REST services) is to obtain as much leverage as possible out of the HTTP standard, using lesser known methods such as PUT and DELETE in addition to the more common GET and POST. The authentication mechanism is particularly interesting: since Apache’s support for digest authentication requires an additional module that many hosts may not provide, the Atom guys have created their own based around new Atom-Authenticate HTTP headers.

[... 227 words]