Lists Home |
Date Index |
- From: "Michael Champion" <Mike.Champion@softwareag-usa.com>
- To: <firstname.lastname@example.org>
- Date: Wed, 17 Nov 1999 19:25:32 -0500
----- Original Message -----
From: David Megginson <email@example.com>
Sent: Wednesday, November 17, 1999 5:55 PM
Subject: XML Memory Requirements (was Re: Feeling good about SML)
Thanks for such an informative posting!
> Again, the big problem in creating a tiny XML processor is the
> required error reporting for illegal characters in names, attribute
> values, etc. -- if you build lookup tables, you're looking at an
> enormous amount of memory for each table.
Could you elaborate a bit here for the benefit of those of us who are not
familiar with the finer points of the XML spec with respect to "illegal
characters in names, attribute values, etc."
More procedurally, let's say for the sake of argument that one were
designing an XML-like metalanguage with the goal of making its processors as
small and fast as possible. Are there plausible ways of loosening XML's
"required error reporting" to make it easier to write parsers without big
Again, this is the voice of inexperience speaking so be merciful if I'm
missing something obvious ... but in an "SML" without entities, attributes,
PIs, and comments, and without any concern for maintaining SGML
compatibility, I can't think of too many printable characters besides "<"
">" and maybe " " that *have* to be illegal in element names. I can think of
a lot of characters that sensible people probably would not put in their
markup, but that's another matter, and arguably not the job of the SML
parser to enforce.
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 unsubscribe, 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)