Re: Attributes should only be there if part of the name/address space
Dan Connolly <connolly@w3.org> Fri, 21 February 1997 01:47 UTC
Received: from cnri by ietf.org id aa03406; 20 Feb 97 20:47 EST
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa28251; 20 Feb 97 20:47 EST
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id UAA16394 for uri-out; Thu, 20 Feb 1997 20:17:29 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with SMTP id UAA16389 for <uri@services.bunyip.com>; Thu, 20 Feb 1997 20:17:23 -0500 (EST)
Received: from mintaka.lcs.mit.edu by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA28190 (mail destined for uri@services.bunyip.com); Thu, 20 Feb 97 20:17:21 -0500
Received: from beach.w3.org by MINTAKA.LCS.MIT.EDU id aa26490; 20 Feb 97 20:15 EST
Message-Id: <330CF721.40E57757@w3.org>
Date: Thu, 20 Feb 1997 19:15:13 -0600
From: Dan Connolly <connolly@w3.org>
Organization: World Wide Web Consortium
X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.18 i586)
Mime-Version: 1.0
To: Larry Masinter <masinter@parc.xerox.com>
Cc: Daniel LaLiberte <liberte@ncsa.uiuc.edu>, uri@bunyip.com
Subject: Re: Attributes should only be there if part of the name/address space
References: <3.0.32.19970218151607.0080d4d0@hq.lcs.mit.edu> <199702201524.JAA11237@void.ncsa.uiuc.edu> <330C7650.6EF22561@w3.org> <330CB46B.FA8@parc.xerox.com> <199702202230.QAA22773@void.ncsa.uiuc.edu> <330CE7B4.18C21C9E@w3.org> <330CEB0F.26D@parc.xerox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-uri@bunyip.com
Precedence: bulk
Yeah... what he said. Larry Masinter wrote: > > This all got better for me when I just admitted that the > definitions were circular, and decided that it was OK. > > What's a resource? > Something that has a URI. > > What's a URL? > Something that locates a resource. > > What's a URN? > Something that names a resource. > > If you can name it, it's a resource. Different resources > have different names. A single resource might have > multiple names. You can't "get" a resource, you can > only interact with it. One way to interact with > a resource is to obtain an entity that is a representation > of the resource at a given point in time. > > This isn't smalltalk, it's webtalk. "Web" for me is > defined not by HTTP and HTML, but by this fundamental > architectural point, that some entities contain URIs > that locate/name other entities. > > Larry I suppose it's enough to say "same URL implies same resource" and that "different URL implies different resource" isn't useful or necessary. Dan
- Attributes should only be there if part of the na… Tim Berners-Lee
- Attributes should only be there if part of the na… Daniel LaLiberte
- Re: Attributes should only be there if part of th… Dan Connolly
- Re: Attributes should only be there if part of th… Larry Masinter
- Re: Attributes should only be there if part of th… Daniel LaLiberte
- Re: Attributes should only be there if part of th… Dan Connolly
- Re: Attributes should only be there if part of th… Larry Masinter
- Re: Attributes should only be there if part of th… Dan Connolly
- Re: Resources and Identifiers Dan Connolly
- Re: Resources and Identifiers Michael Mealling
- Resources and Identifiers Daniel LaLiberte
- Re: Resources and Identifiers Daniel LaLiberte