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

Tim Berners-Lee (timbl@www3.cern.ch)
Mon, 18 Oct 93 10:39:12 +0100

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Tim Berners-Lee: "Re: <'s for URLs"
- Previous message: Michael Mealling: "Re: URN: wrapper and URLs"
- Maybe in reply to: Michael Mealling: "The URN: wrapper and URLs..."
- Next in thread: Michael Mealling: "Summary of Re: URN wrappers and URL:"
- Reply: Michael Mealling: "Summary of Re: URN wrappers and URL:"

    Date: Mon, 18 Oct 93 10:39:12 +0100

    From: Tim Berners-Lee <timbl@www3.cern.ch>

    Message-Id: <9310180939.AA01330@www3.cern.ch>

    To: Kevin Gamiel <kgamiel@vinca.cnidr.org>

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

>Date: Sun, 17 Oct 1993 12:54:04 -0400 (EDT)
>From: Kevin Gamiel <kgamiel@vinca.cnidr.org>

[re: Adding "URL:" for "no good reason"...]

>No good reason? Do you want your parser to have to know _every_
protocol
>tag there is rather than just look for URL:?

Hold on. The URL: is not a wrapper to allow one to find
URLs.

> As protocols x,y,z,... begin
>using URLs do you want to rewrite your parser every time?

No no no. The parser parses the namespace field
and looks up in a table of known namespaces. It then
resorts to a known namespace handler (be it local
or remote) or a default (remote) one. No sweat.

> Its obviously
>not valid to say "I'll just ignore the ones I don't know"

Of couse not. You can store them, and if you
want to dereference them you can ask you
(library|kids|teacher) what they are. No rewriting.
Tim

- Next message: Tim Berners-Lee: "Re: <'s for URLs"
- Previous message: Michael Mealling: "Re: URN: wrapper and URLs"
- Maybe in reply to: Michael Mealling: "The URN: wrapper and URLs..."
- Next in thread: Michael Mealling: "Summary of Re: URN wrappers and URL:"
- Reply: Michael Mealling: "Summary of Re: URN wrappers and URL:"