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

Re: Entity resolution vs. URI resolution

• To: xml-dev@l...
• Subject: Re: Entity resolution vs. URI resolution
• From: Norman Walsh <ndw@n...>
• Date: Thu, 24 Jan 2002 13:58:43 -0500
• In-reply-to: <p04330103b875c12489c5@[192.168.254.4]> (Elliotte RustyHarold's message of "Thu, 24 Jan 2002 08:53:47 -0500")
• References: <3C4DE133.21C45105@s...> <878zaphx6q.fsf@n...><p04330103b875c12489c5@[192.168.254.4]>
• Sender: Norman Walsh <ndw@mercury>
• User-agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 (i686-pc-linux-gnu)

/ Elliotte Rusty Harold <elharo@m...> was heard to say:
| At 11:03 AM -0500 1/23/02, Norman Walsh wrote:
|
|>I maintain that adding a resolveURI(uri, baseURI) method to the SAX
|>API is "the right thing".
|>
|
| While this is important I just can't see any reason to put this in SAX
| instead of in java.net. In fact, I think this constructor probably

Yeah, well, getting SAX updated is probably slightly easier than
getting java.net changed :-)

| offers exactly the functionality you're looking for:
|
| public URL(URL context,
|             String spec)
|      throws MalformedURLException

Uhm. I'm confused. That'll return the stream, but I actually want the
URI to be passed through *the resolver* (for example XML Catalogs[1])
not blindly slurped across the net.

I want an entry point to do for URIs what resolveEntity() does for
external identifiers. And I maintain that calling a URI a system
identifier with a null public identifier is wrong.

                                        Be seeing you,
                                          norm

[1] http://www.oasis-open.org/committees/entity/spec.html
-- 
Norman.Walsh@S...   | One stops being a child when one realizes that
XML Standards Engineer | telling one's trouble does not make it
XML Technology Center  | better.--Cesare Pavese
Sun Microsystems, Inc. | 

• Follow-Ups:
  • Re: Entity resolution vs. URI resolution
    • From: Elliotte Rusty Harold <elharo@m...>

• References:
  • Entity resolution vs. URI resolution
    • From: Edwin Goei <edwingo@s...>
  • Re: Entity resolution vs. URI resolution
    • From: Norman Walsh <ndw@n...>
  • Re: Entity resolution vs. URI resolution
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Re: Strategies for a lowly XML document
• Next by Date: Modeling relationships in XML
• Previous by thread: Re: Entity resolution vs. URI resolution
• Next by thread: Re: Entity resolution vs. URI resolution
• Index(es):
  • Date
  • Thread