# Re: URN to URC resolution scenario

Larry Masinter (masinter@parc.xerox.com)
Fri, 12 Nov 1993 00:02:34 PST

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Mitra: "Re: URN to URC resolution scenario"
- Previous message: Mitra: "New list IETF-TYPES@SERVER.PATH.NET"

    To: mitra@path.net

    In-Reply-To: mitra@path.net's message of Wed, 3 Nov 1993 16:48:59 -0800 <93Nov3.164912pst.2795@golden.parc.xerox.com>

    Subject: Re: URN to URC resolution scenario

    From: Larry Masinter <masinter@parc.xerox.com>

    Message-Id: <93Nov12.000239pst.2795@golden.parc.xerox.com>

    Date: 	Fri, 12 Nov 1993 00:02:34 PST

Mitra's scenario brings a question to mind:

Don't you think it is likely that different kinds of URNs will have
different URN to URL resolution mechanisms? You'll use a different
method to find something that's identified by its ISBN number than
something that's identified by it's news message-ID.

E.g., for an ISBN number, you'll check your shelves, your local
library, a close bookstore, and finally, if you can't find it anywhere
else, the library of congress.

For a news identifier, you might check your local news server, a
couple of the net CDROM authorities, and some of the netnews archive
sites.

For an RFC document, you'd check the various document repositories.

You don't want to build the URN -> URL resolution method into the
design of URN, do you?

I've not been taking the 'authority' part of 'naming authority'
seriously. It's more the 'naming style', isn't it?

- Next message: Mitra: "Re: URN to URC resolution scenario"
- Previous message: Mitra: "New list IETF-TYPES@SERVER.PATH.NET"