Home > Articles > Web Services > XML

📄 Contents

  1. Sams Teach Yourself XML in 21 Days, Third Edition
  2. Table of Contents
  3. About the Author
  4. Acknowledgments
  5. We Want to Hear from You!
  6. Introduction
  7. Part I: At a Glance
  8. Day 1. Welcome to XML
  9. All About Markup Languages
  10. All About XML
  11. Looking at XML in a Browser
  12. Working with XML Data Yourself
  13. Structuring Your Data
  14. Creating Well-Formed XML Documents
  15. Creating Valid XML Documents
  16. How XML Is Used in the Real World
  17. Online XML Resources
  18. Summary
  19. Q&A
  20. Workshop
  21. Day 2. Creating XML Documents
  22. Choosing an XML Editor
  23. Using XML Browsers
  24. Using XML Validators
  25. Creating XML Documents Piece by Piece
  26. Creating Prologs
  27. Creating an XML Declaration
  28. Creating XML Comments
  29. Creating Processing Instructions
  30. Creating Tags and Elements
  31. Creating CDATA Sections
  32. Handling Entities
  33. Summary
  34. Q&A
  35. Workshop
  36. Day 3. Creating Well-Formed XML Documents
  37. What Makes an XML Document Well-Formed?
  38. Creating an Example XML Document
  39. Understanding the Well-Formedness Constraints
  40. Using XML Namespaces
  41. Understanding XML Infosets
  42. Understanding Canonical XML
  43. Summary
  44. Q&A
  45. Workshop
  46. Day 4. Creating Valid XML Documents: DTDs
  47. All About DTDs
  48. Validating a Document by Using a DTD
  49. Creating Element Content Models
  50. Commenting a DTD
  51. Supporting External DTDs
  52. Handling Namespaces in DTDs
  53. Summary
  54. Q&A
  55. Workshop
  56. Declaring Attributes in DTDs
  57. Day 5. Handling Attributes and Entities in DTDs
  58. Specifying Default Values
  59. Specifying Attribute Types
  60. Handling Entities
  61. Summary
  62. Q&A
  63. Workshop
  64. Day 6. Creating Valid XML Documents: XML Schemas
  65. Using XML Schema Tools
  66. Creating XML Schemas
  67. Dissecting an XML Schema
  68. The Built-in XML Schema Elements
  69. Creating Elements and Types
  70. Specifying a Number of Elements
  71. Specifying Element Default Values
  72. Creating Attributes
  73. Summary
  74. Q&A
  75. Workshop
  76. Day 7. Creating Types in XML Schemas
  77. Restricting Simple Types by Using XML Schema Facets
  78. Creating XML Schema Choices
  79. Using Anonymous Type Definitions
  80. Declaring Empty Elements
  81. Declaring Mixed-Content Elements
  82. Grouping Elements Together
  83. Grouping Attributes Together
  84. Declaring all Groups
  85. Handling Namespaces in Schemas
  86. Annotating an XML Schema
  87. Summary
  88. Q&A
  89. Workshop
  90. Part I. In Review
  91. Well-Formed Documents
  92. Valid Documents
  93. Part II: At a Glance
  94. Day 8. Formatting XML by Using Cascading Style Sheets
  95. Our Sample XML Document
  96. Introducing CSS
  97. Connecting CSS Style Sheets and XML Documents
  98. Creating Style Sheet Selectors
  99. Using Inline Styles
  100. Creating Style Rule Specifications in Style Sheets
  101. Summary
  102. Q&A
  103. Workshop
  104. Day 9. Formatting XML by Using XSLT
  105. Introducing XSLT
  106. Transforming XML by Using XSLT
  107. Writing XSLT Style Sheets
  108. Using <xsl:apply-templates>
  109. Using <xsl:value-of> and <xsl:for-each>
  110. Matching Nodes by Using the match Attribute
  111. Working with the select Attribute and XPath
  112. Using <xsl:copy>
  113. Using <xsl:if>
  114. Using <xsl:choose>
  115. Specifying the Output Document Type
  116. Summary
  117. Q&A
  118. Workshop
  119. Day 10. Working with XSL Formatting Objects
  120. Introducing XSL-FO
  121. Using XSL-FO
  122. Using XSL Formatting Objects and Properties
  123. Building an XSL-FO Document
  124. Handling Inline Formatting
  125. Formatting Lists
  126. Formatting Tables
  127. Summary
  128. Q&A
  129. Workshop
  130. Part II. In Review
  131. Using CSS
  132. Using XSLT
  133. Using XSL-FO
  134. Part III: At a Glance
  135. Day 11. Extending HTML with XHTML
  136. Why XHTML?
  137. Writing XHTML Documents
  138. Validating XHTML Documents
  139. The Basic XHTML Elements
  140. Organizing Text
  141. Formatting Text
  142. Selecting Fonts: <font>
  143. Comments: <!-->
  144. Summary
  145. Q&A
  146. Workshop
  147. Day 12. Putting XHTML to Work
  148. Creating Hyperlinks: <a>
  149. Linking to Other Documents: <link>
  150. Handling Images: <img>
  151. Creating Frame Documents: <frameset>
  152. Creating Frames: <frame>
  153. Creating Embedded Style Sheets: <style>
  154. Formatting Tables: <table>
  155. Creating Table Rows: <tr>
  156. Formatting Table Headers: <th>
  157. Formatting Table Data: <td>
  158. Extending XHTML
  159. Summary
  160. Q&A
  161. Workshop
  162. Day 13. Creating Graphics and Multimedia: SVG and SMIL
  163. Introducing SVG
  164. Creating an SVG Document
  165. Creating Rectangles
  166. Adobe's SVG Viewer
  167. Using CSS Styles
  168. Creating Circles
  169. Creating Ellipses
  170. Creating Lines
  171. Creating Polylines
  172. Creating Polygons
  173. Creating Text
  174. Creating Gradients
  175. Creating Paths
  176. Creating Text Paths
  177. Creating Groups and Transformations
  178. Creating Animation
  179. Creating Links
  180. Creating Scripts
  181. Embedding SVG in HTML
  182. Introducing SMIL
  183. Summary
  184. Q&A
  185. Workshop
  186. Day 14. Handling XLinks, XPointers, and XForms
  187. Introducing XLinks
  188. Beyond Simple XLinks
  189. Introducing XPointers
  190. Introducing XBase
  191. Introducing XForms
  192. Summary
  193. Workshop
  194. Part III. In Review
  195. Part IV: At a Glance
  196. Day 15. Using JavaScript and XML
  197. Introducing the W3C DOM
  198. Introducing the DOM Objects
  199. Working with the XML DOM in JavaScript
  200. Searching for Elements by Name
  201. Reading Attribute Values
  202. Getting All XML Data from a Document
  203. Validating XML Documents by Using DTDs
  204. Summary
  205. Q&A
  206. Workshop
  207. Day 16. Using Java and .NET: DOM
  208. Using Java to Read XML Data
  209. Finding Elements by Name
  210. Creating an XML Browser by Using Java
  211. Navigating Through XML Documents
  212. Writing XML by Using Java
  213. Summary
  214. Q&A
  215. Workshop
  216. Day 17. Using Java and .NET: SAX
  217. An Overview of SAX
  218. Using SAX
  219. Using SAX to Find Elements by Name
  220. Creating an XML Browser by Using Java and SAX
  221. Navigating Through XML Documents by Using SAX
  222. Writing XML by Using Java and SAX
  223. Summary
  224. Q&A
  225. Workshop
  226. Day 18. Working with SOAP and RDF
  227. Introducing SOAP
  228. A SOAP Example in .NET
  229. A SOAP Example in Java
  230. Introducing RDF
  231. Summary
  232. Q&A
  233. Workshop
  234. Part IV. In Review
  235. Part V: At a Glance
  236. Day 19. Handling XML Data Binding
  237. Introducing DSOs
  238. Binding HTML Elements to HTML Data
  239. Binding HTML Elements to XML Data
  240. Binding HTML Tables to XML Data
  241. Accessing Individual Data Fields
  242. Binding HTML Elements to XML Data by Using the XML DSO
  243. Binding HTML Tables to XML Data by Using the XML DSO
  244. Searching XML Data by Using a DSO and JavaScript
  245. Handling Hierarchical XML Data
  246. Summary
  247. Q&A
  248. Workshop
  249. Day 20. Working with XML and Databases
  250. XML, Databases, and ASP
  251. Storing Databases as XML
  252. Using XPath with a Database
  253. Introducing XQuery
  254. Summary
  255. Q&A
  256. Workshop
  257. Day 21. Handling XML in .NET
  258. Creating and Editing an XML Document in .NET
  259. From XML to Databases and Back
  260. Reading and Writing XML in .NET Code
  261. Using XML Controls to Display Formatted XML
  262. Creating XML Web Services
  263. Summary
  264. Q&A
  265. Workshop
  266. Part V. In Review
  267. Appendix A. Quiz Answers
  268. Quiz Answers for Day 1
  269. Quiz Answers for Day 2
  270. Quiz Answers for Day 3
  271. Quiz Answers for Day 4
  272. Quiz Answers for Day 5
  273. Quiz Answers for Day 6
  274. Quiz Answers for Day 7
  275. Quiz Answers for Day 8
  276. Quiz Answers for Day 9
  277. Quiz Answers for Day 10
  278. Quiz Answers for Day 11
  279. Quiz Answers for Day 12
  280. Quiz Answers for Day 13
  281. Quiz Answers for Day 14
  282. Quiz Answers for Day 15
  283. Quiz Answers for Day 16
  284. Quiz Answers for Day 17
  285. Quiz Answers for Day 18
  286. Quiz Answers for Day 19
  287. Quiz Answers for Day 20
  288. Quiz Answers for Day 21
Recommended Book

Creating XML Web Services

The last .NET XML topic we'll take a look at today are XML Web services. These services let you provide accessible services on the Web, and they can be used by other applications.

For example, say you were in the field and wanted to retrieve data from a database back at the central office. A Web service can help you do that, as long as the Web server the service is on has access to that database. All you have to do is connect to the Web service from a laptop, and you can get all the data you want. Even a Windows application can call the methods you put into a Web service, allowing you to integrate Web access into Windows applications easily. Web services are often used to implement multitiered, distributed data applications, and in the following sections we'll create a Web service much like that. All the data in this example will be passed back and forth by using XML.

Creating a Web Service

Our sample XML Web service is called ch21_06, and we'll use it to gain access to the authors table in the SQL pubs sample database. In particular, we'll implement two methods in this Web service—GetAuthors, to return a dataset that holds the authors table, and UpdateAuthors, to update that table in the pubs database when needed. Our XML Web service will be on the Web, so if a Windows application needs that data, it can just use our Windows service.

You can create a new Web service project by selecting File, New, Project, selecting the ASP.NET Web Service icon, making the project a Visual Basic .NET project, and giving this project the name ch21_06. When you click the OK button in the New Project dialog box, the new Web service project shown in Figure 21.20 is created.

21fig20.jpg

Figure 21.20 Creating a new Web service project.

The Visual Basic .NET code file for your new Web service is Service1.asmx.vb, and the name of your new Web service is Service1. When you open Service1.asmx.vb in Visual Studio .NET, you see that this new service is derived from the WebService class:

Imports System.Web.Services

<System.Web.Services.WebService(Namespace :=
    "http://tempuri.org/ch21_06/Service1")> _
Public Class Service1
    Inherits System.Web.Services.WebService
        .
        .
        .

In this Web service, we'll set up our connection to the authors table in the pubs sample SQL Server database. To do that, drag an OleDbDataAdapter data adapter to the Web service designer and use the Data Adapter Configuration Wizard to connect the data adapter to the authors table, as you did earlier today for the employee table. Then select Data, Generate Dataset to create a new dataset class, DataSet1. This is the dataset class you'll use to access the authors table in the Web service.

To make the methods in a Web service accessible outside the service, you use the <WebMethod()> attribute when declaring those methods. For example, here is how you do this for the GetAuthors method:


   <WebMethod(Description:="Sends the authors table to the client")> _
Public Function GetAuthors() As DataSet1
        .
        .
        .
End Function

In the GetAuthors method, you want to return a dataset filled with the authors table, so add this code in Service1.asmx.vb:

<WebMethod(Description:="Sends the authors table to the client")> _
Public Function GetAuthors() As DataSet1
    Dim AuthorsDataTable As New DataSet1

       OleDbDataAdapter1.Fill(AuthorsDataTable)

       Return AuthorsDataTable
End Function

As you're going to see, the GetAuthors method will be available to code in other applications after you've added a Web reference to the Web service in those applications.

You can also implement the UpdateAuthors method, which will update the authors table with changes the user has made. We can pass this method to a dataset that holds changes to the authors table and update the authors table by using the data adapter's Update method, like this:

<WebMethod(Description:="Updates the authors table from the client")> _
Public Function UpdateAuthors(ByVal _
    ChangedAuthorsRecords As DataSet1) As DataSet1

       If (ChangedAuthorsRecords Is Nothing) Then

           Return Nothing

       Else

           OleDbDataAdapter1.Update(ChangedAuthorsRecords)

           Return ChangedAuthorsRecords

       End If
End Function

We have now implemented the GetAuthors and UpdateAuthors methods. To make this Web service available to applications, you should build the service now by selecting Build, Build ch21_06. Listing 21.5 shows the code we've developed so far for this example.

Example 21.5. An XML Web Service (from Service1.asmx.vb, ch21_06 Project)

Imports System.Web.Services
        .
        .
        .
    <WebMethod(Description:="Sends the authors table to the client")> _
    Public Function GetAuthors() As DataSet1
        Dim AuthorsDataTable As New DataSet1
        OleDbDataAdapter1.Fill(AuthorsDataTable)
        Return AuthorsDataTable
    End Function

    <WebMethod(Description:="Updates the authors table from the client")> _
Public Function UpdateAuthors(ByVal _
    ChangedAuthorsRecords As DataSet1) As DataSet1
        If (ChangedAuthorsRecords Is Nothing) Then
            Return Nothing
        Else
            OleDbDataAdapter1.Update(ChangedAuthorsRecords)
            Return ChangedAuthorsRecords
        End If
    End Function

End Class

Using a Web Service

Now we'll put our new Web service to work and call it from a Windows application. To make that work, add a new Windows project that will connect to the Web service by selecting File, Add Project, New Project.

In the Add New Project dialog box, select the Windows Application icon, name this new Windows application ch21_07, and click OK. The Windows application opens, as shown in Figure 21.21. Because the Web service has no visual interface, you need to make this Windows application the startup project by selecting Project, Set as StartUp Project. Now when you select Debug, Start, the Windows application will appear.

21fig21.jpg

Figure 21.21 The ch21_07 Windows application.

We want to call the GetAuthors and UpdateAuthors methods in our Windows application. To do that, we need to add a Web reference to our Web service. To do this, right-click the ch21_07 entry in the Solution Explorer at the right in Visual Studio, and then select the Add Web Reference menu item. This opens the Add Web Reference dialog box, which lists the available Web service locations.

To add a reference to a Web service, you can enter the URL for the service's .vsdisco (Visual Studio discovery) file in the Address box in the Add Web Reference dialog box. Or you can browse to the service you want to use by clicking the link in the Add Web Reference dialog box for a server and then click the name of the service you want to use (in this case, Service1).

Either technique opens your Web service's entry in the Add Web Reference dialog box, as shown in Figure 21.22. To add a reference to this Web service to your Windows application, click the Add Reference button.

21fig22.gif

Figure 21.22 The Add Web Reference dialog box.

The Web reference is added to our Windows application, and this reference will give us access to the GetAuthors and UpdateAuthors methods. To hold the data returned from the Web service, add a data grid to the Windows application and place above the data grid two buttons with the captions Get the Data and Set the Data.

Next, drag a dataset object—not a data adapter this time—from the Data tab of the toolbox to the main form in the Windows application. When you do, the Add Dataset dialog box opens, as shown in Figure 21.23. In that dialog box, select the dataset object in your Web service, DataSet1, from the drop-down list (the fully qualified name of DataSet1 is ch21_07.localhost.DataSet1, as shown in Figure 21.23).

21fig23.jpg

Figure 21.23 Using the Add Dataset dialog box.

To create the new dataset we'll use in our Windows application, DataSet11, click the OK button in the Add Dataset dialog box. We'll bind DataSet11 to the data grid in the Windows application, so set the data grid's DataSource property to DataSet11 and its DataMember property to authors in the properties window.

You're almost done. When you click the Get the Data button, the dataset, DataSet11, should fill with data sent to us from the Web service. To do that, you create an object, service, of your Web service class:

Private Sub Button1_Click(ByVal sender As System.Object, _
    ByVal e As System.EventArgs) Handles Button1.Click
    Dim service As New ch21_07.localhost.Service1
        .
        .
        .
End Sub

The service object will let us use the methods we've built into our Web service. We can fill the Windows application's DataSet11 object with the dataset returned from the Web service's GetAuthors method by using the Merge method, like this:

Private Sub Button1_Click(ByVal sender As System.Object, _
    ByVal e As System.EventArgs) Handles Button1.Click
    Dim service As New ch21_07.localhost.Service1
    DataSet11.Merge(service.GetAuthors())
End Sub

That's all it takes—you create an object corresponding to the Web service, and then you can use that object's methods and access the Web service in your code.

We can update the authors table as needed. When the user edits the data in the data grid, those changes are also made to the DataSet11 object. To extract the changed records from that dataset, we can use the dataset's GetChanges method, like this:

Private Sub Button2_Click(ByVal sender As System.Object, _
    ByVal e As System.EventArgs) Handles Button2.Click
    If DataSet11.HasChanges() Then
        Dim dsUpdates As New _

               Ch21_07.localhost.DataSet1

           dsUpdates.Merge(DataSet11.GetChanges())
        .
        .
        .
    End If
End Sub

Now we can use the Web service's UpdateAuthors method to update the authors table in the pubs database. That method returns the changed records, and we can merge them into the Windows application's dataset so those records will no longer be marked as changed:

Private Sub Button2_Click(ByVal sender As System.Object, _
    ByVal e As System.EventArgs) Handles Button2.Click
    If DataSet11.HasChanges() Then
        Dim service As New Ch21_07.localhost.Service1
        Dim dsUpdates As New _
            Ch21_07.localhost.DataSet1
        dsUpdates.Merge(DataSet11.GetChanges())
        DataSet11.Merge(service.UpdateAuthors(dsUpdates) )
    End If
End Sub

The complete code for this example is shown in Listing 21.6.

Example 21.6. Using an XML Web Service (from Form1.vb, ch21_07 Project)

Public Class Form1
    Inherits System.Windows.Forms.Form
        .
        .
        .
    Private Sub Button1_Click(ByVal sender As System.Object, _
        ByVal e As System.EventArgs) Handles Button1.Click
        Dim service As New ch21_07.localhost.Service1
        DataSet11.Merge(service.GetAuthors())
    End Sub

    Private Sub Button2_Click(ByVal sender As System.Object, _
        ByVal e As System.EventArgs) Handles Button2.Click
        Dim service As New ch21_07.localhost.Service1
        Dim dsUpdates As New _
            ch21_07.localhost.DataSet1
        dsUpdates.Merge(DataSet11.GetChanges())
        DataSet11.Merge(service.UpdateAuthors(dsUpdates))
    End Sub
End Class

When you run this example and click the Get the Data button, the data from the authors table should appear in the data grid, as shown in Figure 21.24. If you edit the data in the data grid and click the Set the Data button, your edits will be sent back to the authors table in the pubs database.

21fig24.gif

Figure 21.24 Connecting to and using a Web service.

As far as the users are concerned, the connection to the Web is maintained entirely behind-the-scenes; all the users have to do is click buttons. That's how XML Web services work. Behind-the-scenes in this example, all the data was sent back and forth by using XML. All in all, this is a very impressive showing for .NET programming.

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