Lists Home |
Date Index |
- From: "Simon St.Laurent" <firstname.lastname@example.org>
- To: email@example.com
- Date: Wed, 10 Feb 1999 15:54:15 -0500
>There will always be a tradeoff between code size,
>performance and conformance to the spec. We have taken the same approach:
>for XML which might go outside our environment or some in from outside, we
>use a heavyweight parser with full validation. But where it's "behind the
>covers" we use a homegrown (tiny, nonconformant) parser and just check the
>structures a few times during design, with a validating parser.
If we could work with parser layers rather than parsers, this might become
a lot easier to manage. We could just turn on the parts we need and turn
off the ones we don't.
I'm hoping to build an open and extensible parser based on the approach I'm
outlining in that "Layered Model for XML Processing" document
(http://www.simonstl.com/articles/layering/layered.htm) over the summer.
Open source, open architecture, open model. It'll be event-based for now,
maybe with a tree-builder at the end.
Tilting at windmills, a glorious hobby.
XML: A Primer / Building XML Applications (April)
Sharing Bandwidth / Cookies
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)