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. 0 1 A feed The Atom entry id is the object's resource URI (So there is no id property) common Atom structure 1 1 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) a human-readable title the state of an entry at a time hasContent indicates a person or other entity who contributes to the feed hasEntry an individual entry that is contained by the feed atom:created - indicates the time that the entry was . (must have a timeZone in UTC according to atom spec, but check what the dateTime spec requires) a URI associated with the person a human-readable copyright statement for the feed human-readable name for the person, corporation or other entity rel the type of relationship that the link represents alternate start prev service.edit service.post service.feed next href alternate start service.feed service.post service.edit prev next indicates the media type of the content. The atom spec .3.2 says that most of these will be "application/x.atom+xml" generator indentifies the software agent used to generate the feed, for debugging and other purposes. the default language of the feed e-mail address associated with the person the atom spec 0.3 draft 2 says that a person can only have on e-mail address. What they probably meant to say is that the e-mail relation is Inverse Functional. The "atom:summary" element is a Content construct that conveys a short summary, abstract or excerpt of the entry. onveys a human-readable explanation of the feed format itself date this entry was modified escaped base64 xml indicates the method used to encode the content Issue Date indicates the default author of the feed Indicates the version of the Atom specification that the construct conforms to.