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

Re: Entity resolution vs. URI resolution

• To: Edwin Goei <edwingo@s...>, xml-dev@l...
• Subject: Re: Entity resolution vs. URI resolution
• From: David Brownell <david-b@p...>
• Date: Fri, 25 Jan 2002 10:11:13 -0800
• References: <3C4DE133.21C45105@s...>

The base issue on SAX-devel was whether SAX should be
including support for functionality that's clearly not required
to support "core XML" (XML 1.0 + namespaces) ... and
which, in cases where it's desirable (there was argument
that the answer is "never") is easily/naturally layered.


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

That presupposes that they are different things.  Let me put
it to you this way:  when would it lead to anything other than
confusion to resolve a URI http://xml.example.com/foo in
two different ways depending on whether it was used as
the SYSTEM id for an entity, or something else?

I'll also point out that "resolve" is a vague word.  Sometimes
it means just turning text into more absolute URI, while in other
cases it involves fetching the content -- perhaps with some
particular set of constaints like "accepts PNG not GIF".  So
this question is posed in a rather vague manner.

- Dave

• Follow-Ups:
  • Re: Entity resolution vs. URI resolution
    • From: Edwin Goei <edwingo@s...>
  • Re: Entity resolution vs. URI resolution
    • From: John Cowan <cowan@m...>

• References:
  • Entity resolution vs. URI resolution
    • From: Edwin Goei <edwingo@s...>

• Prev by Date: Re: New W3C Patent Practice
• Next by Date: Re: Revised Internet-Draft: Media Feature - xmlns
• Previous by thread: Re: Entity resolution vs. URI resolution
• Next by thread: Re: Entity resolution vs. URI resolution
• Index(es):
  • Date
  • Thread