Google

Saturday, December 15, 2007

For other meanings of RSS, see RSS (disambiguation).
For RSS feeds from Wikipedia, see Wikipedia:Syndication.
RSS
The Firefox and Internet Explorer 7 Feed icon.

Screenshot of an RSS feed as seen in Mozilla Thunderbird
File extension: .rss, .xml
MIME type: application/rss+xml (Registration Being Prepared)[1]
Extended from: XML

RSS (formally "RDF Site Summary", known colloquially as "Really Simple Syndication") is a family of Web feed formats used to publish frequently updated content such as blog entries, news headlines or podcasts. An RSS document, which is called a "feed", "web feed", or "channel", contains either a summary of content from an associated web site or the full text. RSS makes it possible for people to keep up with their favorite web sites in an automated manner that's easier than checking them manually.

RSS content can be read using software called an "RSS reader", "feed reader" or an "aggregator". The user subscribes to a feed by entering the feed's link into the reader or by clicking an RSS icon in a browser that initiates the subscription process. The reader checks the user's subscribed feeds regularly for new content, downloading any updates that it finds.

The initials "RSS" are used to refer to the following formats:

RSS formats are specified using XML, a generic specification for the creation of data formats.

Contents

[hide]

[edit] History

Screenshot of an RSS feed in Safari 2.0.4
Screenshot of an RSS feed in Safari 2.0.4

The RSS formats were preceded by several attempts at syndication that did not achieve widespread popularity. The basic idea of restructuring information about web sites goes back to as early as 1995, when Ramanathan V. Guha and others in Apple Computer's Advanced Technology Group developed the Meta Content Framework (MCF).[2] For a more detailed discussion of these early developments, see the history of web syndication technology.

RDF Site Summary, the first version of RSS, was created by Guha at Netscape in March 1999 for use on the My.Netscape.Com portal. This version became known as RSS 0.9.[3] In July 1999, Dan Libby of Netscape produced a new version, RSS 0.91,[4] that simplified the format by removing RDF elements and incorporating elements from Dave Winer's scriptingNews syndication format.[5] Libby also renamed RSS to Rich Site Summary and outlined further development of the format in a "futures document".[6]

This would be Netscape's last participation in RSS development for eight years. As RSS was being embraced by web publishers who wanted their feeds to be used on My.Netscape.Com and other early RSS portals, Netscape dropped RSS support from My.Netscape.Com in April 2001 during new owner AOL's restructuring of the company, also removing documentation and tools that supported the format.[7]

Two entities emerged to fill the void, neither with Netscape's help or approval: The RSS-DEV Working Group and Winer, whose UserLand Software had published some of the first publishing tools outside of Netscape that could read and write RSS.

Winer published a modified version of the RSS 0.91 specification on the UserLand web site, covering how it was being used in his company's products, and claimed copyright to the document.[8] A few months later, UserLand filed a U.S. trademark registration for RSS, but failed to respond to a USPTO trademark examiner's request and the request was rejected in December 2001.[9]

The RSS-DEV Working Group, a project whose members included Guha and representatives of O'Reilly Media and Moreover, produced RSS 1.0 in December 2000.[10] This new version, which reclaimed the name RDF Site Summary from RSS 0.9, reintroduced support for RDF and added XML namespaces support, adopting elements from standard metadata vocabularies such as Dublin Core.

In December 2000, Winer released RSS 0.92[11] a minor set of changes aside from the introduction of the enclosure element, which permitted audio files to be carried in RSS feeds and helped spark podcasting. He also released drafts of RSS 0.93 and RSS 0.94 that were subsequently withdrawn.[12]

In September 2002, Winer released a major new version of the format, RSS 2.0, that redubbed its initials Really Simple Syndication. RSS 2.0 removed the type attribute added in the RSS 0.94 draft and added support for namespaces.

Because neither Winer nor the RSS-DEV Working Group had Netscape's involvement, they could not make an official claim on the RSS name or format. This has fueled ongoing controversy in the syndication development community as to which entity was the proper publisher of RSS.

One product of that contentious debate was the creation of a rival syndication format, Atom, that began in June 2003. The Atom syndication format, whose creation was in part motivated by a desire to get a clean start free of the issues surrounding RSS, has been adopted as an IETF standard.

In July 2003, Winer and UserLand Software assigned the copyright of the RSS 2.0 specification to Harvard's Berkman Center for the Internet & Society, where he had just begun a term as a visiting fellow.[13] At the same time, Winer launched the RSS Advisory Board with Brent Simmons and Jon Udell, a group whose purpose was to maintain and publish the specification and answer questions about the format.[14]

In December 2005, the Microsoft Internet Explorer team[15] and Outlook team[16] announced on their blogs that they were adopting the feed icon first used in the Mozilla Firefox browser . A few months later, Opera Software followed suit. This effectively made the orange square with white radio waves the industry standard for RSS and Atom feeds, replacing the large variety of icons and text that had been used previously to identify syndication data.

In January 2006, RSS Advisory Board chairman Rogers Cadenhead announced that eight new members had joined the group, continuing the development of the RSS format and resolving ambiguities in the RSS 2.0 specification. Netscape developer Chris Finke joined the board in March 2007, the company's first involvement in RSS since the publication of RSS 0.91. In June 2007, the board revised its version of the specification to confirm that namespaces may extend core elements with namespace attributes, as Microsoft has done in Internet Explorer 7. In its view, a difference of interpretation left publishers unsure of whether this was permitted or forbidden.

[edit] Incompatibilities

As noted above, there are several different versions of RSS, falling into two major branches (RDF and 2.*). The RDF, or RSS 1.* branch includes the following versions:

The RSS 2.* branch (initially UserLand, now Harvard) includes the following versions:

For the most part, later versions in each branch are backward-compatible with earlier versions (aside from non-conformant RDF syntax in 0.90), and both versions include properly documented extension mechanisms using XML Namespaces, either directly (in the 2.* branch) or through RDF (in the 1.* branch). Most syndication software supports both branches. Mark Pilgrim's article "The Myth of RSS Compatibility" discusses RSS version compatibility in more detail.

The extension mechanisms make it possible for each branch to track innovations in the other. For example, the RSS 2.* branch was the first to support enclosures, making it the current leading choice for podcasting, and as of mid-2005 is the format supported for that use by iTunes and other podcasting software; however, an enclosure extension is now available for the RSS 1.* branch, mod_enclosure. Likewise, the RSS 2.* core specification does not support providing full-text in addition to a synopsis, but the RSS 1.* markup can be (and often is) used as an extension. There are also several common outside extension packages available, including a new proposal from Microsoft for use in Internet Explorer 7.

The most serious compatibility problem is with HTML markup. Userland's RSS reader—generally considered as the reference implementation—did not originally filter out HTML markup from feeds. As a result, publishers began placing HTML markup into the titles and descriptions of items in their RSS feeds. This behavior has become expected of readers, to the point of becoming a de facto standard, though there is still some inconsistency in how software handles this markup, particularly in titles. The RSS 2.0 specification was later updated to include examples of entity-encoded HTML; however, all prior plain text usages remain valid.

[edit] Modules

The primary objective of all RSS modules is to extend the basic XML schema established for more robust syndication of content. This inherently allows for more diverse, yet standardized, transactions without modifying the core RSS specification.

To accomplish this extension, a tightly controlled vocabulary (in the RSS world, "module"; in the XML world, "schema") is declared through an XML namespace to give names to concepts and relationships between those concepts.

Some RSS 2.0 modules with established namespaces:

[edit] BitTorrent and RSS

The peer-to-peer application BitTorrent has also announced support for RSS. Such feeds (also known as Torrent/RSS-es or Torrentcasts) will allow client applications to download files automatically from the moment the RSS reader detects them (also known as Broadcatching). Most common BitTorrent clients already offer RSS support.

[edit] Examples

[edit] RSS 1.0

The following is an example of an RSS 1.0 file.

 version="1.0"?>


xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns="http://purl.org/rss/1.0/">

 rdf:about="http://www.xml.com/xml/news.rss">
  >XML.com>
  >http://xml.com/pub>
  >
    XML.com features a rich mix of information and services
    for the XML community.
  >
   rdf:resource="http://xml.com/universal/images/xml_tiny.gif" />
  >
    >
       rdf:resource="http://xml.com/pub/2000/08/09/xslt/xslt.html" />
       rdf:resource="http://xml.com/pub/2000/08/09/rdfdb/index.html" />
    >
  >
   rdf:resource="http://search.xml.com" />
>

 rdf:about="http://xml.com/universal/images/xml_tiny.gif">
  >XML.com>
  >http://www.xml.com>
  >http://xml.com/universal/images/xml_tiny.gif>
>

 rdf:about="http://xml.com/pub/2000/08/09/xslt/xslt.html">
  >Processing Inclusions with XSLT>
  >http://xml.com/pub/2000/08/09/xslt/xslt.html>
  >
   Processing document inclusions with general XML tools can be
   problematic. This article proposes a way of preserving inclusion
   information through SAX-based processing.
  >
>

 rdf:about="http://xml.com/pub/2000/08/09/rdfdb/index.html">
  >Putting RDF to Work>
  >http://xml.com/pub/2000/08/09/rdfdb/index.html>
  >
   Tool and API support for the Resource Description Framework
   is slowly coming of age. Edd Dumbill takes a look at RDFDB,
   one of the most exciting new RDF toolkits.
  >
>

 rdf:about="http://search.xml.com">
  >Search XML.com>
  >Search XML.com's XML collection>
  >s>
  >http://search.xml.com>
>
>

[edit] RSS 2.0

The following is an example of an RSS 2.0 file.

 version="1.0"?>
 version="2.0">
 >
   >Liftoff News>
   >http://liftoff.msfc.nasa.gov/>
   >Liftoff to Space Exploration.>
   >en-us>
   >Tue, 10 Jun 2003 04:00:00 GMT>
   >Tue, 10 Jun 2003 09:41:01 GMT>
   >http://blogs.law.harvard.edu/tech/rss>
   >Weblog Editor 2.0>
   >editor@example.com>
   >webmaster@example.com>

   >
     >Star City>
     >http://liftoff.msfc.nasa.gov/news/2003/news-starcity.asp>
     >How do Americans get ready to work with Russians aboard the
       International Space Station? They take a crash course in culture, language
       and protocol at Russia's Star City.>
     >Tue, 03 Jun 2003 09:39:21 GMT>
     >http://liftoff.msfc.nasa.gov/2003/06/03.html#item573>
   >

   >
     >Space Exploration>
     >http://liftoff.msfc.nasa.gov/>
     >Sky watchers in Europe, Asia, and parts of Alaska and Canada
       will experience a partial eclipse of the Sun on Saturday, May 31st.>
     >Fri, 30 May 2003 11:06:42 GMT>
     >http://liftoff.msfc.nasa.gov/2003/05/30.html#item572>
   >

   >
     >The Engine That Does More>
     >http://liftoff.msfc.nasa.gov/news/2003/news-VASIMR.asp>
     >Before man travels to Mars, NASA hopes to design new engines
       that will let us fly through the Solar System more quickly.  The proposed
       VASIMR engine would do that.>
     >Tue, 27 May 2003 08:37:32 GMT>
     >http://liftoff.msfc.nasa.gov/2003/05/27.html#item571>
   >

   >
     >Astronauts' Dirty Laundry>
     >http://liftoff.msfc.nasa.gov/news/2003/news-laundry.asp>
     >Compared to earlier spacecraft, the International Space
       Station has many luxuries, but laundry facilities are not one of them.
       Instead, astronauts have other options.>
     >Tue, 20 May 2003 08:56:02 GMT>
     >http://liftoff.msfc.nasa.gov/2003/05/20.html#item570>
   >
 >
>

# posted by Google Publisher : 3:54 AM  0 Comments

This page is powered by Blogger. Isn't yours?

Subscribe to Posts [Atom]