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

Re: Fielding on MOVE & COPY

From: Judith Slein <slein@wrc.xerox.com>
Date: Fri, 6 Sep 1996 13:03:43 PDT
Message-Id: <2.2.32.19960906200343.0069be44@uffa.wrc.xerox.com>
To: hallam@ai.mit.edu
Cc: slein@wrc.xerox.com, w3c-dist-auth@w3.org, hallam@ai.mit.edu

At 09:02 AM 9/6/96 PDT, hallam@ai.mit.edu wrote:
>
>>One reason for having a separate MOVE operation is that if the document has
>>attributes, you want a COPY operation to result in new values for certain
>>attributes (like create date, creator) whereas a MOVE operation should leave
>>the values alone.
>
>I disagree. Such attributes make little sense in the context of the
>Web, indeed the Web currently has no knowledge whatsoever of such
>things.
>
>If I move a file from one area of URL space to another that does
>not imply a transfer on the backing store.
>
>	Phill
>

I don't mean just file attributes, but metadata in general -- author, title,
publisher, subject, etc.  Most metadata stays the same whether a document is
MOVEd or COPYd, but there are exceptions.  URN, if implemented, is another
attribute that should never change when a document is MOVEd, whereas a COPY
of a document should get its own URN.  Although work on metadata on the Web
is very much "in progress" (URC, Z39.50, STARTS, etc.), I think it is an
important part of document management that should be encompassed by the Web.
It should be possible to set metadata using HTTP, however it turns out to be
expressed.  And the metadata should get updated properly when a document
gets COPYd or MOVEd.

--Judy 
Name:		Judith A. Slein
E-Mail:		slein@wrc.xerox.com
Phone:  	8*222-5169
Fax:		(716) 265-7133
MailStop:	128-29E
Received on Friday, 6 September 1996 16:04:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:41 GMT