Welcome to the RSS Version 3 Frequently Asked Questions Page, where the most relevant information concerning the standard is available in a Question-Answer form. If you have a question which is not found here, please contact the Editor or post a note in the Message Board.

Question List

Click on the following links to jump to the question:

  1. What is RSS?
  2. How is it made?
  3. What are the RSS standards?
  4. For what purpose is the RSS Version 3 standard necessary?
  5. Why no namespaces?
  6. Why no escaped or proper HTML?
  7. Why not use xml:id, xml:lang etc. instead of the corresponding RSS features?
  8. What does the Version 3 class contain?
  9. Why are there three different standards?
  10. And what is RCDL?
  11. And RRDL?
  12. How can I help?
  13. What is the history of RSS?
  14. Who designs the RSS Version 3 standard?

What is RSS?

RSS stands for Really Simple Syndication. It is a way to broadcast online content's metadata via the Internet - thus letting webmasters inform users who read the RSS feed of changes in their site (updates, news, new links etc.) or inform applications of changes in a service.

How is it made?

RSS is an XML based standard, with an intentionally well-understood and simplified structure. An RSS 3 file carries the suffix .rss, though note that feeds may be URLs, either containing parameters or not.

Once a user is a aware of the feed, he may choose to apply to it using programs (or features) called Aggregators. These programs are supposed to withdraw the metadata from the given feed and present it in a human-readable manner for the user. An aggregator may also choose to allow the user to use some or all of the more advanced features of RSS, such as categorizing, enclosed files, thumbnail images among others.

What are the RSS standards?

Currently, there are three classes of RSS standards:

  1. The 0.9x class (where x is a number between and including 1 to 4)
  2. The 1.0 class (using an RDF structure, thus excluding all others)
  3. The 2.0 class (the popular standard using the 2.0.1 specifications which is a reworking of 0.94)

This site's purpose is to develop and document a new standard, the RSS Version 3, based on the 2.0 class.

For what purpose is the RSS Version 3 standard necessary?

The 0.9x class of standards is outdated and underdocumented. The 2.0 class is highly underdocumented, filled with unnecessary features though lacking others which could be useful. The RSS 3 standard is supposed to extensively document the standard, to expand where expansion is needed and to remove unnecessary features.

Why no namespaces?

Though XML namespaces offer several advantages to some, in the particular case of the RSS standard it hold many disadvantages. In using XML namespaces the standard is prevented from being backwards-compatible, which is a requirement imperative to the standard.

However, anyone who wishes to use elements in an RSS document which are not a part of the format itself must place them under a namespace. Also, the RSS 3 Extension Modules all use namespaces in order to separate them from the proper format.

Why no escaped or proper HTML?

The RSS format is no longer used solely in relation to web pages and it cannot be assumed that the aggregator processing the document is able to process HTML, whether in escaped or proper form. (Escaped example: escaped -- Proper example: proper)

However, for those who wish to transmit proper HTML (or XHTML) the feature has been set up.

Why not use xml:id, xml:lang etc. instead of the corresponding RSS features?

Though the XML language does indeed provide mechanisms for the identification of an element's ID, language or base-file, the RSS format's needs are greater than the scope of those mechanisms. For example, using the xml:lang attribute in an element describes the language of the metadata itself, while the element can describe the language of the item's destination. Also, handling further elements instead of extra-attributes makes processing an RSS document much easier.

What does the Version 3 class contain?

In theory, RSS Version 3 Standard consists of two specifications: RSS 3 Lite and RSS 3 Full, the latter covering the first, though the first excludes the latter (i.e, an RSS 3 Lite file can also apply to a RSS 3 Full aggregator, but an RSS 3 Full file will be processed in a Lite-only aggregator with the Full-only features being ignored).

Two related standards are the RSS Categories Declaration Language (RCDL) and the RSS Rating Description Language (RRDL).

Why are there three different standards?

There aren't. The two RSS 3 specifications, Lite and Full, are both parts of the RSS 3 Standard. The Full version is the one with all the advanced features for high-end aggregators. The Lite version is a small-scale version of features, all included in the Full version, meant to be used by aggregators which are only a feature of a greater program or site (for example, an RSS aggregator within a browser such as Mozilla Firefox should use RSS 3 Lite while the rss/news/email reader of the same source, Mozilla Thunderbird, should use the RSS 3 Full specifications).

The RSS 3 Lite specification is available here, while the RSS 3 Full specification is available here.

And what is RCDL?

The RSS Category Declaration Language (RCDL) is supposed to be an XML based language used to produce a file to which an RSS feed links in case it uses the categories feature. An RCDL file would contain simple declaration of the different categories, with several other, optional, features. This is meant to help an aggregator organize the feed content better.

This standard is an extension created to relate to the element.

And RRDL?

The RSS Rating Description Language (RCDL) is an XML based language used to create classes of ratings (a single class containing several ratings) and giving them descriptions. An RRDL file would be linked from an RSS document in order to describe to the aggregator the different ratings used.

This standard is an extension created to relate to the element.

How can I help?

One can always help by posting useful features and comments in the Message Board or otherwise emailing the editor. Also, once a specification is in a Call for Comments or Call for Review stage (see the Process section in the Requirements page), all reviews of the standard are appreciated.

What is the history of RSS?

A rather complete and thorough history of RSS can be found here.

Who designs the RSS Version 3 standard?

Jonathan Avidan managers this site and edits the specifications according to common requests and open debates held in the Message Board and via email.



Navigate: Home | Message Board | FAQ | Extensions | Specifications | Requirements | Terminology | RSS 3 Lite | Links | Contact Us

©2005 Jonathan Avidan - Created using Nvu - Distributed under the Attribution/Share Alike Creative Commons License