Lists Home |
Date Index |
- From: Leigh Dodds <email@example.com>
- To: Sebastien Sahuc <firstname.lastname@example.org>, email@example.com
- Date: Tue, 16 Nov 1999 10:46:22 -0000
> but I would like to have a summary of WHEN and WHEN NOT to use
> external entities.
> I sum up some points I have understood so far :
> * DO NOT use external entities when working with remote XML document
> since it would badly increase downloading time.
> * DO use them only when you can rely on the parser's behaviour, i.e.
> you know exactly how the parser will behave with these entities.
> Any comments on this ?
Heres some others, gleaned from the discussions:
"The *ONLY TIME* external parsed entities are the right thing to do is
when exactly one actor is working on exactly one doucment and needs to
partition it into separate files for *their own* convenience. *AT ALL
OTHER TIMES* external parsed entities are not the right thing to use."
Use them to separate the logical and physical document structure
Never rely on data being stored in a specific entity
(above link, last paragraph, see also
I'm sure there are other wise words to be added as well!
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)