[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Full Disclosure: What The XML Processor Must Tell The XML Applicatio

• From: John Cowan <cowan@l...>
• To: XML Dev <xml-dev@i...>
• Date: Fri, 06 Nov 1998 09:55:57 -0500

david@m... wrote:

>  > 10. An XML processor (necessarily a non-validating one) that does
>  > not include the replacement text of an external parsed entity
>  > in place of an entity reference must notify the application that
>  > it recognized but did not read the entity (4.4.3)  [SAX does not
>  > provide for this]
> 
> SAX offloads this responsibility to the application using the
> EntityResolver interface.

But there's no way for the application to tell the parser
"Don't read this entity."  Returning an InputSource on the null
string is similar, but not identical, in effect.

-- 
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...>
  • Full Disclosure: What The XML Processor Must Tell The XML Application
    • From: <david@m...>

• Prev by Date: Re: Namespaces - defaulting question (re:WD-xml-names19980916)
• Next by Date: Storing XML documents in an OODB
• Previous by thread: 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