SAX is mostly about the instance document, not the DTD or schema. However, given a validating parser, or at least an internal DTD subset, the DTD can affect the contents of the instance document in six ways:

SAX includes an adapter class you can subclass to build these sorts of two-way filters, org.xml.sax.helpers.XMLFilterImpl. Its general design is similar to what I’ve shown above. However, it implements all the relevant interfaces in one class:

XML::SAX is a new way to work with XML Parsers in Perl. In this article we’ll discuss why you should be using SAX, why you should be using XML::SAX, and we’ll see some of the finer implementation details. The text below assumes some familiarity with callback, or push based parsing, but if you are unfamiliar with these techniques then a good place to start is Kip Hampton’s excellent series of articles on XML.com.

This is a quickstart guide for processing XML in Perl using SAX, the Simple API for XML. It is targetted at people who already know XSLT or DOM programming and want to do first steps with SAX by using some of the already available modules. This guide assumes knowledge of XML and, of course, Perl.

As an events-based parser that processes documents in a serial manner, the Simple API for XML (SAX) presents an excellent alternative to the Document Object Model (DOM).

SAX – An alternative approach to parsing [PDF]

I have a fascination with dead technologies, which explains why I started reading the Java Web Services Tutorial today. In the XSLT chapter, I came across this gem entitled “Generating XML from an Arbitrary Data Structure”.

The Java API for XML Processing (JAXP) makes it easy to process XML data using applications written in the Java programming language. JAXP leverages the parser standards SAX (Simple API for XML Parsing) and DOM (Document Object Model) so that you can choose to parse your data as a stream of events or to build a tree-structured representation of it.

This page continues the overview of the SAX APIs, summarizing those you are most likely to use when building a SAX-based application.

The customer requirement is to separate the SAX spacecraft in sunlight. Because the rocket flies Eastward and the separation occurs at 600 km altitude, the launch could occur as early as 3:00 GMT (23:00 Eastern Daylight time) and still nominally separate in sunlight (approximately over West Africa).

For debugging purposes, it’s often useful to know exactly where a particular element or other item appears. To provide this information, parsers should (but are not required to) implement the Locator interface. A Locator object knows at which point in which file the latest event was fired.

This example demonstrates how to create a simple SAX validator application in Microsoft® Visual Basic®. The application allows the user to select an XML file to be validated against an XSD schema file.

This document describes a set of small but hopefully useful extensions to the current SAX 2.0beta. For the most part they are independent and can be evaluated individually. Below you'll find brief descriptions of each of them, links to the online javadoc, and links to download sources and pre-built binaries of sample implementations.

SAX 1.0 has been very widely implemented and has been in widespread use almost since the day the first draft appeared on 12 January 1998 – a month earlier than the date of the final XML 1.0 recommendation. It has met user needs well, in spite of a few criticisms, some of which are hinted at in this chapter.

The difference to SAX becomes obvious in the DOM implementation of our example. [PDF]

SAX parses a document sequentially, doing a callback for each thing that it encounters in the XML file. Because this is very fast and takes a minimum amount of memory, it is ideal for some tasks.

SAX parsers use a callback mechanism to parse XML. Applications register a ContentHandler to receive the parsing events. Although this is a little more complicated, it's more efficient because there's no need to build any data structures.

In working on the Smalltalk SAX 2 implementation has generated some questions and issues on which I could use some input. You may find it useful to look at the SAX 2 API. The SAX 2 web site is at: http://www.megginson.com/SAX/SAX2/

Developers using SAX, for example, will state in their Java source code that the application implements one or more SAX interfaces. [PDF]

OTN XML DB Sample: Standalone SAX Loader Application - Install