Home > Articles > Web Services > XML

An XML and RSS Overview

Learn some basics of an XML document and see how to use an XML variant, RSS, for the Web.

The Extensible Markup Language, commonly called XML, is a markup language for structured documents. A structured document is one that contains various elements, such as images and text, as well as an indication of what that element is. For example, a letter has elements such as address, body, and footer that all have different roles in the document. When there is some indicator on the letter as to what each part of each element does, then there is a structured document. Most documents do have structure, and XML can be used to define that structure in a usable, and standard, way. HTML documents are structured documents because they have elements and tags defining the role of that element.

HTML and XML are not the same, however. HTML has a known set of tags. XML, on the other hand, does not. XML isn't just a way to mark up documents; it is really a meta-language giving developers a way to describe markups. The developers of the XML documents and applications that use them define the tags for the document as well as the relationship between those tags. XML was created to allow developers to use their tags to create structured documents for the Web. Through this chapter you will learn some basics of an XML document and see how to use an XML variant, RSS, for the Web.

Structure of an XML Document

The look of an XML document is very close to that of HTML and should be easy to follow and understand. In Listing 16-1 you will see a simple XML document.

Listing 16-1  Example XML document

<?xml version="1.0"">
<quote>Good night Cleveland, wherever you are!</quote>
<quote>Shoot low, they're riding Shetlands.</quote>

Well, there is nothing too mystical looking in there. The first line declares that this is an XML document as well as the version of XML being used. This line is not obligatory, but it is a good practice to have it and it helps make the document well formed. Next a container is created. The name of the container is "Zappa". Inside of this container, there are two elements that are being tagged as "quote". Finally, the "Zappa" container is closed, containing two quote elements. The preceding example is a very simple one, and XML goes much deeper than what you see there, but it would take a book to show all the aspects (in fact, there are books that do). However, the preceding example shows enough to help you understand the coming examples and quickly get started using XML and its variants.

News Portals with RSS

A few short years ago, Netscape created what could be called the first Web portal. They developed the My News Network,1 or MNN, which gave a facility for its users to get much of the news and search capabilities from their own starting page. Users can choose sites from which they would like to see news summaries and have them displayed. Netscape dubbed these summaries "channels," and that is now the common name. For Netscape channels, the backend server would periodically fetch structured XML documents from contributing sites and update the content of the channels. In order to ensure that all contributors' files were structured in the same way, Netscape developed the RDF Site Summary (RSS) format. This format uses XML and Resource Description Format (RDF)2 to define a markup language for developers to use. The RSS format is not just for Netscape channels anymore. Using the XML::RSS module a programmer can use the same channel files to format data for the Web.

Before we jump into using XML::RSS, let's first cover the RSS format markup language. There is a finite set of tags to use with RSS. The main container for the document is the channel. Within this containter there are a few elements that can be used to define the content. Three main elements are title, link, and description. The channel container can also contain image, textinput, and other containers. Let's take a moment to break down an RSS document.

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN"
<rss version="0.91">

This section is doing three declarations. The first is declaring that this is an XML document, as you saw in the previous section. The second declaration is the DOCTYPE for the document. The third is declaring that this is a RSS document, using version 0.91. Version 0.90 of RSS was introduced by Netscape in 1999, so this is all still very new. Now that we have the type of document we will be creating, the next step is to create it.


This line opens the channel container. Everything up until this containter is closed will be a part of this container. The main container in all RSS documents is channel.

<title>My News</title>
<description>My news, for you!</description>
<copyright>Copyright 2000++, Me</copyright>
<pubDate>Sun May 21 15:43:45 2000</pubDate>
<lastBuildDate>Sun May 21 15:43:45 2000</lastBuildDate>

Here a list of elements is being defined. The three main ones, which are also required, are title, which is the title of the channel; link, which is the location of the Web site for this channel; and description, which is how to describe the channel. The remaining elements listed are optional for inclusion in the document but can provide useful information. We will not go into individual descriptions of them, since the name of each element does a good job of that on its own.

<title>My News</title>

The preceding snippet shows the optional image container. This container will hold information about the image logo for the channel. Again, the simplicity of the RSS format makes each element name self-explanatory for what the element data is used for. The last line of the snippet closes the container.

<title>Man eats cheese, MPEG at 11.</title>

The item container is extremely important, since it defines the content of the channel. This container is required, and there can be multiple item containers per channel. For example, if there were five news stories, there would be five item containers. There are two elements in an item container, and both are required. These elements define the title of the item as well as the link to the full story.

<title>Search My News</title>
<description>Search the Archives</description>

The "textinput" containter will create a text box that people can use to search your site. This container is optional, since some sites may not have search capabilities. If the site does have search capabilities, then this is an excellent way to allow users to search the site from wherever the channel is displayed.


The document ends by closing the channel container and closing the RSS document. This is equivalent to closing an HTML document with </HTML>. That's the entire RSS document. With this document, a Netscape channel can be created3 and you can share it with others around the world who want to customize their Web pages and applications with your information. Now that you know the structure of an RSS document, we will show you how to use that file and then create your own using Perl.

A Home Page News Portal

Now that you have a general understanding what an RSS document is and how one in structured, it is time to see how a developer can use these files to create dynamic content and create a customized portal with them. The easiest way to use RSS formatted files in Perl is with the XML::RSS module, written by Jonathan Eisenzopf. This module allows a programmer to easily get the data that is inside an RSS formatted file in an object-oriented fashion. In this section we will walk through an application that fetches RSS files, displays the channels to a Web page, and allows a user to add channels to fetch and choose what channels are displayed on the Web page.

The first thing to know is where to get channel files to use! The xmlTree Web site4 is attempting to categorize much of the XML content on the Web, and much of this content is RSS files. Using this Web site, you can search for the type of channel you wish you have and find the location of the RSS files5 for those channels. Now that you know where to look for channel files, let's get on with the script.

We begin by creating a table that will hold information about the channels. We will be keeping information on three things: the URL of the RSS file, the name of the channel, and whether the channel is to be viewed on the Web page.

Listing 16-2  SQL to create the RDF table

 URL varchar(250) NOT NULL,
 Name varchar(250) NOT NULL,
 Selected int(11)

To help you use this script as you read along, Listing 16-2 shows the insert statements of four channels. This will also give you an idea of what the data in the table looks like.

INSERT INTO rdf VALUES ('http://slashdot.org/slashdot.rdf',
INSERT INTO rdf VALUES ('http://www.news.perl.org/perl-news-
                        short.rdf','Perl News',1);
INSERT INTO rdf VALUES ('http://freshmeat.net/backend/fm.rdf',
INSERT INTO rdf VALUES ('http://www.securityfocus.com/topnews-
                        rss.html','Security Focus',1);

The first thing that is needed is a way to get the RSS files locally so the XML::RSS module can parse it. To accomplish this, we create the script fetch, which can be run from the command line or via cron at regular intervals.

01: #!/usr/bin/perl -w
02: # fetch
03: use strict;
04: use File::Basename;
05: use DBI;
06: use LWP::Simple qw(mirror);

Lines 1-6 define the path to Perl and use() the needed modules. The mirror() method from LWP::Simple will be used to get the remote RSS files. When the file will be saved locally, they will be saved with the same name of the remote file. The basename() method from File::Basename will be used to easily get that information for us.

07: my $RDF_DIR = './rdf';

Line 7 initializes the $RDF_DIR variable. Its value will be used as the directory to store the retrieved RSS files.

08: my $dbh = DBI->connect("dbi:mysql:book", "user", "password");
09: my $sth = $dbh->prepare(qq{select URL from rdf});
10: $sth->execute or die $DBI::errstr;

Line 8 connects to the database. Line 9 then prepares a query that selects all the URLs for the RSS files from the table. Line 10 executes this statement or dies with the error from DBI.pm.

11: while (my $url = $sth->fetchrow) {
12:     my $name = basename($url);
13:     mirror($url, "./$RDF_DIR/$name");
14: }

Lines 11-14 loop through the results set from the database. The value returned and stored in $url will be a single URL. In line 12 $url is passed to the basename() method, which will return the filename from the end of the URL. This value is stored in $name. Line 13 does the real work. The mirror() method takes the URL as its first argument and in turn fetches the remote Web page. The second argument is the location of where the new file is to be saved. When this loop is done, all the available RSS files will be stored locally. This script would be most helpful if run in intervals to make sure the latest RSS files are local.

15: $dbh->disconnect;

Line 15 closes the database connect.

The next part of the application is to take the RSS files and make them useful. The index.cgi script, to be explained next, will create channel boxes on a Web page displaying the data from the RSS files.

01: #!/usr/bin/perl -wT
02: # index.cgi
03: use strict;
04: use CGI qw(:standard end_ul end_table);
05: use CGI::Carp qw(fatalsToBrowser);
06: use File::Basename;
07: use DBI;
08: use XML::RSS;
09: my $RDF_DIR = './rdf';
10: my $dbh = DBI->connect("dbi:mysql:book", 'user','password') or 
                           print $DBI::errstr;
11: my $sth = $dbh->prepare(qq{select URL from rdf where 
                           Selected = 1});
12: $sth->execute;

Lines 1-12 only introduce one new thing: using XML::RSS. This is the module that will be used to retrieve the wanted information from the RSS files in $RDF_DIR. We are also selecting all the URLs from the database where Selected is 1, which indicates that channel should be displayed on the Web page.

13: print header,
14:       start_html("My Home Page"),
15:       h2("My Favorite Sites");
16: print start_table({cellpadding=>0, cellspacing=>0, border=> 0, 
                 width => '100%'}),
17:       td;

Lines 13-17 start off the HTML for the page. All the HTML is being printed out using methods from the CGI.pm module.

18: my $count = 1;
19: my @html = ('</TD><TD>', '</TD><TR><TD>');

Line 18 and 19 initialize two variables that will be used together as a sort of toggle. The channels will be displayed in two columns, and one way or another we have to know if a <TR> is to be printed to start a new row. Since every other column will have the <TR>, a simple little toggle can be used to switch between the two HTMLs.

20: while (my $url = basename($sth->fetchrow)) {
21:      my $rss = new XML::RSS;

Line 20 starts iterating through the results set, which will be URLs. As the results row is fetched, it is also put through the basename() method to get only the filename. For example, the URL http://slasdhot.org/slashdot.rdf will be reduced to "slashdot.rdf." That filename is then stored in $url. Line 21 then creates a new XML::RSS object. The resulting $rss variable will be an object reference.

22:      eval {$rss->parsefile("$RDF_DIR/$url")};
23:      warn "$url will not parse $@" and next if $@;

Line 22 evaluates the parsefile() method. The parsefile() method takes the location of the RSS file on disk, opens it, and parses it. This is being wrapped in an eval() because if the RSS is broken, an exception may be thrown. By using eval(), the exception can be caught, and the script will continue. Line 23 will print a warning to STDERR and move on to the next iteration of the loop if an exception is caught.

24: my $last_mod = scalar localtime((stat("$RDF_DIR/$url"))[9]);

Line 24 initializes $last_mod with the scalar value of the last modified time of the RSS file.

25:     print start_table({cellpadding=>0, cellspacing=>2, 
                           border=> 5, width=>'75%'}),
26:     td({valign=>'CENTER', bgcolor => '#C0C0C0'});

Lines 25 and 26 begin the HTML table for the channel.

27:    $rss->{image}{url}
28:    ? print img({src=>$rss->{image}{url}})
29:    : print strong($rss->{channel}{title});

Lines 27, 28, and 29 are one line broken up for clarity. Line 27 wants to see if there is a true value for $rss->{image}{url}. If there is, then the RSS file has an image container. If it is true, line 28 then displays that image to the browser. If there is no image container, the title for the channel is displayed instead.

30: print ul;

Line 30 prints the <UL> tag. The items in the RSS file will be displayed as an unordered list.

31: for (@{$rss->{items}}) {
32:        print li(a({href=>$_->{link}}, $_->{title})); 
33: }

Lines 31-33 iterate over the items in the channel container. $rss->{items} is a reference to an array and is being dereferences as such. Line 32 prints out the item to the browser. The item is displayed as a hyperlink to the URL for the story. The text for the hyperlink is the items title. These values come from the link and title elements of the item container.

34: print end_ul;

Line 34 prints the </UL> tag.

35: if ($rss->{textinput}{link}) {
36:        print $rss->{textinput}{description}, 
                 start_form(-method => 'GET',
37:                         -action => $rss->{textinput}{link}),
38:              textfield(-name => $rss->{textinput}{name}),
39:              end_form;
40: }

Lines 35-40 handle an occurrence of a textinput container. If line 35 finds that the link element of the textinput container has a true value, the rest of the block prints the appropriate form.

41:     print qq(Last Updated $last_mod<BR>),
42:        end_table;
43:     $html[$count^=1];
44: } 

Line 41 displays the last modified date that was retrieved in line 24. Line 42 closes the table for the channel, but line 43 does something fun. Remember lines 18 and 19 when we initialized @html and $count so they would act as a toggle? Line 43 is that toggle. We want to have two columns of channels being displayed, and by XORing the values of $count and 1, we can print the desired HTML to either end the table row with a <TR> tag or not. The higher the value to initialize $count with, the more columns you will have. Finally, line 44 ends the while() loop.

45: print end_table,
46:       end_html;

Lines 45 and 46 end the script by printing the closing tags for the main table and the HTML. When this script is run, the Web page that is generated is similar to that shown in Figure 16-1.

Figure 16-1
Channels on a Web page

To this point, the application has a means to fetch updated RSS files and display the channel data to a Web page. However, the application still needs a way to add RSS files to the database, as well as choose which ones to display and which ones not to. To accomplish this, we will show the script admin.cgi.

01: #!/usr/bin/perl -wT
02: # admin.cgi
03: use strict;
04: use CGI qw(:standard);
05: use CGI::Carp qw(fatalsToBrowser);
06: use DBI;
07: my $dbh = DBI->connect("dbi:mysql:book", "user", "password");
08: param('Submit') ? add_new() : show_form();
09: $dbh->disconnect;

Lines 1-9 introduce nothing new. Line 8 is what is really important here. Line 8 checks if there was a "Submit" parameter sent to the script. If there was, this means that the form to make changes was submitted and to call the add_new() subroutine. The add_new() subroutine will make the needed changes to the database, then reshow the form with the show_form() subroutine. If there was no "Submit" parameter sent to the script, the show_form() subroutine is immediately called. Line 9 disconnects from the database.

10: sub show_form {
11:    my $sth = $dbh->prepare(qq{select * from rdf});
12:    $sth->execute;
13:    print header,
14:          start_html("My Home Page Options"),
15:          h2("Choose My Favorite Sites");
16:    print start_form(-method => 'POST', -action => 'admin.cgi');

Lines 9-16 begin the show_form() subroutine. This subroutine will do one thing: display the Web form to the browser. The form will consist of a list of all the channels in the database, each with a checkbox denoting whether it has been selected to be viewable on the main Web page. The page also will have a place to add a new channel by entering the channels' name, URL to the RSS file, and a checkbox to select if the channel should be shown on the main Web page. Figure 16-2 shows what the final form will look like. Line 11 is the query that will select all the information from the database. This data will be used starting in line 17 to display the channels. The other line of note is line 16, which begins the Web form with itself as the script to which the form will be submitted.

17:    while (my $data = $sth->fetchrow_hashref) {
18:         my $checked = $data->{Selected} ? "CHECKED" : "";
19:         print checkbox(-name => 'Selected',
20:                        -checked => $checked,
21:                        -value => $data->{Name},
22:                        -label => $data->{Name},
23:                        ),
24:                 p;
25:    } 

Lines 17-25 are a loop that iterates over the data set returned from the SQL executed on line 12. The data returned is stored in the $data variable, which is a hash reference containing the data for the specific row being returned from the fetchrow_hashref() method. Each channel in the database has a Selected field, which denotes if the channel is to be displayed on the main Web page. This field will either contain a 0 or 1 to not display or display the channel. Line 18 checks to see if the channel is selected or not to determine if the CHECKED attribute of the HTML checkbox input tag should be shown. If $data->{Selected} is a true value, the $checked variable is initialized as the string "CHECKED" and is an empty string if there is a false value. Lines 19-23 display the checkbox for the channel. Passing parameters to the checkbox() method from CGI.pm, we can define the checkbox's name, which will be "Selected," whether or not the checkbox is to be displayed selected, as well as the value and label for the checkbox. The value and label parameters are both defined as the name of the channel, referred to as $data->{Name}. This continues for each of the channels in the database. Line 25 closes the while() block we have been in.

26:    print h2("Add new channel") , p,
27:        "RDFs URL: ", textfield(-name => 'URL', -size => 50), p
28:        "Name of channel: ", textfield(-name => 'Name', 
                                          -size => 50), p
29:        "Display on Home Page: ", 
30:         checkbox(-name => 'new-Selected', -label => ''), p,
31:         submit(-name => 'Submit', -value => 'Make Changes'),
32:         end_form, end_html;
33: }

Lines 26-32 are a long print() to display three form elements that will allow a user to enter a new channel into the database. The first form element, aptly named "URL," is a text box (created with the textfield() method) that will be used to gather the URL of the RSS file. Line 28 creates the second text box, "Name," which is where the user-defined name of the channel is entered. Line 30 is a checkbox, named "new-Slected," where the user can select if the channel is to be displayed or not. You may have noticed that all the form elements except this one is the name of a field in the database. This is to make sure that when the form is submitted, this value doesn't want to get mixed in with the other checkboxes that were selected. The other selected checkboxes will be seen as an array when they are retrieved in the show_form() subroutine, and this value will be separate. Line 31 prints the submit button for the form. A value is defined for the button so the value will have a true value when line 8 checks to see if this form is being submitted for an update or being called directly. Line 32 ends the print() by ending the form and Web page.

34: sub add_new {
35:     my $qry_select = qq(update rdf set Selected = 1 
                            where );
36:     my $qry_deselect = qq(update rdf set Selected = 0 
                            where );

Line 34 begins the add_new() subroutine. Lines 35 and 36 define two variables that are the beginnings of SQL UPDATE statements. When the data is parsed to see what channels were selected, there is no real way to know which ones are not selected. This means that after knowing the selected channels, two queries will be executed. One will update the Selected field of those selected to 1, and those that are not selected will have it set to 0. These queries will be built in lines 39 and 40.

37:     my @selected = param('Selected');

Line 37 builds the @selected array by getting all the parameters submitted with the name "Selected." The elements of the @selected array will be the names of the channels the user checked to be viewable from the form.

38:     $qry_select .= qq(Name = '$_' or ) for @selected;
39:     $qry_deselect .= qq(Name <> '$_' and ) for @selected;

Lines 38 and 39 build the update statements. Both scalars are concatenated as for() iterates through @selected.

40:     $qry_deselect =~ s! and $!!;
41:     $qry_select =~ s! or $!!;

Lines 40 and 41 clean up the queries being made. At the end of each string, there will be an extra "and" or "or" and they need to be removed before trying to execute them.

42:     my $sth = $dbh->prepare($qry_select);
43:     $sth->execute or print $DBI::errstr;
44:     $sth = $dbh->prepare($qry_deselect);
45:     $sth->execute or print $DBI::errstr;

Lines 42-45 prepare() and execute() the queries. When this is done, the database will match what the user wanted as far as what is Selected and what is not.

46:     if (param('URL') && param('Name')) {
47:             my $url = param('URL');
48:             my $name = param('Name');
49:             my $display = param('new-Selected') ? 1 : 0;
50:             $sth = $dbh->prepare(qq{insert into rdf (URL, NAME,
                   SELECTED) values ('$url', '$name', $display)});
51:             $sth->execute or print $DBI::errstr;
52:     }
53:     show_form;
54: }

Lines 46-54 complete the script. Line 46 is checking to see if a URL and Name parameter have been passed to the script. Both are checked because we do not want to add a channel with no Name or no URL. If those parameters are true, the block continues and adds a record into the database, thereby creating a new channel. When this is all finished, the show_form() subroutine is called, and the form, with the updated information, is displayed to the screen.

Figure 16-2
Channel admin page

The three scripts explained in this section showed you how to create an RSS file as well as how to parse, read, and display them. The tools taught in this section can be used to provide, or receive other, information in Web applications. There are other features that can be added to this application, which will be suggested reader exercises at the end of this chapter. Using XML is growing in popularity and is an excellent tool for the programmer's toolbox. With the basic techniques taught in this chapter, you can already use Perl and XML to enhance Web applications.


  1. http://my.netscape.com

  2. This is a format used to describe Web-based meta-data.

  3. The RDF file needs to be registered with Netscape so they know where to fetch it.

  4. www.xmltree.com

  5. Many of these have an .rdf extension, although this is not required.


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