by Piroz Mohseni The XML parser world is a dynamic one. As standards change, the parsers change as well–XML parsers are becoming more sophisticated. For most programming projects, the parser, at minimum, must support DOM Level 2, SAX 2, XSLT, and Namespaces. All the parsers discussed here prov

Bijan Parsia tells us…As is all too common in the programming world, much of the XML community has identified itself and all its works with object oriented programming (OOP). While I'm a fan of OOP, it's clear to me that even the best OOP-for-XML techniques aren't a panacea, and, moreo

An excerpt from WROX Press Professional XML Databases by Kevin Williams, Michael Brundage, Patrick Dengler, Jeff Gabriel, Andy Hoskinson, Michael Kay, Thomas Maxwell, Marcelo Ochoa, Johnny Papa, Mohan Vanmane. In this chapter, we will examine some approaches for taking an existing relatio

Before making the important decision to purchase an XML parser, look at the results of Steve Franklin's test of a selection of both DOM- and SAX-based parsers.

By Kip Hampton, The problem: The XML documents you have to parse are getting too large to load the entire document tree into memory; performance is suffering. The solution: use SAX.

Over nineteen months since its previous inception as a Working Draft, XML Fragment Interchange has become a W3C Candidate Recommendation.