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

Re: SAX Locator vs {start,end}Entity

• To: <michael.h.kay@n...>,"'Richard Tobin'" <richard@c...>,<xml-dev@l...>
• Subject: Re: SAX Locator vs {start,end}Entity
• From: "Jeff Rafter" <jeffrafter@d...>
• Date: Thu, 20 Feb 2003 08:40:03 -0600
• References: <000601c2d8e6$88da49c0$6401a8c0@pcukmka>

> Why do you need to monitor the startEntity and endEntity events to get
> the base URI? Saxon simply asks the Locator for the systemId when
> startElement is reported (or processingInstruction, or an unparsed
> entity declaration), and this seems to give the right answer.

This might be because SAXON uses AElfred2 by default. Dave Brownell was very
concerned with base URIs, especially in later versions of AElfred2. There is
even a warning fired when the base URI cannot be determined ("must be
absolute") So I am not sure if this would be indicative of all parsers...
one could argue that AElfred2 is generally "right" on these kinds of things
and that checking the locator on event callback is a Good Thing.

Cheers,
Jeff Rafter
Defined Systems
http://www.defined.net
XML Development and Developer Web Hosting

• References:
  • RE: SAX Locator vs {start,end}Entity
    • From: "Michael Kay" <michael.h.kay@n...>

• Prev by Date: RE: SAX Locator vs {start,end}Entity
• Next by Date: Re: SAX Locator vs {start,end}Entity
• Previous by thread: RE: SAX Locator vs {start,end}Entity
• Next by thread: Re: SAX Locator vs {start,end}Entity
• Index(es):
  • Date
  • Thread