• From: John Cowan <cowan@l...>
• To: XML Dev <xml-dev@i...>
• Date: Thu, 12 Nov 1998 15:18:39 -0500

Paul Prescod scripsit:

> I think David agrees with me that XML processors do not have enough
> information to make the decision about whether entity references should be
> expanded or not.

What about an XML processor that (as a part of its design) never expands
external entity references?

For example, one might want to have an ultrafast XML processor that
works only from a string input source and can therefore operate
in embedded environments.  It cannot have a SAX interface as SAX
is currently defined without violating XML 1.0.

-- 
John Cowan	http://www.ccil.org/~cowan		cowan@c...
	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:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • Full Disclosure: What The XML Processor Must Tell The XML Application
    • From: John Cowan <cowan@l...>
  • Re: Full Disclosure: What The XML Processor Must Tell The XML Application
    • From: Paul Prescod <papresco@t...>

• Prev by Date: Re: Open-source licensing (was: XLink library)
• Next by Date: Re: using xml/xsl/dom together
• Previous by thread: Re: Full Disclosure: What The XML Processor Must Tell The XML Application
• Next by thread: Re: Full Disclosure: What The XML Processor Must Tell The XML Application
• Index(es):
  • Date
  • Thread