W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 1996

RE: Seiwald Q & A -- "GET for EDIT" cookies

From: Yaron Goland <yarong@microsoft.com>
Date: Wed, 4 Sep 1996 11:45:58 -0700
Message-ID: <c=US%a=_%p=msft%l=RED-44-MSG-960904184558Z-27680@mail2.microsoft.com>
To: "'w3c-dist-auth@w3.org'" <w3c-dist-auth@w3.org>, "'www-vers-wg@ics.UCI.EDU'" <www-vers-wg@ics.UCI.EDU>, "'David G. Durand'" <dgd@cs.bu.edu>
Sorry I should have been more clear. Please refer to my requirements
sheet (the relevant section of which I have included below).
1.7 Link
Links are needed for a variety of reasons including associating the
pre-processed and processed versions of files and establishing shadow
directories. Links are especially important in finding the 'source'
version of a file. In some cases, such as an HTML file with Server Side
Includes, the relationship between the source and presentation files is
straight forward. However there are other cases, such as in computer
programs which have an executable, one or more object files, and then
source code files, where the chain between first document and final
presentation contains many links. Rather than trying to hack a "GET for
Edit" solution, links allow us to gracefully solve the document
relationship problem. 
The variety of values one would want to associate with a link are
numerous and argue that links should be made into first class objects. A
tag would be added to the HTTP header of an entity indicating the URLs
of any associated links. The format of a link URL should be equal to the
URL of the requested entity with appropriate tags, indicating link type,
appended to the end. The client would then request the links using a
normal GET. The bodies of the replies would contain whatever information
was relevant to the link.
In order to ease administration it is also possible that each linked
entity will have a special link URL associated with it that will act as
a directory to all the links attached to this entity.
A PUT with appropriate tags should be used to associate a link body with
one or more URLs. Note that there is no restriction on the number of
files to which a link URL may be attached.

>From: 	David G. Durand[SMTP:dgd@cs.bu.edu]
>Sent: 	Tuesday, September 03, 1996 9:07 PM
>To: 	w3c-dist-auth@w3.org; www-vers-wg@ics.UCI.EDU
>Subject: 	RE: Seiwald Q & A -- "GET for EDIT" cookies
>At 7:10 PM 9/3/96, Yaron Goland wrote:
>>Talking about dead horses... When people say things like "Check Out the
>>Source" I get worried. As I mentioned previously there are cases where
>>the number of links between the final version of an entity and the
>>original version contains many nodes. Rather than trying to put together
>>a "GET for Edit" which will either only have one level and thus is not
>>very useful or will hack the hell out itself to support more levels we
>>should just support links which solve the problem very elegantly.
>>					Yaron
>   I'm afraid I'm a casualty of nomenclature here. What's a link in this
>context? An ancestor? A set of derivation relationships and intermediate
>states? or some other semantic relationship?
>   -- David
>David Durand                  dgd@cs.bu.edu | david@dynamicDiagrams.com
>Boston University Computer Science          | Dynamic Diagrams
>http://www.cs.bu.edu/students/grads/dgd/    | http://dynamicDiagrams.com/
Received on Thursday, 5 September 1996 13:11:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:13 UTC