Library Zone Articles
External Articles
Byte Size

Discovery Zone Catalogue
Interactive Zone Ask the Gurus
Discussion Groups
Etc Cartoons
ASP Web Ring ASP Web Ring - Get your VS.NET news here
The Developer's Resource & Community Site
International This Week Forums Author Central Find a Job

Byte Size

Byte size is exactly what it says: Byte Size articles of all the channels covered by We will publish Byte Size articles on a regular basis to be a smaller alternative to our main articles.

We are currently seeking authors for Byte Size articles for all areas on If you would like to submit a Byte Size article, please use our form here.

COM Byte SizeASP Byte SizeJava Byte SizeATR Byte Size

Byte Size Contents:

Want to read Byte Size articles? Go here: Articles

Interested in reading XML FAQ's? Go here: XML FAQ's

XML Byte Size Articles:

Level 3 DOM by Aaron Skinner and Richard Anderson
An introduction to a discussion concerning the Level 3 DOM,

Type Library Info, XML and a bit of XSL for fun! by Richard Anderson November 12 1999
This article assumes you understand COM, Type Libraries, XML and enough about VB that you can either use the code as a starting point, or, translate it into another language.
Go To Article.
This article can be downloaded: Zip File (76kb).


What is the single most important thing XML enables you to do now, that you were unable to do before?

XML has given me a truly universal data exchange format, as well a nice storage format for simple applications. As an exchange format, for the first time ever I can exchange data with people in a format that is typically human readable and easily processed by a computer using free/cheap software (check out for example). Further more I can add new elements or attributes to an XML document that were not previously there, without the software that processes the file format breaking (providing the original content model was open).

What do you think the most important development in XML will be over the next 12 months?

For people to use XML as the basis for e-business exchange formats, open file formats etc, we need a decent schema specification. The schema format must allow us to unambiguously describe an expected/allowed format for a given class of XML document. This schema can then be used for validation, or as basic programming spec for conversion programs etc. The W3C are getting close with their schema spec, but no doubt this will need a lot of revision and work over the next 12 months. Once a good schema spec is in place, we need a good XML repository with 'decent' schemas. A lot of the existing repositories contain junk. For a good example of how to do things the right way, any EDI readers our there should check out the Basda ( specifications on BizTalk. That's how EDI and XML should work together! Even if you are not in EDI, check out the basic approach to document structuring taken by Basda, it's good.

What do you consider to be the biggest misconception surrounding XML?

As XML was created by the W3C, it is often discussed in a context with HTML, and is often seen as being a web-only technology. Worse still, people often see it as a presentation language, something that is the replacement for HTML. Both of these are serious misconceptions. Whilst the W3C do focus on web technologies, people should understand that XML is nothing to do with presentation of data in a browser. XML is just a very good way of structuring data for exchange or processing. The fact that data can be processed using XSL, converted to HTML and then viewed in a browser, is just one of the many advantages of keeping data in an XML format (or exporting data into an XML format before processing). The same data could be imported into a database, converted into a different XML format etc etc.

XML FAQ's from dev-xml

What is SAX ?

SAX is an API for event-based XML parsing, as opposed to DOM-based XML parsing.

The home of SAX is here :

That is, for DOM-based parsing, the parser reads in the entire XML document, builds a tree-based object model around the document, and then gives you access to the entire document through that object model. On the other hand, in event-based parsing you are given access to "events" that are raised to your application while the document is being read in by the parser. For example, there might be an event raised to tell your application "this is the start of an element", and another which says "this is the end of an element".

This is too small a nutshell to properly explain SAX. For a better resource, see

The advantages of SAX over DOM can be a smaller memory footprint, since the whole document doesn't have to be in memory at once, as well as speed. However, for applications where you need to access an entire document as an entity, DOM is the better way to go.

David Hunter
[email protected]

Other XML FAQ's and resources

Check your XML!

Microsoft XML Developer's Guide External Link

Extreme XML External Link Microsoft magazine - ASP Technology and the XML DOM, Sept 99 issue

SOAP spec External Link

OReilly's DocBook External Link, the long-awaited O'Reilly DocBook, and the entire book is online now

Oracle's XML pages External Link, including free Developer's Kit, a live XML demo and technical articles.

Resources available for validating and checking XML

Richard Tobin's External Link well-formedness and validator using the RXP parser. External Link

Frontier 5's External Link XML syntax checker's External Link RUWF - based on the Lark parser.

IBM's DOMit External Link validator.

IBM's experimental XML4J External Link parser by Ralf I Pfeiffer.

Microsoft's XML Validator (download) External Link

Visit our NEW WTL Section

Visit the IDR Forums

Code Project

Learn C#

Visit the IDR Bookstore! - Jobs for Professional Developers

Contribute to IDR:

To contribute an article to IDR, a click here.

To contact us at, use our feedback form, or email us.

To comment on the site contact our webmaster.

Promoted by CyberSavvy UK - website promotion experts

All content © Copyright 2000, Disclaimer notice