Lists Home |
Date Index |
- From: Tyler Baker <firstname.lastname@example.org>
- To: Bill la Forge <email@example.com>
- Date: Thu, 11 Feb 1999 00:43:15 -0500
Bill la Forge wrote:
> From: Simon St.Laurent <firstname.lastname@example.org>
> >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.
> We've been continuing our effort to add filters to MDSAX and in the process
> ran into a small problem--the runtime was loading all the filters specifiec in the context
> boot document. The next release fixes this, so that only the filters actually being
> used get loaded.
> Anyway, the point here is that a reasonable approach to dynamic configuration
> should give you a very small footprint when only selected features are used.
> This in contrast to a does-everything monolithic parser. And as the specs
> mature, it seems likely that the larger companies represented at the W3C
> have no reason at all to keep the specs small and lightweight--cumbersom
> specs nicely eliminates much of the competition!
> So it seems the choice is clear... expect your parsers to grow till they have more
> features than MS Word, or take a configurable approach which allows the developer
> to select the capabilities necessary for the job at hand.
Sad but true, but this is not the parser writer's fault as we are almost completely obligated
to support everything in a W3C recommendation to call ourselve's compliant. I am wondering if
you will be able to call an XML framework compliant if it elects to omit namespaces support or
any future technical headache that is thrown at us developers.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)