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

Introducing the DOM Objects

Here's an overview of the W3C DOM Level 1 objects:

  • Document — The document object
  • DocumentFragment — A reference to a fragment of a document
  • DocumentType — A reference to the <!DOCTYPE> element
  • EntityReference — A reference to an entity
  • Element — An element
  • Attr — An attribute
  • ProcessingInstruction — A processing instruction
  • Comment — The content of an XML comment
  • Text — The text content of an element or attribute
  • CDATASection — A CDATA section.
  • Entity — A parsed or unparsed entity in the XML document
  • Notation — A notation
  • Node — A single node in the document tree
  • NodeList — A list of node objects; allows iteration and indexed access operations
  • NamedNodeMap — A collection that allows iteration and access by name to the collection of attributes

That's the official list of objects. However, Microsoft, going its own way as usual, supports the W3C DOM but uses its own names for the programming objects:

  • DOMDocument — The first node of the XML DOM tree
  • XMLDOMNode — A single node in the document tree
  • XMLDOMNodeList — A list of node objects
  • XMLDOMNamedNodeMap — A map of named nodes; supports access by name to a collection of attributes
  • XMLDOMParseError — Data about an error; includes error number, line number, character position, and a text description
  • XMLHttpRequest — An object that supports communication with HTTP servers
  • XTLRuntime — An object that supports methods that you can call from XSL style sheets
  • XMLDOMAttribute — An attribute object
  • XMLDOMCDATASection — A CDATA section object
  • XMLDOMCharacterData — An object that supports methods used for text manipulation
  • XMLDOMComment — A comment
  • XMLDOMDocumentFragment — A document fragment object
  • XMLDOMDocumentType — Data for the document type declaration
  • XMLDOMElement — An element object
  • XMLDOMEntity — A parsed or unparsed entity in the XML document
  • XMLDOMEntityReference — An entity reference node
  • XMLDOMImplementation — An object that supports general DOM methods
  • XMLDOMNotation — A notation
  • XMLDOMProcessingInstruction — A processing instruction
  • XMLDOMText — The text value of an element or attribute

The list of DOM objects is substantial, so the following sections go through some of the highlights you'll need in code, starting with the main object, the DOMDocument object.

Using the DOMDocument Object

In the Microsoft version of the DOM, the DOMDocument object is the main object, and it represents the top node in every document tree. When we're working with the DOM, this is the only object we create directly. Here's how you might create the DOMDocument object in JavaScript:

function readXMLData()
{
    var xmlDocumentObject
    xmlDocumentObject = new ActiveXObject("Microsoft.XMLDOM")
    xmlDocumentObject.load("ch15_01.xml")
                  .
                  .
                  .

The Microsoft.XMLDOM class used here is an early version of Microsoft's XML support, but it's still supported in recent versions of Internet Explorer, which means we can use it as a common denominator in our code. The current version, and the one to use if you can (because it supports the full DOM 1.0 as well as XML schemas), is Microsoft's MSXML version 4.0, which comes with recent versions of Internet Explorer 6. Here's how to use this version:

function readXMLData()
{
    var xmlDocumentObject
    xmlDocumentObject = new ActiveXObject("MSXML2.DOMDocument.4.0")
    xmlDocumentObject.load("ch15_01.xml")
                  .
                  .
                  .

You can also specify earlier versions of the Microsoft.XMLDOM class by using "MSXML2.DOMDocument.2.0" or "MSXML2.DOMDocument.3.0".

Here's an overview of the most significant properties of the DOMDocument object:

  • attributes — Contains the list of attributes for the node. Read-only.
  • childNodes — Contains a node list of the child nodes of nodes that may have children. Read-only.
  • dataType*— Contains the data type for the node. Read/write.
  • definition*— Contains the definition of the node in the DTD or schema. Read-only.
  • doctype — Contains the document type node, which is what specifies the DTD for the document. Read-only.
  • documentElement — Contains the root element of the document. Read/write.
  • firstChild — Contains the first child of the current node. Read-only.
  • lastChild — Contains the last child node of the current node. Read-only.
  • namespaceURI*— Contains the URI of a namespace. Read-only.
  • nextSibling — Contains the next sibling node of the current node. Read-only.
  • nodeName — Contains the qualified name of the element, attribute, or entity reference. Read-only.
  • nodeType — Contains the node type. Read-only.
  • nodeTypedValue*— Contains the node's value. Read/write.
  • nodeTypeString*— Contains the node type, expressed as a string. Read-only.
  • nodeValue — Contains the text of the node. Read/write.
  • ondataavailable*— Sets the event handler for the ondataavailable event. Read/write.
  • onreadystatechange*— Sets the event handler that handles readyState property changes. Read/write.
  • ontransformnode *— Sets the event handler for the ontransformnode event. Read/write.
  • ownerDocument — Contains the root of the document that contains this node. Read-only.
  • parentNode — Contains the parent node of the current node. Read-only.
  • parsed*— Is set to true if this node has been parsed; false otherwise. Read-only.
  • parseError*— Contains information about the most recent parsing error. Read-only.
  • prefix*— Contains the namespace prefix. Read-only.
  • preserveWhiteSpace*— Is set to true if processing should preserve whitespace; false otherwise. Read/write.
  • previousSibling — Contains the previous sibling of this node. Read-only.
  • readyState*— Contains the current browser state of the XML document. Read-only.
  • text*— Contains the text content of the node and its subtrees. Read/write.
  • url*— Contains the URL for the most recently loaded XML document. Read-only.
  • validateOnParse*— Is set to true (the default) if the parser should validate this document on parsing it; false if not. Read/write.
  • xml*— Contains the XML text representation of the node and all of its children. Read-only.

Here is an overview of the significant methods for this object:

  • abort*— Aborts a download.
  • appendChild — Appends a new child as the last child of the current node.
  • cloneNode — Returns a node that is a copy of this node.
  • createAttribute — Returns a new attribute, using the given name.
  • createCDATASection — Returns a CDATA section node that contains the given data.
  • createComment — Returns a comment node.
  • createDocumentFragment — Returns an empty DocumentFragment object.
  • createElement — Returns an element node, using the given name.
  • createEntityReference — Returns a new EntityReference object.
  • createNode*— Returns a node, using the given type, name, and namespace.
  • createProcessingInstruction — Returns a processing instruction node.
  • createTextNode — Returns a text node that contains the given data.
  • getElementsByTagName — Yields a collection of elements that have the given name.
  • hasChildNodes — Returns true if this node has children; false if not.
  • insertBefore — Inserts a child node before the given node.
  • load*— Loads an XML document from the given location.
  • loadXML*— Loads an XML document, using the given string.
  • nodeFromID*— Yields the node whose ID attribute matches the given value.
  • removeChild — Removes the given child node from the list of children.
  • replaceChild — Replaces the given child node with the given new child node.
  • save*— Saves an XML document to the given location.
  • transformNode*— Transforms the node and its children by using the given XSL style sheet.

Using the XMLDOMNode Object

The Microsoft XMLDOMNode object extends the core XML DOM Node object by adding support for data types, namespaces, DTDs, and schemas, as implemented in Internet Explorer. It's the generic object used to handle nodes. Here is an overview of the significant properties of this object:

  • attributes — List of attributes for the node. Read-only.
  • childNodes — List containing the child nodes of the current node. Read-only.
  • dataType*— Contains the data type for this node. Read/write.
  • firstChild — Contains the first child of the current node. Read-only.
  • lastChild — Contains the last child of the current node. Read-only.
  • namespaceURI*— Contains the URI for the namespace. Read-only.
  • nextSibling — Contains the next sibling of this node. Read-only.
  • nodeName — Contains the qualified name for an element, attribute, or entity reference, or a string for other node types. Read-only.
  • nodeType — Contains the node type. Read-only.
  • nodeTypedValue*— Contains the node's value. Read/write.
  • nodeTypeString*— Contains the node type, in string form. Read-only.
  • nodeValue — Contains the text associated with the node. Read/write.
  • ownerDocument — Contains the root of the document. Read-only.
  • parentNode — Contains the parent node. Read-only.
  • parsed*— Returns true if this node has been parsed; false otherwise. Read-only.
  • prefix*— Contains the namespace prefix. Read-only.
  • previousSibling — Contains the previous sibling of this node. Read-only.
  • text*— Contains the text content of the node and its subtrees. Read/write.
  • xml*— Contains the XML representation of the node and its children. Read-only.

Here is an overview of the significant methods for this object:

  • appendChild — Appends a new child as the last child of this node.
  • cloneNode — Creates a new node that is a copy of this node.
  • hasChildNodes — Returns true if this node has children; false otherwise.
  • insertBefore — Inserts a child node before the given node.
  • removeChild — Removes the given child node.
  • replaceChild — Replaces the given child node with the given new child node.
  • transformNode *— Transforms the node and its children by using the given XSL style sheet.

Using the XMLDOMElement Object

The type of node you'll probably work with most often is the element node, which is supported in the Microsoft programming model by the XMLDOMElement object. Here are the significant properties of the XMLDOMElement object:

  • attributes — List of attributes for the node. Read-only.
  • childNodes — Contains a list of the node's children. Read-only.
  • dataType*— Contains the data type for this node. Read/write.
  • firstChild — Contains the first child node of this node. Read-only.
  • lastChild — Contains the last child node of this node. Read-only.
  • namespaceURI*— Contains the URI for the namespace. Read-only.
  • nextSibling — Contains the next sibling of this node. Read-only.
  • nodeName — Contains the qualified name of an element, attribute, or entity reference, or a string for other node types. Read-only.
  • nodeType — Contains the node type. Read-only.
  • nodeTypeString*— Contains the node type, in string form. Read-only.
  • nodeValue — Contains the text associated with the node. Read/write.
  • ownerDocument — Contains the root of the document. Read-only.
  • parentNode — Contains the parent node of the current node. Read-only.
  • parsed*— Returns true if this node has been parsed; false otherwise. Read-only.
  • prefix*— Contains the namespace prefix. Read-only.
  • previousSibling — Contains the previous sibling of this node. Read-only.
  • tagName — Contains the element name. Read-only.
  • text*— Contains the text content of the node and its subtrees. Read/write.
  • xml*— Contains the XML text representation of the node and all of its children. Read-only.

Here are the significant methods of this object:

  • appendChild — Appends a new child as the last child of the current node.
  • cloneNode — Returns a new node that is a copy of this node.
  • getAttribute — Gets the value of the named attribute.
  • getAttributeNode — Gets the named attribute node.
  • getElementsByTagName — Returns a list of all descendant elements that match the given name.
  • hasChildNodes — Returns true if this node has children; false otherwise.
  • insertBefore — Inserts a child node before the given node.
  • normalize — Normalizes all descendent elements by combining two or more text nodes next to each other into one text node.
  • removeAttribute — Removes or replaces the named attribute.
  • removeAttributeNode — Removes the given attribute from the element.
  • removeChild — Removes the given child node.
  • replaceChild — Replaces the given child node with the given new child node.
  • setAttribute — Sets the value of a named attribute.
  • setAttributeNode — Adds or changes the given attribute node on the element.
  • transformNode*— Transforms the node and its children by using the given XSL style sheet.

Using the XMLDOMAttribute Object

Attributes are considered nodes in the W3C DOM, but an attribute is not considered a child node of an element. As you'll see today, you use special methods to get the attributes of an element (for example, the getAttribute method). Here are the significant properties of the XMLDOMAttribute object:

  • attributes — List of attributes for this node. Read-only.
  • childNodes — Contains the list of the child nodes. Read-only.
  • dataType*— Contains the data type of this node. Read/write.
  • firstChild — Contains the first child of the current node. Read-only.
  • lastChild — Contains the last child of the current node. Read-only.
  • name — Contains the attribute name. Read-only.
  • namespaceURI*— Contains the URI for the namespace. Read-only.
  • nextSibling — Contains the next sibling of the node. Read-only.
  • nodeName — Contains the qualified name for an element, attribute, or entity reference, or a string for other node types. Read-only.
  • nodeType — Contains the node type. Read-only.
  • nodeTypedValue*— Contains the node's value. Read/write.
  • nodeTypeString*— Contains the node type, in string form. Read-only.
  • nodeValue — Contains the text associated with the node. Read/write.
  • ownerDocument — Contains the root of the document. Read-only.
  • parentNode — Holds the parent node (for nodes that can have parents). Read-only.
  • parsed*— Returns true if this node has been parsed; false otherwise. Read-only.
  • prefix*— Contains the namespace prefix. Read-only.
  • previousSibling — Contains the previous sibling of this node. Read-only.
  • specified — Indicates whether the node (usually an attribute) is explicitly specified or derived from a default value. Read-only.
  • text — Contains the text content of the node and its subtrees. Read/write.
  • value — Contains the attribute's value. Read/write.
  • xml — Contains the XML text representation of the node and all its descendants. Read-only.

Here are the significant methods of this object:

  • appendChild — Appends a new child as the last child of this node.
  • cloneNode — Returns a new node that is a copy of this node.
  • hasChildNodes — Is set to true if this node has children.
  • insertBefore — Inserts a child node before the given node.
  • removeChild — Removes the given child node from the list.
  • replaceChild — Replaces the given child node with the new child node.
  • transformNode — Transforms this node and its children by using the given XSL style sheet.

Using the XMLDOMText Object

When it comes time to access the data in an XML document, you'll usually want to work with the text content of an element or an attribute, and you can use the Microsoft XMLDOMText object for text nodes. Here are the significant properties of the XMLDOMText object:

  • attributes — Holds the list of attributes for the node. Read-only.
  • childNodes — Contains the list of the child nodes. Read-only.
  • data — Contains the node's data. What is actually stored depends on the node type. Read/write.
  • dataType*— Contains the data type for the node. Read/write.
  • firstChild — Contains the first child of the current node. Read-only.
  • lastChild — Contains the last child of the current node. Read-only.
  • length — Contains the length, in characters, of the data. Read-only.
  • namespaceURI*— Contains the URI for the namespace. Read-only.
  • nextSibling — Contains the next sibling of this node. Read-only.
  • nodeName — Contains the qualified name of an element, attribute, or entity reference, or a string for other node types. Read-only.
  • nodeType — Indicates the node type. Read-only.
  • nodeTypedValue*— Contains the node's value. Read/write.
  • nodeTypeString*— Contains the node type, in string form. Read-only.
  • nodeValue — Contains the text associated with the node. Read/write.
  • ownerDocument — Contains the root of the document. Read-only.
  • parentNode — Contains the parent node. Read-only.
  • parsed*— Returns true if this node has been parsed; false otherwise. Read-only.
  • prefix*— Contains the namespace prefix. Read-only.
  • previousSibling — Contains the previous sibling of this node. Read-only.
  • specified — Indicates whether the node is explicitly specified or derived from a default value. Read-only.
  • text*— Holds the text content of the node. Read/write.
  • xml*— Holds the XML representation of the node and all of its descendants. Read-only.

Here are the significant methods of this object:

  • appendChild — Appends a new child as the last child of the node.
  • appendData — Appends the given string to the existing string data.
  • cloneNode — Returns a new node that is a copy of this node.
  • deleteData — Removes the given substring within the string data.
  • hasChildNodes — Returns true if this node has children; false otherwise.
  • insertBefore — Inserts a child node before the specified node.
  • insertData — Inserts the supplied string at the specified offset.
  • removeChild — Removes the specified child node from the list of children.
  • replaceChild — Replaces the specified child node with the given new child node.
  • splitText — Breaks the text node into two text nodes.
  • substringData — Returns a substring of the full string.
  • transformNode*— Transforms the node and its children by using the given XSL style sheet.

This overview of the JavaScript objects you'll be using today might seem somewhat mysterious, so in the following sections you'll put it to work.

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