• To: "xml-dev@l..." <xml-dev@l...>
• Subject: Entity resolution vs. URI resolution
• From: Edwin Goei <edwingo@s...>
• Date: Tue, 22 Jan 2002 14:01:23 -0800

Hi, this posting is regarding an issue that was discussed on the
sax-devel list recently, but I think it deserves a larger audience since
it is not specific to SAX.

In SAX there is an entity resolver that takes a pair (publicID,
systemID) as input:
  InputSource resolveEntity(String publicID, String systemID)

For other standards (such as W3C XML Schema), there is a need to resolve
a schema location URI as a single input paramater:
  InputSource resolveURI(String locationURI)

One view is that "entity resolution" = "uri resolution" + "publicID
resolution".  So if only "uri resolution" is desired, pass "null" as the
publicID.

Another view is that these are two fundamentally different animals and
so two different resolvers should be used.

So should entity resolution and URI resolution go through the same
resolver or different ones?

I hope I captured the essence of the argument.  If not, please correct
me.

-Edwin

• Follow-Ups:
  • Re: Entity resolution vs. URI resolution
    • From: David Brownell <david-b@p...>
  • Re: Entity resolution vs. URI resolution
    • From: "Takuki Kamiya" <takuki@p...>
  • Re: Entity resolution vs. URI resolution
    • From: Norman Walsh <ndw@n...>

• Prev by Date: RE: Generality of HTTP
• Next by Date: Re: Generality of HTTP
• Previous by thread: Better Frameworks (WAS: RE: Being "precise" vs being "human")
• Next by thread: Re: Entity resolution vs. URI resolution
• Index(es):
  • Date
  • Thread