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).

This article demonstrates the techniques involved in parsing an XML document using SAX and the JAXP API. It assumes a basic familiarity with XML and some experience with the Java programming language.

SAX – An alternative approach to parsing [PDF]

This preview of the second edition of XML by Example by Benoit Marchal gives a solid introduction to SAX, the event-based API for processing XML that has become a de facto standard. This preview tells when to use SAX instead of DOM, gives an overview of commonly used SAX interfaces, and provides detailed examples in a Java-based application with many code samples.

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.

There are two simple methods in my application: one is reading xml file by using DOM method and the other is reading the same file using SAX method. I’m not gonna explain the difference between DOM & SAX, only telling this that in DOM , a parser must read the whole file u r reading before u can read anything. In other words the file is loaded into the memory of your application, where DOM makes an object model of it, then u can traverse throw the elements of this object model & receive/update needed information. SAX method, reads file step by step, so it is a resource benefit .

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.

Although the Simple API for XML (SAX) is not built into the .NET platform, SAX type functionality can be created using the XmlTextReader.

The Infoset is a nice idea, but it is barely useful if software cannot be written against it. Fortunately, there are two widely accepted programmatic interfaces based on the Infoset that allow documents to be manipulated and [de]serialized at the Infoset level, not at the character-stream/markup level: SAX and DOM.

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.

See the file simple_appl.py for a simple example