Atom allows lists of information, known as syndication feeds, to be synchronised between publishers and consumers. Atom feeds are composed of a number of entries, each with an extensible set of associated metadata. 1 1 A feed The Atom entry id is the object's resource URI (So there is no id property) 1 1 0 1 content Content 1 represents an individual entry that is contained by the feed. The Atom entry id is the object's resource URI (So there is no id property) 1 1 1 1 1 1 1 common Atom structure an individual entry that is contained by the feed hasEntry hasContent indicates a person or other entity who contributes to the feed a URI associated with the person href a W3C Date-Time Issue Date the default language of the feed indentifies the software agent used to generate the feed, for debugging and other purposes. generator indicates the media type of the content. The atom spec says that most of these will be "application/x.atom+xml" alternate prev service.edit service.post service.feed next start a short summary, abstract or excerpt of the entry human-readable name for the person, corporation or other entity the date and time at which the Entry was modified in W3 format rel start prev service.feed service.post service.edit next alternate the type of relationship that the link represents a human-readable description or tagline for the feed indicates the time that the entry was created. (must have a timeZone in UTC according to atom spec, but check what the dateTime spec requires) indicates the default author of the feed a human-readable title indicates the method used to encode the content xml escaped base64 a human-readable copyright statement for the feed Indicates the version of the Atom specification that the construct conforms to. conveys a human-readable explanation of the feed format itself info e-mail address associated with the person http://bblfish.net/snip/snap/blog1/entry1 I think the field for entering the content itself is missing here... henry.story@bblfish.net http://bblfish.net