W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2004

Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Wed, 23 Jun 2004 18:13:13 -0400
To: w3c-dist-auth@w3.org
Message-ID: <OF73FA765A.B0A2F47D-ON85256EBC.00666007-85256EBC.007A1C4A@us.ibm.com>
I noticed that you moved the sentence to the end of the third
paragraph instead of to the end of the second paragraph.
I'd prefer it to be at the end of the second paragraph, but
either way is OK.

Cheers,
Geoff

Julian Reschke <julian.reschke@gmx.de> wrote on 06/23/2004 02:27:36 PM:

> Geoffrey M Clemm wrote:
> 
> > 
> > Yes, we can simplify that.  In particular, I would just move
> > the second sentence of the last paragraph to the end of the second 
> > paragraph,
> > and then delete the rest of the last paragraph. 
> 
> OK, here's the section after the simplification:
> 
> 
> 2.5  MOVE and Bindings
> 
>     When MOVE is applied to a resource, the other bindings to that
>     resource MUST be unaffected, and if the resource being moved is a
>     collection, the bindings to any members of that collection MUST be
>     unaffected.  Also, if MOVE is used with Overwrite:T to delete an
>     existing resource, the constraints specified for DELETE apply.
> 
>     If the destination collection of a MOVE request supports the REBIND
>     method (see Section 6), a MOVE of a resource into that collection 
MAY
>     be implemented as a REBIND request.  Although [RFC2518] allows a 
MOVE
>     to be a non-atomic operation, when the MOVE operation is implemented
>     as a REBIND, the operation is atomic.  In particular, applying a 
MOVE
>     to a Request-URI and a Destination URI has the effect of removing a
>     binding to a resource (at the Request-URI), and creating a new
>     binding to that resource (at the Destination URI).
> 
>     As an example, suppose that a MOVE is issued to URI-3 for resource R
>     below (which is also mapped to URI-1 and URI-2), with the 
Destination
>     header set to URI-X.  After successful completion of the MOVE
>     operation, a new binding has been created which creates the URI
>     mapping between URI-X and resource R.  The binding corresponding to
>     the final segment of URI-3 has been removed, which also causes the
>     URI mapping between URI-3 and R to be removed.  If resource R were a
>     collection, old URI-3 based mappings to members of R would have been
>     removed, and new URI-X based mappings to members of R would have 
been
>     created.  Even when the Request-URI identifies a collection, the 
MOVE
>     operation involves only removing one binding to that collection and
>     adding another.
> 
>     >> Before Request:
> 
>      URI-1   URI-2    URI-3
>        |       |        |
>        |       |        |      <---- URI Mappings
>        |       |        |
>     +---------------------+
>     |     Resource R      |
>     +---------------------+
> 
>     >> After Request:
> 
>      URI-1   URI-2    URI-X
>        |       |        |
>        |       |        |      <---- URI Mappings
>        |       |        |
>     +---------------------+
>     |     Resource R      |
>     +---------------------+
> 
> 
> 
> 
> Best regards, Julian
> 
> -- 
> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Wednesday, 23 June 2004 18:14:19 GMT

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