Lists Home |
Date Index |
- From: james anderson <James.Anderson@mecomnet.de>
- To: email@example.com
- Date: Wed, 03 Nov 1999 11:53:33 +0100
David Brownell wrote:
> It's a simple extension of what I showed above:
> <!DOCTYPE foo [
> <!ENTITY % MathML SYSTEM "http://www.example.com/MathML.dtd">
> <!ENTITY % SpeechML SYSTEM "http://www.example.com/SpeechML.dtd">
> I'd encourage you to use PUBLIC identifiers as well, so that
> local cached copies of those declarations can easily be used.
Could someone expound further on this statement?
I recall only that the rec says something about permitting a processor to use
the public identifier to generate an alternative URI to the system identifier
to be used to retrieve an external resource.
Is the "customary usage", in fact, that processors use the public identifier
to name an entry in a local and/or process-specific cache? which they manage dynamically?
I wonder this also because I've yet to see a conclusive discussion of whether
dtd's (or for that matter schema) in the namespace age are stable. That is,
whether the same system uri will always identify an identical dtd/schema.
For example, would a processor be conforming if it were to, upon not finding a
resource "under" a public identifier, retrieve and expand the resource located
through the system identifier and cache the expanded (or even decoded result)
"under" the public identifier?
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)