Lists Home |
Date Index |
- From: "Simon St.Laurent" <firstname.lastname@example.org>
- To: John Cowan <email@example.com>, XML Dev <firstname.lastname@example.org>
- Date: Fri, 12 Mar 1999 15:24:32 -0500
At 02:33 PM 3/12/99 -0500, John Cowan wrote:
>No, it doesn't. An NVP is privileged to not read any and all external
>entities with the sole exception of the document entity, which it
>In practice, however, I suspect that all NVPs fall into one of the
>following four classes:
>1) Read only the document entity.
>2) Read the whole DTD but no external general entities.
>3) Read all external general entities, but only process
>the internal DTD subset.
>4) Read all external entities (except unparsed entities).
I think 4 should read:
4) Read the document, the internal subset, the external subset, and all
external entities except unparsed entities.
(In my experience with Aelfred, that's what it does, though I'll admit to
not actually using entities in 'real' practice.)
I guess the question comes down to whether your interpretation of current
practice is reason enough to combine the external subset and external
entities in this situation. Given the point Sean McGrath just raised about
things (INCLUDE/IGNORE, but also certain kinds of PE processing) that are
legal in the external DTD subset but not in the internal subset or external
PEs referenced from the internal subset, I'd say to keep these things
Of course, we could create a feature that simply referred to external
resources, combining both properties, on top of the external PEs/external
subset features. Might be the best of all worlds, though it would take
some clear documentation identifying what happened if you used both the
convenience feature and its sub-parts.
XML: A Primer / Building XML Applications (April)
Sharing Bandwidth / Cookies
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)