<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
<TITLE>Grafting DOM on a C++ XML parser?</TITLE>
<META content="MSHTML 5.00.2920.0" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#800080 face=Arial size=2><SPAN class=616255918-17111999>Note:
David Brownwell's conformance articles did NOT cover our IE5 COM based
MSXML.DLL. </SPAN></FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #800080 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Ben Berck
[mailto:BBerck@ESPS.com]<BR><B>Sent:</B> Wednesday, November 17, 1999 9:48
AM<BR><B>To:</B> xml-dev@ic.ac.uk<BR><B>Subject:</B> Grafting DOM on a C++ XML
parser?<BR><BR></DIV></FONT>
<P><FONT size=2>Sean of FalconWing wrote:</FONT> <BR><FONT
size=2>>>(Note that there are add-on utilities to graft DOM and SAX2
support to</FONT> <BR><FONT size=2>>>various popular parsers too)</FONT>
</P>
<P><FONT size=2>We have been burnt with relying on MSXML.DLL, so we have
chosen Dundas Software's new C++ XML parser, which includes source code.
However, I was disappointed to see that it doesn't support XML DOM.</FONT></P>
<P><FONT size=2>What add-on utility exists to get the DOM on top of a C++ XML
Parser class?</FONT> </P>
<P><FONT size=2>Thanks,</FONT> <BR><FONT size=2>Ben Berck</FONT> </P><BR>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
schen@falconwing.com [<A
href="mailto:schen@falconwing.com">mailto:schen@falconwing.com</A>]</FONT>
<BR><FONT size=2>Sent: Wednesday, November 17, 1999 11:42 AM</FONT> <BR><FONT
size=2>To: Sean Mc Grath</FONT> <BR><FONT size=2>Cc: xml-dev@ic.ac.uk</FONT>
<BR><FONT size=2>Subject: Re: Towards an XML Parser Compliance Table</FONT>
<BR><FONT size=2>Version:17-11-99-15:16</FONT> </P><BR>
<P><FONT size=2>Hi Sean, everyone,</FONT> </P>
<P><FONT size=2>David Brownell already wrote up a nice article about this
at:</FONT> <BR><FONT size=2><A
href="http://www.xml.com/pub/1999/09/conformance/index.html"
target=_blank>http://www.xml.com/pub/1999/09/conformance/index.html</A></FONT>
<BR><FONT size=2>which I can't get to at the moment.</FONT> </P>
<P><FONT size=2>His test driver can be found at <A
href="http://home.pacbell.net/david-b/xml/"
target=_blank>http://home.pacbell.net/david-b/xml/</A></FONT> </P>
<P><FONT size=2>From memory:</FONT> </P>
<P><FONT size=2>On Wed, 17 Nov 1999, Sean Mc Grath wrote:</FONT> </P>
<P><FONT size=2>> Fully 1.0 Compliant - Non Validating</FONT> <BR><FONT
size=2>> -------------------------------------</FONT> <BR><FONT size=2>4.
Sun ProjectX</FONT> </P>
<P><FONT size=2>> Fully XML 1.0 Compliant - Validating</FONT> <BR><FONT
size=2>> ------------------------------------</FONT> <BR><FONT size=2>2.
Sun ProjectX</FONT> </P>
<P><FONT size=2>> Non XML 1.0 Compliant - Non-Validating</FONT> <BR><FONT
size=2>> --------------------------------------</FONT> <BR><FONT
size=2>aelfred</FONT> <BR><FONT size=2>DataChannel</FONT> <BR><FONT
size=2>Microsoft</FONT> <BR><FONT size=2>IBM XML4J</FONT> <BR><FONT size=2>IBM
XML4C</FONT> </P><BR>
<P><FONT size=2>> Non XML 1.0 Compliant - Validating</FONT> <BR><FONT
size=2>> ----------------------------------</FONT> <BR><FONT size=2>>
nsgmls (C++)</FONT> <BR><FONT size=2>> xmlproc (Python)</FONT> </P>
<P><FONT size=2>IBM XML4J</FONT> <BR><FONT size=2>IBM XML4C (? I think)</FONT>
</P>
<P><FONT size=2>-------------</FONT> <BR><FONT size=2>BTW, I think a more
useful table would include what other features the</FONT> <BR><FONT
size=2>parsers have, rather than just a strict compliance/validating
judgement.</FONT> </P>
<P><FONT size=2>Example features to consider would be: parser size (why I use
aelfred),</FONT> <BR><FONT size=2>parser speed (why XP is a good choice),
language supported (Java/C/C++),</FONT> <BR><FONT size=2>DOM1 support, DOM2
support, SAX support, SAX2 support, namespace support,</FONT> <BR><FONT
size=2>external entities support, memory usage, maximum file size
supported,</FONT> <BR><FONT size=2>and last but not least character set
encodings supported.</FONT> </P>
<P><FONT size=2>. . . Sean (not related =)</FONT> </P><BR><BR>
<P><FONT size=2>xml-dev: A list for W3C XML Developers. To post, <A
href="mailto:xml-dev@ic.ac.uk">mailto:xml-dev@ic.ac.uk</A></FONT> <BR><FONT
size=2>Archived as: <A href="http://www.lists.ic.ac.uk/hypermail/xml-dev/"
target=_blank>http://www.lists.ic.ac.uk/hypermail/xml-dev/</A> and on
CD-ROM/ISBN 981-02-3594-1</FONT> <BR><FONT size=2>To unsubscribe, <A
href="mailto:majordomo@ic.ac.uk">mailto:majordomo@ic.ac.uk</A> the following
message;</FONT> <BR><FONT size=2>unsubscribe xml-dev</FONT> <BR><FONT
size=2>To subscribe to the digests, <A
href="mailto:majordomo@ic.ac.uk">mailto:majordomo@ic.ac.uk</A> the following
message;</FONT> <BR><FONT size=2>subscribe xml-dev-digest</FONT> <BR><FONT
size=2>List coordinator, Henry Rzepa (<A
href="mailto:rzepa@ic.ac.uk">mailto:rzepa@ic.ac.uk</A>)</FONT>
</P></BLOCKQUOTE></BODY></HTML>