Lists Home |
Date Index |
- From: John Cowan <email@example.com>
- To: XML Dev <firstname.lastname@example.org>
- Date: Tue, 04 May 1999 13:32:56 -0400
Joshua E. Smith wrote:
> I suppose that the validation should really be done a priori by the content
> developer using a validating editor, so doing validation in my plugin is
> really unnecessary. Is that true?
It depends on whether you are going to take action dependent on the
XML you get, in which case validating provides some (but not all)
of the sanity checks you will need. If you are just going to
display the content (or do something else that can't damage the
user or the client) then there is no real need.
> I assume it ignores external
> entities, right? That means I can't rely on putting boilerplate (think C
> #include files) into an external parsed general entity if I go with expat,
Correct. Other non-validating parsers do read external entities, though.
> If you were using a programming language which is XML-ish, what XML
> features would you be annoyed to see left out (substitution of entities is
> an obvious one, which I've seen 3DML slammed for)? Of those features,
> which does expat not do (and therefore I'll have to do in my application,
> or extend expat to do -- three cheers for open source!)?
Expat does everything except read external entities and validate.
Therefore, it doesn't read an external DTD, but it will process
attribute defaults and such from the internal DTD.
John Cowan http://www.ccil.org/~cowan email@example.com
You tollerday donsk? N. You tolkatiff scowegian? Nn.
You spigotty anglease? Nnn. You phonio saxo? Nnnn.
Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5)
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)