Message-Id: <9310170357.AA15283@expresso.bunyip.com>
From: Peter Deutsch <peterd@bunyip.com>
Date: Sat, 16 Oct 1993 23:57:26 -0400
In-Reply-To: Erik Ostrom's message as of Oct 16, 11:27
To: eostrom@gac.edu (Erik Ostrom), ses@tipper.oit.unc.edu (Simon E Spero)
Subject: Re: The URN: wrapper and URLs...
[ You wrote: ]
> > Breaking existing code for cosmetic reasons is truly the ISO way.
>
> Just for review, could someone explain to me what existing code we're
> talking about breaking (that wouldn't be broken by the inclusion of
> URNs anyway)?
. . .
> By "picking up" I mean something like "My web-aware newsreader should
> be able to scan through a plaintext Usenet article, spot strings like
> URL:http://jhm.ccs.neu.edu:7043/, and mark those as links to be
> followed." You probably don't want to flag everything beginning with
> some letters and then a colon; you also probably don't want your news
> scanner to have to know about every kind of URL scheme (updating as
> new ones are added). Encapsulation issue, I guess.
Thank you! This is to me the first practical example of
what I was struggling to define as future functionality.
Yes, there will come a time when we want to pick both URNs
and URLs out of text for automatic processing (whether it
be for a hypertext news reader or an automatic resource
discovery tool). I think this is a strong argument in
favour of the prefix for both puppies.
For this reason I must vote against Simon's proposed
motion.
- peterd
--