Home > Articles > Web Services > XML

Sams Teach Yourself XML in 21 Days

Sep 16, 2005

📄 Contents

␡

⎙ Print

< Back Page 230 of 288 Next >

Recommended Book 

Sams Teach Yourself XML in 21 Days, 3rd Edition

Learn More Buy

Introducing RDF

RDF is an XML-based language that we use to describe various resources in a standard way. We can use it to describe any resource, but it's most often used to describe documents on the Web. This is how the W3C describes RDF:

Resource Description Framework (RDF) is a foundation for processing metadata; it provides interoperability between applications that exchange machine-understandable information on the Web. RDF emphasizes facilities to enable automated processing of Web resources. RDF can be used in a variety of application areas; for example: in resource discovery to provide better search engine capabilities, in cataloging for describing the content and content relationships available at a particular Web site, page, or digital library, by intelligent software agents to facilitate knowledge sharing and exchange, in content rating, in describing collections of pages that represent a single logical "document", for describing intellectual property rights of Web pages, and for expressing the privacy preferences of a user as well as the privacy policies of a Web site. RDF with digital signatures will be key to building the "Web of Trust" for electronic commerce, collaboration, and other applications.

As expected, RDF is a W3C recommendation. You can find an overview page at http://www.w3.org/RDF. The RDF model and syntax specification are at http://www.w3.org/TR/REC-rdf-syntax and the RDF schema specification is at http://www.w3.org/TR/rdf-schema. And you can find an RDF primer at http://www.w3.org/TR/rdf-primer. Here's an overview of some RDF resources that are available:

http://athena.ics.forth.gr:9090/RDF/— A validating RDF parser by ICS-FORTH that is based on Java.
http://lists.w3.org/Archives/Public/www-rdf-interest/2000May/0009.html— An RDF parser by Dan Connolly that uses XSLT.
http://nestroy.wi-inf.uni-essen.de/xwmf— The Extensible Web Modeling Framework (XWMF), which includes an RDF parser.
http://www.w3.org/RDF/Validator— A simple RDF validator on the W3C site.
http://www.w3.org/Library/src/HTRDF— John Punin's RDF parser, which is written in C.
http://www710.univ-lyon1.fr/~champin/rdf-tutorial— An RDF tutorial online. (It's in English, even though the Web page is French.)

No major browser has a lot of built-in RDF support right now. Mozilla, Netscape Navigator's open-source test version, has some RDF support built into it. If you want to learn more, take a look at these documents:

http://www.mozilla.org/rdf/50-words.html— An overview of RDF and how it fits with Mozilla.
http://www.mozilla.org/rdf/doc/faq.html— The RDF Mozilla FAQ, which also includes a little sample code.
http://www.mozilla.org/rdf/doc/datasource-howto.html— A cookbook that shows how to create RDF data sources.
http://www.mozilla.org/rdf/rdf-nglayout.html— A document that describes how to use RDF in Mozilla.
http://www.mozilla.org/rdf/doc/api.html— A technical overview of the Mozilla RDF implementation.
http://www.mozilla.org/rdf/doc/SmartBrowsing.html— A page that describes Mozilla's SmartBrowsing system, which allows third-party metadata servers to provide RDF related-link annotations. SmartBrowsing is one of the first true uses of RDF for indexing Web resources on a large scale.

Internet Explorer lags behind Mozilla, although Microsoft does have an RDF viewer available for free. You can find it at (as of this writing) http://msdn.microsoft.com/downloads/samples/Internet/xml/xml_rdf_viewer/sample.asp. This viewer can read RDF documents and display the data in them—but note that to run the viewer, you need Internet Explorer 5.0 or later, Visual Basic 6.0, and Windows 98, Windows NT 4.0, or Windows 2000.

What do RDF documents look like? Here's an example of an RDF document that describes the stoic philosopher Epictetus as the creator of a certain resource, which, let's say, is to be found at the (fictitious) URI http://www.XMLPowerCorp.com/philosophy.html:

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
    <rdf:Description about="http://www.XMLPowerCorp.com/philosophy.html">
        <Creator>Epictetus</Creator>
    </rdf:Description>
</rdf:RDF>

RDF is a very general language. In fact, the <Creator> element does not exist in standard RDF. However, there are many sublanguages built on RDF, such as one called the Dublin Core. The <Creator> element is part of the Dublin Core, which means that Web search engines that support the Dublin Core know enough to search for <Creator> elements when they want to find a particular Web resource's author.

We'll start working with RDF by seeing what the rules are.

Understanding How RDF Documents Work

In general, RDF documents are made of RDF statements, each of which has three parts, making each statement a triple. Here are the three parts of an RDF statement:

A resource— A resource is typically a Web document that we point to with a URI.
A named property— A named property is a characteristic or an attribute of the resource, such as the resource's creator.
A property value— The property value is the property's content. For example, the value of the <Creator> property is often the name of the resource's creator.

In RDF the resource is called the subject of the statement, the named property is called the predicate of the statement, and the property value is called the object of the statement. In the following simple RDF document:

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
    <rdf:Description about="http://www.XMLPowerCorp.com/philosophy.html">
        <Creator>Epictetus</Creator>
    </rdf:Description>
</rdf:RDF>

the subject is the document http://www.XMLPowerCorp.com/philosophy.html, the predicate is the named property Creator, and the object is the name of the document's creator, Epictetus. We'll take this document apart in detail now.

Creating RDF Root Elements

RDF documents are XML documents, of course, so start each one with an XML declaration. The root element is <RDF>:

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

RDF documents must use the RDF namespace setting, which is "http://www.w3.org/1999/02/22-rdf-syntax-ns#". (The # on the end, which might look odd, is not an error; the idea is that it can help applications create XPointers.) The usual prefix for this namespace is rdf, and you'll use that here:

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

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

           .

           .

           .

   </rdf:RDF>

Creating Description Elements

When you describe a resource, it gets its own <rdf:Description> element. Here are the attributes you can use with this element:

about — Specifies what resource the element describes.
aboutEach — Specifies statements about each of the element's children.
aboutEachPrefix — Specifies RDF container items, by prefix.
bagID — Specifies the ID of an associated bag container.
ID — Gives the element an ID value.
type — Specifies the description's type.

In this example, the resource you are describing is http://www.XMLPowerCorp.com/philosophy.html, so assign that URI to the about attribute of the <rdf:Description> element:

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
    <rdf:Description about="http://www.XMLPowerCorp.com/philosophy.html">

       .

       .

       .

       </rdf:Description>
</rdf:RDF>

To store the actual description of the resource, we use property elements, which are described next.

Creating Property Elements

The <rdf:Description> element contains the elements that contain the actual description. For example, for the document you're describing, you can use a <Creator> element:

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
    <rdf:Description about="http://www.XMLPowerCorp.com/philosophy.html">
        <Creator>Epictetus</Creator>
    </rdf:Description>
</rdf:RDF>

There are no properties, like Creator, built into RDF, per se. We can create whatever properties we like. There are a number of RDF applications already available, however, and the most popular and well supported of these is the Dublin Core. You'll take a look at it next—and it does have a <Creator> element built into it.

Using the Dublin Core

All the details about the Dublin Core are available at http://dublincore.org/. The Dublin Core provides a set of elements for use in RDF, and it is being used in many places—government agencies, libraries, corporations, on the Web. The Dublin Core calls itself a "metadata initiative," and it's a strongly supported concern; you'll find frequent updates to what's going on at its Web site.

The Dublin Core namespace setting is "http://purl.org/DC/" (note that this namespace is usually associated with the prefix dc). You should use this namespace setting if you're going to use the Dublin Core. Here's how that looks in our RDF example:

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:dc="http://purl.org/DC/">
    <rdf:Description about="http://www.XMLPowerCorp.com/philosophy.html">
        <dc:Creator>Epictetus</dc:Creator>
    </rdf:Description>
</rdf:RDF>

Besides <Creator>, there are plenty of other elements in the Dublin Core, as listed in Table 18.1.

Table 18.1. The Dublin Core Elements

Element	What It Means
`Contributor`	A person or an organization that has contributed to this resource.
`Coverage`	The extent or scope of the resource.
`Creator`	Usually refers to the resource's author.
`Date`	A date connected to the resource, such as its last update or its creation date. It uses the YYYY-MM-DD format.
`Description`	A description of the resource.
`Format`	The format used for the resource. It is usually a MIME type.
`Identifier`	An ID value for the resource in its context.
`Language`	The language of the resource. It uses values defined by RFC 1766 and includes a two-letter language code with an optional two-letter country code (from the ISO 3166 standard), such as `"en-us"`.
`Publisher`	The entity responsible for the resource.
`Relation`	A reference to a related resource or relationship type.
`Rights`	Rights information for the resource.
`Source`	The source from which the current resource is derived.
`Subject`	The topic of the content of the resource.
`Title`	A name given to the resource.
`Type`	The content type of the resource.

Also, each of the Dublin Core elements has 10 attributes:

Comment — Provides a comment about the use of the data in the element.
Datatype — Specifies the type of data in the element.
Definition — Defines the concept behind the data in the element.
Identifier — Specifies a unique identifier assigned to the element that identifies it.
Language — Specifies the language of the data in the element.
Maximum Occurrence — Puts a limit on how many times the element may occur.
Name — Specifies the name assigned to the data element.
Obligation — Specifies whether the element is required.
Registration Authority — Refers to the agency or group authorized to register the element.
Version — Specifies the version of the element.

Six of these attributes have fixed values:

Version — 1.1
Registration Authority — Dublin Core Metadata Initiative
Language — en (that is, English)
Obligation — Optional
Datatype — Character String
Maximum Occurrence — Unlimited

In addition, the Dublin Core also lists a set of default resource types that we can use with the <Type> element:

collection
dataset
event
image
interactive resource
model
party
physical object
place
service
software
sound
text

Up to this point, you've only used one property, Creator, to describe the resource, but you can use multiple resources at the same time. For example, Listing 18.7 shows an example of an RDF document that uses multiple properties to describe a single resource.

Example 18.7. An RDF Example (`ch18_07.rdf`)

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:dc="http://purl.org/DC/">

    <rdf:Description about="http://www.XMLPowerCorp.com/philosophy.html">
        <dc:Creator>Epictetus</dc:Creator>

           <dc:Description>The stoic philosopher's teachings</dc:Description>

           <dc:Title>The Discourses</dc:Title>

           <dc:Type>text</dc:Type>
    </rdf:Description>

</rdf:RDF>

Working with Multiple Resources

Besides using multiple properties for each description, you can also use one single RDF document to describe multiple resources; in this case, each description has its own <rdf:Description> element. Listing 18.8 shows an example that describes various chapters from Book III of Epictetus' Discourses.

Example 18.8. An RDF Example That Describes Multiple Resources (`ch18_08.rdf`)

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:dc="http://purl.org/DC/">

    <rdf:Description about="http://www.XMLPowerCorp.com/chapter1.html">

           <dc:Creator>Epictetus</dc:Creator>

           <dc:Language>en</dc:Language>

           <dc:Title>Of personal adornment</dc:Title>

           <dc:Type>text</dc:Type>

       </rdf:Description>


       <rdf:Description about="http://www.XMLPowerCorp.com/chapter2.html">

           <dc:Creator>Epictetus</dc:Creator>

           <dc:Language>en</dc:Language>

           <dc:Title>The fields of study</dc:Title>

           <dc:Type>text</dc:Type>

       </rdf:Description>


       <rdf:Description about="http://www.XMLPowerCorp.com/chapter3.html">

           <dc:Creator>Epictetus</dc:Creator>

           <dc:Language>en</dc:Language>

           <dc:Title>What is the subject-matter?</dc:Title>

           <dc:Type>text</dc:Type>
    </rdf:Description>

</rdf:RDF>

We can also nest RDF descriptions. For example, if we want to describe three chapters of Epitectus' Book III by using nested RDF, we just have to nest <rdf:Resource> elements appropriately. Listing 18.9 shows how this works.

Example 18.9. A Nested RDF Example (`ch18_09.rdf`)

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:dc="http://www.purl.org/DC/">

    <rdf:Description about="http://www.XMLPowerCorp.com/bookIII.html">

           <dc:Title>Book III</dc:Title>

           <dc:Creator>Epictetus</dc:Creator>

           <rdf:Description about="http://www.XMLPowerCorp.com/chapter1.html">

               <dc:Creator>Epictetus</dc:Creator>

               <dc:Language>en</dc:Language>

               <dc:Title>Of personal adornment</dc:Title>

               <dc:Type>text</dc:Type>

           </rdf:Description>


           <rdf:Description about="http://www.XMLPowerCorp.com/chapter2.html">

               <dc:Creator>Epictetus</dc:Creator>

               <dc:Language>en</dc:Language>

               <dc:Title>The fields of study</dc:Title>

               <dc:Type>text</dc:Type>

           </rdf:Description>


           <rdf:Description about="http://www.XMLPowerCorp.com/chapter3.html">

               <dc:Creator>Epictetus</dc:Creator>

               <dc:Language>en</dc:Language>

               <dc:Title>What is the subject-matter?</dc:Title>

               <dc:Type>text</dc:Type>

           </rdf:Description>

       </rdf:Description>
</rdf:RDF>

Using Resource Attributes

In RDF, there's another valid way of referring to a resource that a property describes: using the rdf:resource attribute. Listing 18.10 shows an example that uses this attribute to tie various RDF elements to the resources they describe.

Example 18.10. An RDF Resource Attribute Example (`ch18_10.rdf`)

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:dc="http://www.purl.org/DC/">

    <rdf:Description about="http://www.XMLPowerCorp.com/chapter1.html">
        <dc:Title>Chapter 1</dc:Title>
        <dc:Creator rdf:resource="http://www.XMLPowerCorp.com/epictetus.html"/>
    </rdf:Description>

    <rdf:Description about="http://www.XMLPowerCorp.com/chapter2.html">
        <dc:Title>Chapter 2</dc:Title>
        <dc:Creator rdf:resource="http://www.XMLPowerCorp.com/epictetus.html"/>
    </rdf:Description>

    <rdf:Description about="http://www.XMLPowerCorp.com/chapter3.html">
        <dc:Title>Chapter 3</dc:Title>
        <dc:Creator rdf:resource="http://www.XMLPowerCorp.com/epictetus.html"/>
    </rdf:Description>

</rdf:RDF>

Using the rdf:resource attribute is a shortcut way to connect a resource to an RDF that makes such a connection easy to implement.

Using XML in RDF Elements

It's not uncommon to use XML inside RDF elements to store data. Unfortunately, although we can set the Type property to "text", there is no official "xml" setting for this property. Instead, we can set up our software to treat the XML data as XML. As far as RDF is concerned, we can set the parseType attribute of the property to "Literal", as shown in Listing 18.11.

Example 18.11. A Nested RDF Example (`ch18_11.rdf`)

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:dc="http://www.purl.org/DC/"
    xmlns:nsp="http://www.XMLPowerCorp.com/namespace/">

    <rdf:Description about="http://www.XMLPowerCorp.com/philosophy.html">
        <dc:Creator parseType="Literal">

               <nsp:name>Epictetus</nsp:name>

               <nsp:occupation>Philosopher</nmp:occupation>

               <nsp:type>Stoic</nsp:type>

               <nsp:locale>Italy</nsp:locale>

           </dc:Creator>
    </rdf:Description>

</rdf:RDF>

Another way of doing this is to use the Dublin Core <Format> element and use an XML MIME type, like this:

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:dc="http://www.purl.org/DC/"
    xmlns:nsp="http://www.XMLPowerCorp.com/namespace/">

    <rdf:Description about="http://www.XMLPowerCorp.com/philosophy.html">
        <dc:Format>application/xml</dc:Format>
        <dc:Creator parseType="Literal">
            <nsp:name>Epictetus</nsp:name>
            <nsp:occupation>Philosopher</nmp:occupation>
            <nsp:type>Stoic</nsp:type>
            <nsp:locale>Italy</nsp:locale>
        </dc:Creator>
    </rdf:Description>

</rdf:RDF>

Using Abbreviated RDF

There's also an abbreviated RDF syntax that can make writing RDF documents easier. When we abbreviate RDF, we just change property elements into attributes of the <rdf:Description> element. Say, for example, that you have this RDF document:

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:dc="http://purl.org/DC/">

    <rdf:Description about="http://www.XMLPowerCorp.com/chapter1.html">
        <dc:Creator>Epictetus</dc:Creator>
        <dc:Language>en</dc:Language>
        <dc:Title>Chapter 1</dc:Title>
        <dc:Type>text</dc:Type>
    </rdf:Description>

    <rdf:Description about="http://www.XMLPowerCorp.com/chapter2.html">
        <dc:Creator>Epictetus</dc:Creator>
        <dc:Language>en</dc:Language>
        <dc:Title>Chapter 2</dc:Title>
        <dc:Type>text</dc:Type>
    </rdf:Description>
    .
    .
    .

You could abbreviate the RDF this way:

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:dc="http://purl.org/DC/">

    <rdf:Description about="http://www.XMLPowerCorp.com/chapter1.html">

           dc:Creator = "Epictetus"

           dc:Language = "en"

           dc:Title = "Chapter 1"

           dc:Type = "text">

       </rdf:Description>


       <rdf:Description about="http://www.XMLPowerCorp.com/chapter2.html">

           dc:Creator = "Epictetus">

           dc:Language = "en"

           dc:Title = "Chapter 2"

           dc:Type = "text">

       </rdf:Description>
    .
    .
    .

This type of abbreviating can be especially useful with RDF that is embedded in an HTML document because HTML browsers convert elements they don't understand into simple text. If we want to hide RDF data, we can put that data into attributes, not RDF elements, because the data in the attributes won't be shown.

< Back Page 230 of 288 Next >

🔖 Save To Your Account

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.

Privacy Notice

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

Email Address