Illustration of Different Node Trees for XML (W3C(XT)/IE5)

Steven R. Newcomb srn at
Fri Apr 9 21:58:28 BST 1999

[Ken Holman:]

> ...alternate strategies are required with
> different products when accessing components of
> an XML document because the node structure
> interpreted by engines differ.

Thanks, Ken, for sharing this evidence of the
importance of the Megginson committee's work.  If
these different products had had a standard model
of parsed XML to work from, we could now say that
XT and/or IE5 fail to conform to the standard, and
in exactly what way(s) they fail to conform.
Their respective owners would have to take
responsibility for their incompatibility with one

When the Megginson committee's work is done, I
hope every XML product and system will conform to
the consequent Recommendation as quickly as
possible.  I hope that developers will simply
refuse to work with systems that don't conform.
It's certainly in the best interests of every
developer (and of his/her customers) to demand
nothing less than strict conformance to the
standard Recommendation regarding how XML
resources appear as node trees after they have
been parsed.

(Shhh.  Did someone say "Grove"?)


Steven R. Newcomb, President, TechnoTeacher, Inc.
srn at

voice: +1 972 231 4098 (at ISOGEN: +1 214 953 0004 x137)
fax    +1 972 994 0087 (at ISOGEN: +1 214 953 3152)

3615 Tanner Lane
Richardson, Texas 75082-2618 USA

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list