Re: URN to URC scenario

Michael Mealling (ccoprmm@oit.gatech.edu)
Tue, 22 Feb 94 19:27:28 EST

From: ccoprmm@oit.gatech.edu (Michael Mealling)
Message-Id: <199402230027.AA13921@oit.gatech.edu>
Subject: Re: URN to URC scenario
To: M.T.Hamilton@lut.ac.uk (Martin Hamilton)
Date: Tue, 22 Feb 94 19:27:28 EST
In-Reply-To: <199402221210.MAA01511@lust.mrrl.lut.ac.uk>; from "Martin Hamilton" at Feb 22, 94 12:10 pm

Martin Hamilton said this:
> $ Client->Server: Template=URC;URN="urn:xxx/yyy:ABCD123456"
> $
> $ Server->Client: URN: urn:xxx/yyy:ABCD123456
> $ Author: Mitra <mitra@path.net>
> $ URL: gopher://path.net/00/papers/mitra/urn2urc
> $ Format: Text/plain
> $ URL: ftp://path.net/pub/docs/urn2urc.ps
> $ Format: Application/postscript
>
> In the context of the TXT RR method of discovering URN->UR* servers,
> I don't think it matters much whether the eventual URN lookup returns
> URCs or URLs.

You are right. It doesn't because a URL is just a URC with only one element
in it the same way a URN is just a short URC as well.

> A smart client could use the URC info, and a dumb one could just pick out
> the URLs.

EXACTLY!

> How does that sound?

-- 
------------------------------------------------------------------------------
Michael Mealling                     ! Hypermedia WWW, WAIS, and gopher will be
Georgia Institute of Technology      ! here soon via MIME. Your view of the 
Michael.Mealling@oit.gatech.edu      ! internet is about to change completely!