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

Re: SAX2 ... missing features?

• From: David Brownell <david-b@p...>
• To: Rob Lugt <roblugt@e...>, xml-dev@l...
• Date: Fri, 13 Jul 2001 11:05:59 -0700

> * DTDInputSource
> An application can set this property to provide a DTD.  This will override
> the document's DTD (if it exists) but, more importantly, will create one if
> it doesn't.
> 
> Currently applications can use an EntityResolver to achieve this, but only
> when the input document references an external DTD.  This will allow
> applications to inject a DTD regardless.

This one is interesting because it clearly can't be layered:  swapping DTDs
means changing entity and attribute declarations, which affect the view of
content produced by parsing the body.

Though I don't think "InputSource" is the right model, since it doesn't
support use of internal subsets ... used for many parameterized or
modularized DTDs.  One really wants the three components of a
DTD:  root name decl, "external subset" system ID (and maybe public
ID), and internal subset.

- Dave

• Follow-Ups:
  • Re: SAX2 ... missing features?
    • From: Rob Lugt <roblugt@e...>

• References:
  • SAX2 ... missing features?
    • From: David Brownell <david-b@p...>
  • Re: SAX2 ... missing features?
    • From: Rob Lugt <roblugt@e...>
  • Re: SAX2 ... missing features?
    • From: Rob Lugt <roblugt@e...>

• Prev by Date: Re: Just a Little Explanaton for Veering (RE: Blueberry/Unicode/ XML)
• Next by Date: RE: Well-formed Blueberry
• Previous by thread: Re: SAX2 ... missing features?
• Next by thread: Re: SAX2 ... missing features?
• Index(es):
  • Date
  • Thread