Re: URL attributes
JC Touvet <Jean-Christophe.Touvet@inria.fr> Wed, 17 November 1993 17:20 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07681;
17 Nov 93 12:20 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07677;
17 Nov 93 12:20 EST
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa14929;
17 Nov 93 12:20 EST
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP
id <g.06506-0@haig.cs.ucl.ac.uk>; Wed, 17 Nov 1993 17:08:42 +0000
Received: from concorde.inria.fr by bells.cs.ucl.ac.uk with Internet SMTP
id <g.00291-0@bells.cs.ucl.ac.uk>; Wed, 17 Nov 1993 17:08:23 +0000
Received: from nuri.inria.fr by concorde.inria.fr;
Wed, 17 Nov 1993 18:08:20 +0100
Received: from localhost.inria.fr by nuri.inria.fr;
Wed, 17 Nov 1993 18:08:49 +0100
Message-Id: <199311171708.AA12134@nuri.inria.fr>
To: Martijn Koster <m.koster@nexor.co.uk>
Cc: pays@faugeres.inria.fr, osi-ds@cs.ucl.ac.uk
Subject: Re: URL attributes
In-Reply-To: <199311171156.AA17544@concorde.inria.fr>
Date: Wed, 17 Nov 1993 18:08:48 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: JC Touvet <Jean-Christophe.Touvet@inria.fr>
> To: JC Touvet <Jean-Christophe.Touvet@inria.fr> > Cc: Martijn Koster <m.koster@nexor.co.uk>uk>, pays@faugeres.inria.fr, > osi-ds@cs.ucl.ac.uk > Subject: Re: URL attributes > In-Reply-To: Your message of "Wed, 17 Nov 1993 11:40:55 +0100." <199311171040.AA14669@nuri.inria.fr> > Date: Wed, 17 Nov 1993 11:56:00 +0000 > From: Martijn Koster <m.koster@nexor.co.uk> > > > JC Touvet <Jean-Christophe.Touvet@inria.fr> wrote: > > > > > Date: 16 Nov 93 20:05:10+0000 > > > From: Martijn Koster <m.koster@nexor.co.uk> > > > > > > As you say URL's can point to anything. Why then explicitly type them by > > > calling them VideoURL etc? > > > > You're obsolutely right, and that's why we've made a "PlainURL" attribute > > type, where you can find any kind of URL. > > Yes, but why bother with the specific ones at all? I don't think they are > really needed, as you can have a description "A picture of Earth" indicating > what sort of animal is at the other end of a link. > > I don't think setting up yet another typing system is a good idea; > that is an issue for the URI (as in gopher URLs) and the negotiation in the > transfer protocol (eg HTTP's Accept: field). Where do you draw the line: > CVUrl, ASCIIUrl, WordPerfectUrl...? > I agree, but we'll keep for instance those attributes in order to maintain compatibility with some X500 lookup procedures which actually respond to requests like: retreive Someone's Photo or retreive Someone's Voice If we keep only "raw" URLs in the Directory, that will be somehow difficult to parse. > > Try: http://perignon.inria.fr:2200/htbin/x500person/C=fr;O=inria?touvet > > Nice :-) > > -- Martijn Thanks again. Since this morning, we've changed a bit our interface, and made links to our WWW/WAIS server for each people entry in the INRIA Directory, depending on their Research Unit. Best regards, -JCT-
- URL attributes pays
- Re: URL attributes Martijn Koster
- Re: URL attributes pays
- Re: URL attributes JC Touvet
- Re: URL attributes Martijn Koster
- Re: URL attributes JC Touvet
- Re: URL attributes Erik Huizer (SURFnet BV)
- Re: URL attributes pays
- Re: URL attributes Marshall Rose
- Re: URL attributes Steve Kille
- Re: URL attributes pays