Home > Articles > Web Services > XML

XML Reference Guide

📄 Contents

  1. XML Reference Guide
  2. Overview
  3. What Is XML?
  4. Informit Articles and Sample Chapters
  5. Books and e-Books
  6. Official Documentation
  7. Table of Contents
  8. The Document Object Model
  9. Informit Articles and Sample Chapters
  10. Books and e-Books
  11. Official Documentation
  12. DOM and Java
  13. Informit Articles and Sample Chapters
  14. Books and e-Books
  15. Implementations
  16. DOM and JavaScript
  17. Using a Repeater
  18. Repeaters and XML
  19. Repeater Resources
  20. DOM and .NET
  21. Informit Articles and Sample Chapters
  22. Books and e-Books
  23. Documentation and Downloads
  24. DOM and C++
  25. DOM and C++ Resources
  26. DOM and Perl
  27. DOM and Perl Resources
  28. DOM and PHP
  29. DOM and PHP Resources
  30. DOM Level 3
  31. DOM Level 3 Core
  32. DOM Level 3 Load and Save
  33. DOM Level 3 XPath
  34. DOM Level 3 Validation
  35. Informit Articles and Sample Chapters
  36. Books and e-Books
  37. Documentation and Implementations
  38. The Simple API for XML (SAX)
  39. Informit Articles and Sample Chapters
  40. Books and e-Books
  41. Official Documentation
  42. SAX and Java
  43. Informit Articles and Sample Chapters
  44. Books and e-Books
  45. SAX and .NET
  46. Informit Articles and Sample Chapters
  47. SAX and Perl
  48. SAX and Perl Resources
  49. SAX and PHP
  50. SAX and PHP Resources
  51. Validation
  52. Informit Articles and Sample Chapters
  53. Books and e-Books
  54. Official Documentation
  55. Document Type Definitions (DTDs)
  56. Informit Articles and Sample Chapters
  57. Books and e-Books
  58. Official Documentation
  59. XML Schemas
  60. Informit Articles and Sample Chapters
  61. Books and e-Books
  62. Official Documentation
  63. RELAX NG
  64. Informit Articles and Sample Chapters
  65. Books and e-Books
  66. Official Documentation
  67. Schematron
  68. Official Documentation and Implementations
  69. Validation in Applications
  70. Informit Articles and Sample Chapters
  71. Books and e-Books
  72. XSL Transformations (XSLT)
  73. Informit Articles and Sample Chapters
  74. Books and e-Books
  75. Official Documentation
  76. XSLT in Java
  77. Java in XSLT Resources
  78. XSLT and RSS in .NET
  79. XSLT and RSS in .NET Resources
  80. XSL-FO
  81. Informit Articles and Sample Chapters
  82. Books and e-Books
  83. Official Documentation
  84. XPath
  85. Informit Articles and Sample Chapters
  86. Books and e-Books
  87. Official Documentation
  88. XML Base
  89. Informit Articles and Sample Chapters
  90. Official Documentation
  91. XHTML
  92. Informit Articles and Sample Chapters
  93. Books and e-Books
  94. Official Documentation
  95. XHTML 2.0
  96. Documentation
  97. Cascading Style Sheets
  98. Informit Articles and Sample Chapters
  99. Books and e-Books
  100. Official Documentation
  101. XUL
  102. XUL References
  103. XML Events
  104. XML Events Resources
  105. XML Data Binding
  106. Informit Articles and Sample Chapters
  107. Books and e-Books
  108. Specifications
  109. Implementations
  110. XML and Databases
  111. Informit Articles and Sample Chapters
  112. Books and e-Books
  113. Online Resources
  114. Official Documentation
  115. SQL Server and FOR XML
  116. Informit Articles and Sample Chapters
  117. Books and e-Books
  118. Documentation and Implementations
  119. Service Oriented Architecture
  120. Web Services
  121. Informit Articles and Sample Chapters
  122. Books and e-Books
  123. Official Documentation
  124. Creating a Perl Web Service Client
  125. SOAP::Lite
  126. Amazon Web Services
  127. Creating the Movable Type Plug-in
  128. Perl, Amazon, and Movable Type Resources
  129. Apache Axis2
  130. REST
  131. REST Resources
  132. SOAP
  133. Informit Articles and Sample Chapters
  134. Books and e-Books
  135. Official Documentation
  136. SOAP and Java
  137. Informit Articles and Sample Chapters
  138. Books and e-Books
  139. Official Documentation
  140. WSDL
  141. Informit Articles and Sample Chapters
  142. Books and e-Books
  143. Official Documentation
  144. UDDI
  145. UDDI Resources
  146. XML-RPC
  147. XML-RPC in PHP
  148. Informit Articles and Sample Chapters
  149. Books and e-Books
  150. Official Documentation
  151. Ajax
  152. Asynchronous Javascript
  153. Client-side XSLT
  154. SAJAX and PHP
  155. Ajax Resources
  156. JSON
  157. Ruby on Rails
  158. Creating Objects
  159. Ruby Basics: Arrays and Other Sundry Bits
  160. Ruby Basics: Iterators and Persistence
  161. Starting on the Rails
  162. Rails and Databases
  163. Rails: Ajax and Partials
  164. Rails Resources
  165. Web Services Security
  166. Web Services Security Resources
  167. SAML
  168. Informit Articles and Sample Chapters
  169. Books and e-Books
  170. Specification and Implementation
  171. XML Digital Signatures
  172. XML Digital Signatures Resources
  173. XML Key Management Services
  174. Resources for XML Key Management Services
  175. Internationalization
  176. Resources
  177. Grid Computing
  178. Grid Resources
  179. Web Services Resource Framework
  180. Web Services Resource Framework Resources
  181. WS-Addressing
  182. WS-Addressing Resources
  183. WS-Notifications
  184. New Languages: XML in Use
  185. Informit Articles and Sample Chapters
  186. Books and e-Books
  187. Official Documentation
  188. Google Web Toolkit
  189. GWT Basic Interactivity
  190. Google Sitemaps
  191. Google Sitemaps Resources
  192. Accessibility
  193. Web Accessibility
  194. XML Accessibility
  195. Accessibility Resources
  196. The Semantic Web
  197. Defining a New Ontology
  198. OWL: Web Ontology Language
  199. Semantic Web Resources
  200. Google Base
  201. Microformats
  202. StructuredBlogging
  203. Live Clipboard
  204. WML
  205. XHTML-MP
  206. WML Resources
  207. Google Web Services
  208. Google Web Services API
  209. Google Web Services Resources
  210. The Yahoo! Web Services Interface
  211. Yahoo! Web Services and PHP
  212. Yahoo! Web Services Resources
  213. eBay REST API
  214. WordML
  215. WordML Part 2: Lists
  216. WordML Part 3: Tables
  217. WordML Resources
  218. DocBook
  219. Articles
  220. Books and e-Books
  221. Official Documentation and Implementations
  222. XML Query
  223. Informit Articles and Sample Chapters
  224. Books and e-Books
  225. Official Documentation
  226. XForms
  227. Informit Articles and Sample Chapters
  228. Books and e-Books
  229. Official Documentation
  230. Resource Description Framework (RDF)
  231. Informit Articles and Sample Chapters
  232. Books and e-Books
  233. Official Documentation
  234. Topic Maps
  235. Informit Articles and Sample Chapters
  236. Books and e-Books
  237. Official Documentation, Implementations, and Other Resources
  238. Rich Site Summary (RSS)
  239. Informit Articles and Sample Chapters
  240. Books and e-Books
  241. Official Documentation
  242. Simple Sharing Extensions (SSE)
  243. Atom
  244. Podcasting
  245. Podcasting Resources
  246. Scalable Vector Graphics (SVG)
  247. Informit Articles and Sample Chapters
  248. Books and e-Books
  249. Official Documentation
  250. OPML
  251. OPML Resources
  252. Summary
  253. Projects
  254. JavaScript TimeTracker: JSON and PHP
  255. The Javascript Timetracker
  256. Refactoring to Javascript Objects
  257. Creating the Yahoo! Widget
  258. Web Mashup
  259. Google Maps
  260. Indeed Mashup
  261. Mashup Part 3: Putting It All Together
  262. Additional Resources
  263. Frequently Asked Questions About XML
  264. What's XML, and why should I use it?
  265. What's a well-formed document?
  266. What's the difference between XML and HTML?
  267. What's the difference between HTML and XHTML?
  268. Can I use XML in a browser?
  269. Should I use elements or attributes for my document?
  270. What's a namespace?
  271. Where can I get an XML parser?
  272. What's the difference between a well-formed document and a valid document?
  273. What's a validating parser?
  274. Should I use DOM or SAX for my application?
  275. How can I stop a SAX parser before it has parsed the entire document?
  276. 2005 Predictions
  277. 2006 Predictions
  278. Nick's Book Picks

The Simple API for XML, or SAX, was developed by the XML-DEV mailing list. Rather than treating an XML document as a tree-like structure, SAX treats it as a series of events such as startDocument or endElement. To accomplish this, a SAX appllication consists of a parser that sends these events to "handlers," methods or functions designated to handle them.

In PHP, you can handle this with straight functions, or you can handle them within a class. In this example, we'll do a combination of the two, handling the entire process from within a single class.

Creating a SAX application involves processing events as they arrive, keeping in mind that the handler class knows only about the current event; if you need information about previous events, you need to save it yourself. For example, consider this order file:

<?xml version="1.0"?>
<order orderid="THX1138" customerNumber="3263827">
    <lineitem itemid="C33">
       <item>3/4" Hex Bolt</item>
       <quantity>36</quantity>
       <unitprice currency="dollars">.35</unitprice>
    </lineitem>
    <lineitem itemid="M48">
       <item>Condenser</item>
       <quantity>1</quantity>
       <unitprice currency="dollars">2200</unitprice>
    </lineitem>
    <delivery>Overnight</delivery>
</order>

We can create a SAX application that lists the order information, including the extended total for each item and the grand total for the order. We'd start by creating the main SAX application:

<?php

class OrderProcessor {

   function OrderProcessor(){
   }

   function ProcessOrder($url) {

      $parser = xml_parser_create();

      $fp = fopen($url, "r");
      while(!feof($fp)) {
         $line = fgets($fp, 4096);
         xml_parse($parser, $line);
      }
      fclose($fp);

      xml_parser_free($parser);

   }

}

$order =& new OrderProcessor();
$success = $order->ProcessOrder("order.xml");

?>

We start by creating the new object and running the ProcessOrder function. The function creates the parser and feeds the file to it 4K at a time. At this point, however, the script doesn't actually do anything. In order to get it to act on the file, we need to assign handlers:

<?php

class OrderProcessor {

   function OrderProcessor(){
   }

   function ProcessOrder($url) {

      $parser = xml_parser_create();

      xml_set_element_handler($parser, "_startElement", "_endElement");
      xml_set_character_data_handler($parser, "_charHandler");

      $fp = fopen($url, "r");
      while(!feof($fp)) {
         $line = fgets($fp, 4096);
         xml_parse($parser, $line);
      }
      fclose($fp);

      xml_parser_free($parser);

   }

   function _startElement($parser, $name, $attrs) {
   }

   function _endElement($parser, $name) {
   }

   function _charHandler($parser, $data) {
   }

}

$order =& new OrderProcessor();
$success = $order->ProcessOrder("order.xml");

?>

The xml_set_element_handler() function sets both the "start element" and "end element" handlers, and the xml_set_character_data_handler() function takes care of, well, setting the character data handler.

Note that in PHP there is no way to set handlers for the "start document" and "end document" events, so we'll run them manually within the application:

<?php

class OrderProcessor {

   var $totalPrice;

   function OrderProcessor(){ }

   function ProcessOrder($url) {

      $parser = xml_parser_create();
      xml_set_object($parser, &$this);

      xml_set_element_handler($parser, "_startElement", "_endElement");
      xml_set_character_data_handler($parser, "_characters");

      $this->_startDocument($parser);
   
      $fp = fopen($url, "r");
      while(!feof($fp)) {
         $line = fgets($fp, 4096);
         xml_parse($parser, $line);
      }
      fclose($fp);

      $this->_endDocument($parser);

      xml_parser_free($parser);

   }

   function _startDocument($parser){
      $this->totalPrice = 0;
   }

   function _endDocument($parser){
      echo("<br />Order total: ".$this->totalPrice."<br />");
   }

   function _startElement($parser, $name, $attrs) {
   }

   function _endElement($parser, $name) {
   }

   function _characters($parser, $data) {
   }

}

$order =& new OrderProcessor();
$success = $order->ProcessOrder("order.xml");

?>

In this case, we're going to gather information about the order, so we'll start by initializing the totalPrice variable before we start parsing, and displaying its value when parsing is finished.

Most events fire multiple times. For example, the first events in the sample document are:

startDocument
characters (white space)
startElement (lineitem)
characters (white space)
startElement (item)
characters (3/4" Hex Bolt)
endElement (item)
characters (white space)
startElement (quantity)
characters (36)
endElement (quantity)
...

Now, it's important to understand that each of these events are completely independent of each other. When the characters event fires to note the 3/4" Hex Bolt -- more on the _characters function in a moment -- the handler has no way of knowing that that text is part of the item element. If this information is important (as it is here) we need to keep track of it ourselves.

For our purposes, that means that when we close an element we're tracking, such as item or quantity, we need to store the text that's been flowing through the _characters method function, like so:

<?php

class OrderProcessor {

   var $totalPrice = 0; 
   var $itemid = ""; 
   var $itemname = ""; 
   var $quantity = 0;
   var $unitprice = 0; 
   var $currentElement = ""; 
   var $thisText = ""; 

   function OrderProcessor(){ }

   function ProcessOrder($url) {

      $parser = xml_parser_create();
      xml_parser_set_option($parser, XML_OPTION_CASE_FOLDING, false);
      xml_set_object($parser, &$this);

      xml_set_element_handler($parser, "_startElement", "_endElement");
      xml_set_character_data_handler($parser, "_charHandler");

      $this->_startDocument($parser);
   
      $fp = fopen($url, "r");
      while(!feof($fp)) {
         $line = fgets($fp, 4096);
         xml_parse($parser, $line);
      }
      fclose($fp);

      $this->_endDocument($parser);

      xml_parser_free($parser);

   }

   function _startDocument($parser){
      $this->totalPrice = 0;
   }

   function _endDocument($parser){
      echo("<br />Order total: ".$this->totalPrice."<br />");
   }

   function _startElement($parser, $name, $attrs) {

      if ($name == "order"){ 
  
         $orderid = $attrs["orderid"]; 
         $customerid = $attrs["customerNumber"]; 
         echo("Order ".$orderid." for customer ".$customerid.":<br /><br />"); 

      } else if ($name == "lineitem"){ 
         $this->itemid = $attrs["itemid"]; 
      }    

      $currentElement = $name;

   }

   function _endElement($parser, $name) {

      if (strlen($this->thisText) > 0) { 
         if ($name == "item"){ 
            $this->itemname = $this->thisText;
         } else if ($name == "quantity"){ 
            $this->quantity = $this->thisText; 
         } else if ($name == "unitprice"){ 
            $this->unitprice = $this->thisText; 
         } 
         $this->thisText = ""; 
      } 
      if ($name == "lineitem"){ 
         $this->extendedPrice = $this->quantity * $this->unitprice; 
         echo(" Item: ".$this->itemname." (".$this->itemid.") ".$this->quantity. " @ ".$this->unitprice." = ".$this->extendedPrice."<br />"); 
         $this->totalPrice = $this->totalPrice + $this->extendedPrice; 
         $this->itemname = ""; 
         $this->quantity = ""; 
         $this->quantityInt = 0; 
         $this->unitprice = ""; 
         $this->unitpriceDbl = 0; 
      }

   }

   function _charHandler($parser, $data) {

      $this->thisText = $this->thisText . $data;

   }

}

$order =& new OrderProcessor();
$success = $order->ProcessOrder("order.xml");

?>

Let's start with _startElement. If it's the order element or the lineitem element we've run across, we're pulling the appropriate information from the attributes present, which are fed to the function as an array. In any case, we're storing the name of the element.

In most cases, the next event that will fire is the characters event as the content of the element is processed. One thing that's a little strange about SAX is that you never really know just how text will be processed. You might get it all in one big chunk, or you might get it in a series of smaller pieces. Because of this little idiosyncrasy, we need to store each call in the thisText variable. When we get to the end of the element, the _endElement function executes, and we can check (and clear) the contents of the variable.

Note that our method of saving the "current" element only works because we're only looking for the text children of simple elements. If we needed to track multiple levels of elements, we'd have to find another way of storing the information (or use another way of parsing the document, such as DOM). In this case, though, it's sufficient, so as each element closes, we check to see what it was and perform the appropriate actions. If it was an item, quantity, or unitprice element, we simply store the appropriate values. If, on the other hand, its the end of a lineitem element, we perform the appropriate calculations, display the information for that item, and reinitialize the variables.

Calling up the PHP page displays a result of

Order THX1138 for customer 3263827

Item: 3/4" Hex Bolt (C33) 36 @ .35 = 12.6
Item: Condenser (M48) 1 @ 2200 = 2200.0

Order total: 2212.6

SAX is, in many cases, faster and more efficient than DOM, because it only deals with the information that's relevant at that particular moment rather than keeping the entire tree in memory at once. It may take a little getting used to, but you'll find that it can be an extremely versatile item in your toolbox.

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.