# Re: The URN: wrapper and URLs...

Marc Andreessen (marca@ncsa.uiuc.edu)
Fri, 15 Oct 93 07:36:00 -0700

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Michael Mealling: "Re: The URN: wrapper and URLs..."
- Previous message: Tim Berners-Lee: "Re: The URN: wrapper and URLs..."
- In reply to: Peter Deutsch: "Re: The URN: wrapper and URLs..."
- Next in thread: Tim Berners-Lee: "Re: The URN: wrapper and URLs..."

    Date: Fri, 15 Oct 93 07:36:00 -0700

    From: marca@ncsa.uiuc.edu (Marc Andreessen)

    Message-Id: <9310151436.AA01835@wintermute.ncsa.uiuc.edu>

    To: Peter Deutsch <peterd@bunyip.com>

    Subject: Re: The URN: wrapper and URLs...

    In-Reply-To: <9310142250.AA13164@expresso.bunyip.com>

Peter Deutsch writes:
> [ Simon wrote: ]
>
> > One idea that I've been wondering about, and can't remember if we discussed
> > or not was making a URN have the same syntax as a URL (e.g. have a special
> > URL type, URN, and having a URN be <URN://AUTHORITY:PUBLISHER::NUMBER>
>
> God forbid that we should preserve that ridiculous and
> unnecessary double-/ syntax in the URNs as well! I don't
> object to making it optional to avoid breaking previous
> code, but it's such a blatant hack that it really offends
> my sense of artistic balance no end... :-(
>
> Having vented my spleen on such a minor topic, my vote on
> the topic of consistent wrapping would be to make the
> <UR*:[opaque string] > format the standard for the whole
> family.

Conspicuously missing from your counter-proposal is a mechanism by
which a client knows where to go to locate (or dereference) the
resource. Could you elaborate?

Marc

- Next message: Michael Mealling: "Re: The URN: wrapper and URLs..."
- Previous message: Tim Berners-Lee: "Re: The URN: wrapper and URLs..."
- In reply to: Peter Deutsch: "Re: The URN: wrapper and URLs..."
- Next in thread: Tim Berners-Lee: "Re: The URN: wrapper and URLs..."