[Sax-devel] [Fwd: [xml-dev] Entity resolution vs. URI resolution]

[Edwin G. <ed...@su...>]

This thread was recently disucussed on sax-devel, but I think the topic
is broader than SAX so I posted a summary to xml-dev.  I originally
forgot to cc: sax-devel.  Please comment if I did not capture the
essential points of the discussion.

-Edwin

-------- Original Message --------
Subject: [xml-dev] Entity resolution vs. URI resolution
Date: Tue, 22 Jan 2002 14:01:23 -0800
From: Edwin Goei <ed...@su...>
To: "xm...@li..." <xm...@li...>

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

-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>