Atom (standard) Article Index for
Atom
Website Links For
Atom
 

Information About

Atom (standard)




  Icon and Internet Explorer 7 Feed Icon ]]
  Extension <tt>atom</tt>, <tt>xml</tt>
  Mime application/atom+xml
  Genre Syndication
  Extendedfrom XML


''Atom'' is the name of a specific Web Feed format. Web feeds, from ''a user's perspective'', allow Internet users to subscribe to websites that change or add content regularly. To use this technology, site owners create or obtain specialized Software (such as a Content Management System ) which, in the machine-readable XML format, presents new articles in a list, giving a line or two of each article and a link to the full article or post. Unlike subscriptions to many printed newspapers and magazines, most web subscriptions are free.

Web feeds in general provide web content or summaries of web content together with links to the full versions of the content, and other meta-data in a developer-friendly standardized format. Atom in particular delivers this information as an XML file called an Atom feed, webfeed, Atom stream, or Atom channel. In addition to facilitating syndication, web feeds allow a website's frequent readers to track updates on the site using an Aggregator .

''Atom'', from a ''technical perspective'', is an open standard that includes both:
  • an XML-based Web Syndication format used by Weblog s, news websites and web mail and,

  • an HTTP-based protocol for remote editing of Atom-based weblogs


The development of Atom was motivated by perceived deficiencies in the proposed standard detailed in the recently released RFC 4287.


USAGE


Web feeds are used by the Weblog community to share the latest entries' headlines or their full text, and even attached multimedia files. (See Podcasting , Vodcasting , Broadcasting , Screencasting , Vloging , and MP3 Blog s.) These providers allow other websites to incorporate their "syndicated" headline or headline-and-short-summary feeds under various usage agreements. Atom and other web syndication formats are now used for many purposes, including marketing, bug-reports, or any other activity involving periodic updates or publications.

A program known as a feed reader or aggregator can check webpages on behalf of a user and display any updated articles that it finds. It is common to find web feeds on major Web sites, as well as many smaller ones. Some websites let people choose between RSS or Atom formatted web feeds; others offer only RSS or only Atom. In particular, many Blog and Wiki sites offer their web feeds in the Atom format.

Client-side readers and aggregators are typically constructed as standalone programs or extensions to existing programs like Web Browser s. Browsers are moving toward integrated feed reader functions, such as Safari RSS , Opera , Firefox and Internet Explorer . Such programs are available for various operating systems.

Web-based feed readers and news aggregators require no software installation and make the user's "feeds" available on any computer with Web access. Some aggregators syndicate (combine) web feeds into new feeds, e.g., take all football related items from several sports feeds and provide a new football feed. There are also search engines for content published via web feeds like Technorati and Blogdigger .

On Web pages, web feeds (Atom or RSS) are typically linked the word "Subscribe" or with an orange rectangle, .


ATOM COMPARED TO RSS 2.0


The main starting point and motivation for the development of Atom was the perceived deficiencies in widely adopted RSS 2.0 syndication format [http://www.sixapart.com/about/news/2003/06/why_we_need_ech.html]. The intention was to ease the difficulty of developing applications with web syndication feeds. A brief description of the main issues of RSS 2.0 addressed by Atom 1.0 follows [http://www.intertwingly.net/wiki/pie/Rss20AndAtom10Compared], [http://www.tbray.org/atom/RSS-and-Atom]:
  • RSS 2.0 may contain either plain text or escaped HTML as a payload, with no way to indicate which of the two is provided. Atom in contrast uses an explicitly labeled (i.e. typed) payload container.

  • RSS 2.0 has a "description" element which can contain either a full entry or just a description. Atom has separate “summary” and “content” elements. Atom thus allows the inclusion of non-textual content that can be described by the summary.

  • Atom standardizes Autodiscovery in contrast to the many non-standard variants used with RSS 2.0.

  • Atom is within an XML Namespace whereas RSS 2.0 is not.

  • Atom specifies use of the XML's built-in xml:base for relative URI s. RSS 2.0 does not have a means of differentiating between relative and non-relative URIs.

  • Atom uses XML's built-in xml:lang attribute as opposed to RSS 2.0's use of its own "language" element.

  • In Atom, it is mandatory that each entry has a globally unique ID, which is important for reliable updating of entries.

  • Atom 1.0 allows standalone Atom Entry documents whereas with RSS 2.0 only full documents are supported.

  • RSS 2.0 was copyrighted by Harvard University and it was purposely frozen. Atom is an open and evolvable standard that has undergone the IETF standardization process.

  • Atom specifies that dates be in the format described in RFC 3339 (which is a subset of ISO 8601 ). Date format in RSS 2.0 was underspecified and has led to many different formats being used.

  • Atom 1.0 has IANA-registered MIME-type. RSS 2.0 feeds are often sent as application/rss+xml, although it's not officially accepted MIME-type.

  • Atom 1.0 includes an XML Schema . RSS 2.0 does not.



DEVELOPMENT HISTORY



Background

Prior to the creation of Atom, the primary method for web content syndication was via the RSS family of formats.

Members of the community who felt there were significant deficiencies with this family of formats were unable to make changes directly to RSS 2.0, because it was not an open standard. RSS 2.0 was copyrighted by Harvard University and in the official specification document it stated that it was purposely frozen "no significant changes can be made and it is intended that future work be done under a different name". {Link without Title}


Initial Work

In . It also became clear that the new format could also form the basis of a more robust replacement for blog editing protocols such as Blogger API and LiveJournal XML-RPC Client/Server Protocol.

The project aimed to develop a web syndication format that was: {Link without Title}
  • "100% vendor neutral,"

  • "implemented by everybody,"

  • "freely extensible by anybody, and"

  • "cleanly and thoroughly specified."


In short order, a project road map was built. The effort quickly attracted more than 150 supporters including , the key figure behind RSS 2.0 , gave tentative support to the Atom endeavor (which at the time was called Echo.)[http://backend.userland.com/2003/06/26]

After this point, discussion became chaotic, due to the lack of a decision-making process. The project also lacked a name, with "Pie," "Echo," and "Necho" used before settling on Atom. After releasing a project snapshot known as ''Atom 0.2'' in early July 2003, discussion was shifted off the wiki.


Atom 0.3 and Adoption by Google

The discussion then moved to a newly set up mailing list. The next and final snapshot during this phase was ''Atom 0.3'', released in December 2003. This version gained widespread adoption in syndication tools, and in particular it was added to several Google -related services, such as Blogger , Google News and Gmail .


Atom 1.0, Microsoft support and IETF standardization

In , finally giving the project a charter and process. The Atompub working group is co-chaired by Tim Bray (the co-editor of the XML specification) and Paul Hoffman. Initial development was focused on the syndication format.

The final draft of ''Atom 1.0'' was published in July 2005 and was accepted by the IETF as a "proposed standard" in August of 2005. Work then continued on the further development of the publishing protocol and various extensions to the syndication format.

Microsoft, in its release of Internet Explorer 7 Betas in late 2005 and early 2006, added Atom support to its integrated feed browser and web feed platform. Microsoft now consistently uses the term Web Feed to describe the technology instead of the format-specific RSS term.

The Atom Syndication Format was issued as a proposed "internet official protocol standard" in IETF RFC 4287 in December 2005. {Link without Title} The co-editors of RFC 4287 were Mark Nottingham and Robert Sayre .


EXAMPLE OF AN ATOM 1.0 FEED

An example of an Atom Feed document:




Example Feed
Insert witty or insightful remark here

2003-12-13T18:30:02Z

John Doe
johndoe@example.com

urn:uuid:60a76c80-d399-11d9-b91C-0003939e0af6


Atom-Powered Robots Run Amok

urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a
2003-12-13T18:30:02Z
Some text.






SEE ALSO



EXTERNAL LINKS