Re: AtomPubIssuesList for 2005/02/22

[Robert Sayre <mint@xxxxxxxxxxxxxxx>]

Sam Ruby wrote:
> Robert Sayre wrote:
>
> > > To include MOVE, a la carte, within Atom, seems like feature creep to 
> > > me.
> >
> >
> > Atom, the protocol that can't rename a jpg ;)
>
>
> ... atomically.  ;-)
>
> It is not difficult to craft a series (of two!) operations that combined 
> have the effect of renaming a jpg.

It's very difficult if any URI can be member of any collection.

"COPY and MOVE semantics are not really operations on the target of the 
COPY and MOVE -- in fact, they are operations on the parent collections 
that "own" the origin and destination namespaces."[0]

"To achieve desirable outcomes for multiple containment cases, clients
must have a way of clearly indicating that they want move semantics"[1]

The proposal at hand seems to allow multiple containment, prevent 
operations on the parent collection, and prevent clients from indicating 
they want move semantics.

Robert Sayre

[0] http://www.xent.com/pipermail/fork/2001-August/003191.html
[1] http://www.xent.com/pipermail/fork/2001-August/003197.html