Re: URL semantics
Daniel LaLiberte <liberte@ncsa.uiuc.edu> Fri, 10 January 1997 03:38 UTC
Received: from cnri by ietf.org id ad06292; 9 Jan 97 22:38 EST
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa25742; 9 Jan 97 17:31 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id RAA29394 for uri-out; Thu, 9 Jan 1997 17:04:20 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id RAA29386 for <uri@services.bunyip.com>; Thu, 9 Jan 1997 17:04:18 -0500
Received: from sdgmail.ncsa.uiuc.edu by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA06406 (mail destined for uri@services.bunyip.com); Thu, 9 Jan 97 17:04:16 -0500
Received: from void.ncsa.uiuc.edu (void [141.142.103.20]) by ncsa.uiuc.edu (8.8.2/8.8.2) with ESMTP id QAA08808; Thu, 9 Jan 1997 16:03:29 -0600 (CST)
From: Daniel LaLiberte <liberte@ncsa.uiuc.edu>
Received: (from liberte@localhost) by void.ncsa.uiuc.edu (8.8.2/8.8.2) id PAA13003; Thu, 9 Jan 1997 15:59:13 -0600 (CST)
Date: Thu, 09 Jan 1997 15:59:13 -0600
Message-Id: <199701092159.PAA13003@void.ncsa.uiuc.edu>
To: Dave Lewis <drlewi1@srv.pacbell.com>
Cc: uri@bunyip.com
Subject: Re: URL semantics
In-Reply-To: <9701092003.AA21704@pop.srv.PacBell.COM>
References: <9701092003.AA21704@pop.srv.PacBell.COM>
Sender: owner-uri@bunyip.com
Precedence: bulk
Dave Lewis writes: > If one GETs the resource 'telnet: invoked session' it results in a > session - no problem. If one 'GETs a 'mailto: invoked interaction' one > achieves the result that an interaction occurs (one gets an interaction) - > no problem. I could live with this use of GET, but I'm afraid we might be GETting in trouble because of the strong association to getting an object rather than invoking an interaction. "DO" might be better. > I fully agree. The URL (or URI) identifies a resource onto which > application of a certain set of methods will make sense. Right. And some of the applicable methods might not do anything at all with the identified resource or its associated server. For example, to get a content rating for a resource, you would probably go somewhere else. (Note: In an important sense, the URL identifies the content rating when you use it to interact with a service that provides content ratings.) > GET works for me if we view identified resources as such. In this > fashion it currently acts as a sort of universally applicable method. > Should there be a set of universally applicable methods? Yes, if only > to retrieve info on the set of methods applicable to an identified > resource. That is, as we increasingly see a unique set of methods > applicable for any given URI identified resource, we should introduce > means of learning the nature of these sets. We will probably never have a universal set of methods across all URI schemes. Maybe we will for all resources identified within some particular scheme. But the universal methods you are suggesting for discovering the other methods are really at a meta-level, and it is questionable whether these are methods on the resource itself or on some meta-resource, such as a collection or server. Maybe this distinction doesn't really matter, but then where *is* the resource if we can interact with many different services to get partial information about the resource? > [...] In certain context the semantics are extended, overloaded, > or (yuk) overridden. This doesn't appear to me to warrant throwing out > the notion of universal method but does suggest documenting both the > intended semantics as well as nature of process by which they may be > modified in context. I'm fine with defining *intended* semantics, but I think it is important to realize that there *can be no limit* to the alternative semantics that clients might impose on a URI. Clients can do whatever they want as long as they can find some server that will talk with them. And there will be several reasonable alternative semantics and associated services created and used widely, such as content rating services. dan
- Re: URL semantics Dave Lewis
- Re: URL semantics Larry Masinter
- Re: URL semantics Daniel LaLiberte
- Re: URL semantics Gregory J. Woodhouse
- Re: URL semantics Tim Berners-Lee
- Re: URL semantics Daniel LaLiberte
- Re: URL semantics Tim Berners-Lee
- Re: URL semantics Larry Masinter
- Re: URL semantics Fisher Mark
- Use Web to launch apps (was Re: URL semantics) Zheng Wang