Home > Articles > Web Services > XML

RSS: Implementation Issues and Recommendations

📄 Contents

  1. Picking Your RSS Flavor
  2. Validating the RSS Feed
If you're going to set up content distribution with RSS, you'll need to make some basic decisions. After that, though, it's pretty easy to implement RSS feeds on your site.
Like this article? We recommend

Like this article? We recommend

As I discussed in my previous article, RSS is a powerful new channel for content distribution. In this piece, we'll look at implementation issues for both of the leading RSS standards (RSS 1.0 and RSS 2.0) and consider a step-by-step approach to successfully implement these standards on a web site.

CSS Transformation of RSS Feeds: A Contentious Issue

There has recently been some discussion as to whether to transform RSS feeds using CSS or XSL. While it's possible to do so, the issue still remains open; I strongly recommend that you avoid transforming until this issue has been settled.

Picking Your RSS Flavor

The first question when considering an RSS implementation is what flavor of RSS you want to support. There are currently two leading standards: RSS 1.0 and RSS 2.0.

If integration with the RDF framework is your goal, use RSS 1.0. Otherwise, I recommend using RSS 2.0, which is generally much easier to implement.

Implementing RSS 1.0

Because RSS is an XML language, the first thing in an RSS file is the XML definition:

<?xml version="1.0" encoding="UTF-8"?>

Next, we define this document as a Resource Description Framework (RDF) document:

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

The xmlns notation above specifies a particular namespace for any tags starting with the keyword associated with that suffix. For example, any tags starting with <rdf:> should be parsed according to the rules specified in the document located at http://www.w3.org/1999/02/22-rdf-syntax-ns#.


You may have noticed that one XML namespace in the example (http://purl.org/rss/1.0) is not followed by a keyword. This namespace is the one for all RSS 1.0 applications, and we want it to be our default namespace. Therefore, it doesn't need to be associated with any other keyword.

After defining the document, the next thing we need to do is define the channel:

<channel rdf:about="http://www.tnl.net/channels/feeds/rss100/main.xml">

In this channel definition, we use the rdf:about notation, which specifies that the information following rdf:about refers to the resource that's mentioned between the quotes (" ").

In the channel tag, we then define the title, link, and a description as follows:

<channel rdf:about="http://www.tnl.net/channels/feeds/rss100/main.xml">
  <title>TNL.net weblog</title>
  <description>TNL.net daily views</description>

The title tag defines the title of the resource, highlighting the title of the page that this RSS channel is about, and followed by a link tag, which defines the location of this page. It's generally recommended that the title be no longer than 40 characters, with a link no longer than 500 characters. A plain-text description follows, providing a quick summary to describe the channel.

The next section of the channel definition is a table of contents:

  <rdf:li rdf:resource="http://tnl.net/blog/entry/True_Innovation:_HP_Lightscribe" />
  <rdf:li rdf:resource="http://tnl.net/blog/entry/MacWorld_2004:_What_was_NOT_said" />
  <rdf:li rdf:resource="http://tnl.net/blog/entry/2004_Predictions" />

The table of contents starts with <items></items> tags, which contain a list of items. Similarly, the <rdf:Seq></rdf:Seq> tags specify that the included items are a list of resources that will show up in a sequence. Each item in the sequence is listed, along with the URL of the resource that will be described further in the channel. To ensure backward compatibility with previous RSS implementations, it's recommended that no more than 15 items be listed in the table of contents.

After indicating what our channel is about and what items will be listed in the channel, it's time to provide information about the items themselves:

<item rdf:about="http:// tnl.net/blog/entry/True_Innovation:_HP_Lightscribe" >
  <title>True Innovation: HP Lightscribe</title>
  <description>HP showcases innovation with the introduction of Lightscribe. </description>

An item is defined by the <item></item> tag; however, because RSS 1.0 is an RDF syntax, we need to define what the item is about, hence the rdf:about notation. This is then followed by the title of the item, the link at which the item is located, and the description of the item.

After defining each item, the only task that remains is closing the RDF document, finishing off the RSS 1.0 channel.


A full RSS 1.0 feed can be seen here.

Implementing RSS 2.0

Despite its name, RSS 2.0 was not released after RSS 1.0. It was actually released around the same time and, as a result, is not backwardly compatible with RSS 1.0. It is, however, backwardly compatible with RSS 0.91 and 0.90. An RSS 2.0 channel starts and ends with the rss tag and includes the version number:

<?xml version="1.0"?>
<rss version="2.0">

One of the key differences between RSS 1.0 and RSS 2.0 is that RSS 2.0 doesn't see the channel as a separate entity from the items but treats it as a superset of the items. As a result, the channel tag begins right after the rss tag and is the next-to-last tag in an RSS 2.0 document.

Following the channel tag are the title, link, and description of that channel, which are displayed as follows:

<title>TNL.net weblog</title>
<description>TNL.net daily views</description>

These are the only required elements at the top level of the channel. However, a number of optional elements can provide more details about the channel. One of those optional elements is the image tag, which was required in RSS 0.91 and RSS 0.92:

  <title>TNL.net weblog</title>
  <description>TNL.net weblog</description>

The variables defined above include the title of the image, its web location (specified in the url tag) its width and height (used to display the image properly in RSS aggregators), and the image's description.

After the top levels of the channel have been defined, each of the items follows, with its title, link, and description. For example, an item entry might look like this:

  <title>True Innovation: HP Lightscribe</title>
  <description>HP showcases innovation with the introduction of Lightscribe. </description>

This is very similar to the way in which RSS 0.91 and RSS 0.92 implement their item descriptions, but RSS 2.0 provides a number of optional tags that can add great value to your item's data. Two tags in particular are very appreciated by aggregators: guid and pubDate. The guid tag uniquely identifies an item. For example, if a resource is published at a particular URL on one day but is archived at a different URL, the guid provides an aggregator with a way to link into a resource at its constant URL. Similarly, if a resource is edited, RSS aggregators that use the guid tag are smart enough not to redisplay the whole item to a reader. pubDate, which follows RFC 822, can be included in every item and shows up as follows:

<pubDate>Thu, 8 Jan 2004 18:01:18 -0500</pubDate>


A full RSS 2.0 feed can be seen here.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020