Lists Home |
Date Index |
I consider systemId parameter in resolveEntity to be
something quite different from targetNamespace URI used
for schema-resolution. To me, targetNamespace URI sounds
more like publicID, but I guess the they have different patterns
so we cannot safely make them co-exist in one parameter.
The other solution you indicated, which is to have
resolveURI(String locationURI) sounds more right to me,
assuming if it fails, resolveEntity is then invoked with
systemId being location hint (as in schema resolution) if
there is location information any available.
To some applications, we may need to provide another URI
to distinguish what type of resource the resolver is supposed
to resolve (XML Schema vs. WSDL). In that case resolveURI
would look like: resolveURI(String resourceTypeURI, String resourceNameURI).
----- Original Message -----
From: "Edwin Goei" <email@example.com>
Sent: Tuesday, January 22, 2002 2:01 PM
Subject: [xml-dev] Entity resolution vs. URI resolution
> 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
> 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
> 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>