- From: Gregory J. Woodhouse <gjw@wnetc.com>
- Date: Thu, 31 Oct 1996 05:47:06 -0800 (PST)
- To: Yaron Goland <yarong@microsoft.com>
- cc: "'Daniel W. Connolly'" <connolly@beach.w3.org>, "'Jim Whitehead'" <ejw@rome.ICS.UCI.EDU>, "'w3c-dist-auth@w3.org'" <w3c-dist-auth@w3.org>
On Wed, 30 Oct 1996, Yaron Goland wrote: [...] > No we mean representation(s), meaning one or more than one representations > of a resource. Where representation is defined as in HTTP 1.1. > Should it be made explicit that it might be necessary to edit different representations of the same reource separately? > representation > An entity included with a response that is subject to content > negotiation, as described in section 12. There may exist multiple > representations associated with a particular response status. > Actually, an entity only exists in the context of an HTTP message, but the representation has an existence independent of any such messages. > The key here is that we are not just talking about an entity, we are > talking about a content negotiated entity. I have removed all references to > entity and replaced them with representation. > You mean negotiable representation of a resource. I know I'm being pedantic but entities are parts of messages. > Of edit and update, pick one. > > So I think it should say "... no longer intends to update a resource." > > Update is a loaded term. I prefer edit. I have modified the draft to use > edit. > That's probably better. I think of update as a database operation. [...] > >merge > > A merge is the process whereby a resource represented by one URI is > > combined with a resource represented by a second URI. Merges can > occur > > at the client or the server. > > @@hmmm... > > merge > A merge is the process whereby information from one or more resources is > used to produce a new resource that represents the content of the component > resources. Merges can occur at the client or the server. > I think of merge as an asymmetric operation which does not produce a new resource (though a new version o an existing resource). To illustate, if A and B are tables with the same scheme, mergeing B into A replaces A with a table containing all relations present in either A or B. This would be different from a JOIN which would produce an entirely new table. [...] > > >server diff > > A server diff is a mechanism whereby the server compares two or more > > representations, and sends the client a message containing a summary > of > > the differences between the entities. > > s/representations/entities/. > No. Representations exist on the server. Entities are returned in messages. > server diff > A server diff is a mechanism whereby the server compares two or more > representations and sends the client a message containing the differences. > > [...] --- Gregory Woodhouse gjw@wnetc.com home page: http://www.wnetc.com/ resource page: http://www.wnetc.com/resource/
Received on Thursday, 31 October 1996 08:53:06 UTC