Home > Articles > Programming > C#

Like this article? We recommend

Like this article? We recommend

C# and the .NET FrameworkC# and the .NET Framework

Learn More Buy

Like this article? We recommend

Like this article? We recommend

C# and the .NET FrameworkC# and the .NET Framework

Learn More Buy

Understanding the Vampire Bot

When you improvise code, you need to first write down the information changes, which typically isn't a problem if you're familiar with the task or you have a lot of experience to draw upon. But suppose you're writing a program—such as a vampire bot—that you've never written before, and you have no experience with similar programs to draw on. You need some techniques to help you uncover the information changes. Whenever you're writing a program that automatically does some activity that you know how to do manually, one heuristic is to ask yourself, "How do I do this task manually?" In the case of the vampire bot, the question would be "What do I do when I download a number of images from a web page?" Typically, the information changes are implicit in the answer to the question. The form of the information in the changes may be different, but the information itself is often the same.

In our vampire bot, for example, if you were to download images manually from a web page, you would probably open your browser, type the URL of the web page, note the images you want to download, and then download each image to your computer (usually by right-clicking each image, choosing the Save As menu item, and entering a destination location and filename for the image). Based on this description, here's one possible set of information changes:

URL-->WebPage-->ImageList-->Files

But these changes aren't the same ones that your vampire bot uses. The main difference between downloading images manually from a web page and a vampire bot doing it automatically is that the vampire bot can't "see" the web page the same way you can. The vampire bot has to work with the raw HTML. Thus, the information changes for the vampire bot are as follows:

URL-->RawHTML-->ImageList-->Files

These are really the same set of changes as the previous ones—the web page and the raw HTML denote the same information, but in different forms.

Of course, there's still the matter of implementing the changes. Before you sit down and start coding, you need to at least understand the key changes. Every program has at least one change that distinguishes it from other programs. For a vampire bot, the key change is going from the raw HTML to a list of images; in other words,

RawHTML-->ImageList

To understand what we need to do to implement this change, it's helpful to go through an actual example.

Remember, the vampire bot can't see the web page the same way you can. It has to work with the raw HTML. Imagine that your bot has somehow downloaded the raw HTML for the sample web page at this address:

http://www.professorf.com/planets.html

This web page contains the HTML code shown in Listing 2.

Listing 2—HTML Source Code (Raw HTML) for planets.html

<HTML>
<HEAD>
<STYLE>
<!--
TD {font-family:verdana;font-size:9pt;font-weight:bold;color:white}
-->
</STYLE>
</HEAD>
<BODY BGCOLOR=BLACK>
<TABLE>
<TR><TD VALIGN=TOP>Sun  </TD><TD><IMG SRC="planets/sun.gif">  </TD></TR>
<TR><TD VALIGN=TOP>Mercury</TD><TD><IMG SRC="planets/mercury.gif"></TD></TR>
<TR><TD VALIGN=TOP>Venus </TD><TD><IMG SRC="planets/venus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Earth </TD><TD><IMG SRC="planets/earth.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mars  </TD><TD><IMG SRC="planets/mars.gif">  </TD></TR>
<TR><TD VALIGN=TOP>Jupiter</TD><TD><IMG SRC="planets/jupiter.gif"></TD></TR>
<TR><TD VALIGN=TOP>Saturn </TD><TD><IMG SRC="planets/saturn.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Uranus </TD><TD><IMG SRC="planets/uranus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Neptune</TD><TD><IMG SRC="planets/neptune.gif"></TD></TR>
<TR><TD VALIGN=TOP>Pluto </TD><TD><IMG SRC="planets/pluto.gif"> </TD></TR>
</TABLE>
</BODY>
</HTML>

Our vampire bot has to extract the names of all the images, which are highlighted in Listing 3.

Listing 3—The Image Filenames

<HTML>
<HEAD>
<STYLE>
<!--
TD {font-family:verdana;font-size:9pt;font-weight:bold;color:white}
-->
</STYLE>
</HEAD>
<BODY BGCOLOR=BLACK>
<TABLE>
<TR><TD VALIGN=TOP>Sun  </TD><TD><IMG SRC="planets/sun.gif">  </TD></TR>
<TR><TD VALIGN=TOP>Mercury</TD><TD><IMG SRC="planets/mercury.gif"></TD></TR>
<TR><TD VALIGN=TOP>Venus </TD><TD><IMG SRC="planets/venus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Earth </TD><TD><IMG SRC="planets/earth.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mars  </TD><TD><IMG SRC="planets/mars.gif">  </TD></TR>
<TR><TD VALIGN=TOP>Jupiter</TD><TD><IMG SRC="planets/jupiter.gif"></TD></TR>
<TR><TD VALIGN=TOP>Saturn </TD><TD><IMG SRC="planets/saturn.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Uranus </TD><TD><IMG SRC="planets/uranus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Neptune</TD><TD><IMG SRC="planets/neptune.gif"></TD></TR>
<TR><TD VALIGN=TOP>Pluto </TD><TD><IMG SRC="planets/pluto.gif"> </TD></TR>
</TABLE>
</BODY>
</HTML>

Let's tackle the simpler problem of extracting one image, such as planets/sun.gif, from the raw HTML (Listing 4):

Listing 4—One Image Filename

<HTML>
<HEAD>
<STYLE>
<!--
TD {font-family:verdana;font-size:9pt;font-weight:bold;color:white}
-->
</STYLE>
</HEAD>
<BODY BGCOLOR=BLACK>
<TABLE>
<TR><TD VALIGN=TOP>Sun  </TD><TD><IMG SRC="planets/sun.gif">  </TD></TR>
<TR><TD VALIGN=TOP>Mercury</TD><TD><IMG SRC="planets/mercury.gif"></TD></TR>
<TR><TD VALIGN=TOP>Venus </TD><TD><IMG SRC="planets/venus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Earth </TD><TD><IMG SRC="planets/earth.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mars  </TD><TD><IMG SRC="planets/mars.gif">  </TD></TR>
<TR><TD VALIGN=TOP>Jupiter</TD><TD><IMG SRC="planets/jupiter.gif"></TD></TR>
<TR><TD VALIGN=TOP>Saturn </TD><TD><IMG SRC="planets/saturn.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Uranus </TD><TD><IMG SRC="planets/uranus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Neptune</TD><TD><IMG SRC="planets/neptune.gif"></TD></TR>
<TR><TD VALIGN=TOP>Pluto </TD><TD><IMG SRC="planets/pluto.gif"> </TD></TR>
</TABLE>
</BODY>
</HTML>

We'll generalize our findings to extracting all images.

Step 1: Finding a Close Pattern

To extract planets/sun.gif, we first need to find a pattern that gets us close to the image. One good pattern is IMG SRC=, since we know that an image's filename always follows IMG SRC=. Another good pattern is .gif, because we know all the images in this example end in .gif. We'll use .gif as the pattern that gets us close (see Listing 5):

Listing 5—Finding a Close Pattern (patt)

<HTML>
<HEAD>
<STYLE>
<!--
TD {font-family:verdana;font-size:9pt;font-weight:bold;color:white}
-->
</STYLE>
</HEAD>
<BODY BGCOLOR=BLACK>
<TABLE>
<TR><TD VALIGN=TOP>Sun </TD><TD><IMG SRC="planets/sun.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mercury</TD><TD><IMG SRC="planets/mercury.gif"></TD></TR>
<TR><TD VALIGN=TOP>Venus </TD><TD><IMG SRC="planets/venus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Earth </TD><TD><IMG SRC="planets/earth.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mars </TD><TD><IMG SRC="planets/mars.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Jupiter</TD><TD><IMG SRC="planets/jupiter.gif"></TD></TR>
<TR><TD VALIGN=TOP>Saturn </TD><TD><IMG SRC="planets/saturn.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Uranus </TD><TD><IMG SRC="planets/uranus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Neptune</TD><TD><IMG SRC="planets/neptune.gif"></TD></TR>
<TR><TD VALIGN=TOP>Pluto </TD><TD><IMG SRC="planets/pluto.gif"> </TD></TR>
</TABLE>
</BODY>
</HTML>

Assume that we've stored the value of this pattern that gets us close to an image's filename in a string variable named patt. Further assume that patt's position is stored in an integer variable labeled ploc.

NOTE

As a matter of convention, in our code listings we'll depict C# keywords and code related to the Framework Base Classes in bold monospace type. Moreover, we'll depict any code that you can vary in italic monospace; for example, variable names and prompts, to name a few.

Step 2: Finding the Starting Pattern

Given that we've found a pattern that gets us close to the filename, ploc, the second step is to search backward, looking for a pattern that tells us we're at the start of the image's filename. The double quote character (") is a good start-of-the-image pattern (see Listing 6):

Listing 6—Double Quote as Starting Pattern (spat)

<HTML>
<HEAD>
<STYLE>
<!--
TD {font-family:verdana;font-size:9pt;font-weight:bold;color:white}
-->
</STYLE>
</HEAD>
<BODY BGCOLOR=BLACK>
<TABLE>
<TR><TD VALIGN=TOP>Sun </TD><TD><IMG SRC="planets/sun.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mercury</TD><TD><IMG SRC="planets/mercury.gif"></TD></TR>
<TR><TD VALIGN=TOP>Venus </TD><TD><IMG SRC="planets/venus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Earth </TD><TD><IMG SRC="planets/earth.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mars </TD><TD><IMG SRC="planets/mars.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Jupiter</TD><TD><IMG SRC="planets/jupiter.gif"></TD></TR>
<TR><TD VALIGN=TOP>Saturn </TD><TD><IMG SRC="planets/saturn.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Uranus </TD><TD><IMG SRC="planets/uranus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Neptune</TD><TD><IMG SRC="planets/neptune.gif"></TD></TR>
<TR><TD VALIGN=TOP>Pluto </TD><TD><IMG SRC="planets/pluto.gif"> </TD></TR>
</TABLE>
</BODY>
</HTML>

Assume that we've stored the string pattern that tells us we're at the start of the image in a string variable named spat, and the location of spat in an integer variable named sloc. As you'll see later on, there are a number of built-in string functions that you can use to search for string patterns and find their locations.

Step 3: Finding the Ending Pattern

Given that we know where the start of the image is (sloc), the third step is to search forward, looking for a pattern that tells us we're at the end of the image. Again, a double quote character is a good end-of-the-image pattern (see Listing 7):

Listing 7—Double Quote as Ending Pattern (epat)

<HTML>
<HEAD>
<STYLE>
<!--
TD {font-family:verdana;font-size:9pt;font-weight:bold;color:white}
-->
</STYLE>
</HEAD>
<BODY BGCOLOR=BLACK>
<TABLE>
<TR><TD VALIGN=TOP>Sun </TD><TD><IMG SRC="planets/sun.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mercury</TD><TD><IMG SRC="planets/mercury.gif"></TD></TR>
<TR><TD VALIGN=TOP>Venus </TD><TD><IMG SRC="planets/venus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Earth </TD><TD><IMG SRC="planets/earth.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mars </TD><TD><IMG SRC="planets/mars.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Jupiter</TD><TD><IMG SRC="planets/jupiter.gif"></TD></TR>
<TR><TD VALIGN=TOP>Saturn </TD><TD><IMG SRC="planets/saturn.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Uranus </TD><TD><IMG SRC="planets/uranus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Neptune</TD><TD><IMG SRC="planets/neptune.gif"></TD></TR>
<TR><TD VALIGN=TOP>Pluto </TD><TD><IMG SRC="planets/pluto.gif"> </TD></TR>
</TABLE>
</BODY>
</HTML>

Assume that we've stored the value of the pattern signaling the end of the image in a string variable named epat, and the location of epat in an integer variable named eloc.

At this point, we have the starting location of the image's filename (sloc) and the ending location of the image's filename (eloc), and we can extract the name.

Step 4: Extracting the Image Name

To recap, our test image's filename, planets/sun.gif, is bounded by the starting and ending patterns, both of which happen to be double quotes (see Listing 8):

Listing 8—Starting and Ending Patterns

<HTML>
<HEAD>
<STYLE>
<!--
TD {font-family:verdana;font-size:9pt;font-weight:bold;color:white}
-->
</STYLE>
</HEAD>
<BODY BGCOLOR=BLACK>
<TABLE>
<TR><TD VALIGN=TOP>Sun </TD><TD><IMG SRC="planets/sun.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mercury</TD><TD><IMG SRC="planets/mercury.gif"></TD></TR>
<TR><TD VALIGN=TOP>Venus </TD><TD><IMG SRC="planets/venus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Earth </TD><TD><IMG SRC="planets/earth.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mars </TD><TD><IMG SRC="planets/mars.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Jupiter</TD><TD><IMG SRC="planets/jupiter.gif"></TD></TR>
<TR><TD VALIGN=TOP>Saturn </TD><TD><IMG SRC="planets/saturn.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Uranus </TD><TD><IMG SRC="planets/uranus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Neptune</TD><TD><IMG SRC="planets/neptune.gif"></TD></TR>
<TR><TD VALIGN=TOP>Pluto </TD><TD><IMG SRC="planets/pluto.gif"> </TD></TR>
</TABLE>
</BODY>
</HTML>

The locations of these starting and ending patterns are stored in the variables sloc and eloc. The final step is to extract the string between these locations (see Listing 9):

Listing 9—The Filename Between the Starting and Ending Patterns

<HTML>
<HEAD>
<STYLE>
<!--
TD {font-family:verdana;font-size:9pt;font-weight:bold;color:white}
-->
</STYLE>
</HEAD>
<BODY BGCOLOR=BLACK>
<TABLE>
<TR><TD VALIGN=TOP>Sun </TD><TD><IMG SRC="planets/sun.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mercury</TD><TD><IMG SRC="planets/mercury.gif"></TD></TR>
<TR><TD VALIGN=TOP>Venus </TD><TD><IMG SRC="planets/venus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Earth </TD><TD><IMG SRC="planets/earth.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Mars </TD><TD><IMG SRC="planets/mars.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Jupiter</TD><TD><IMG SRC="planets/jupiter.gif"></TD></TR>
<TR><TD VALIGN=TOP>Saturn </TD><TD><IMG SRC="planets/saturn.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Uranus </TD><TD><IMG SRC="planets/uranus.gif"> </TD></TR>
<TR><TD VALIGN=TOP>Neptune</TD><TD><IMG SRC="planets/neptune.gif"></TD></TR>
<TR><TD VALIGN=TOP>Pluto </TD><TD><IMG SRC="planets/pluto.gif"> </TD></TR>
</TABLE>
</BODY>
</HTML>

That string, of course, is the filename of the image we want the vampire bot to download. To generalize these steps to get a list of all the image filenames, we just need to repeat the procedure for each image in the raw HTML, looking for the next image where the last image left off; that is, start looking for the next image after eloc.

To summarize, to implement a vampire bot you need to improvise code over the information changes shown in Listing 10:

Listing 10—Information Changes for a Basic Vampire Bot

URL-->RawHTML-->ImageList-->Files

Listing 10 shows that the vampire bot takes a web page address (URL) as input and gets the HTML source code (RawHTML) at that URL. From the RawHTML it builds a list of image files to download (ImageList). Finally, the bot downloads the list of images into Files on the user's computer.

If possible, you should determine the datatype for the information before you start coding. Listing 11 shows the information changes with datatypes.

Listing 11—Information Changes with Datatypes

string:URL-->string:RawHTML-->ArrayList:ImageList-->Disk:Files

This is a straightforward chart with plenty of latitude for improvising enhancements; for example, downloading various kinds of image types. In the following sections we show you how to code these changes, starting with getting the URL as input.

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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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