Re: Comment on UNBIND language in BIND specification

Julian Reschke wrote:
> 
> Jim Whitehead wrote:
> 
>> I'm reading through the BIND specification, and the description of the
>> REBIND method's operands is a bit unclear to me. I'm assuming the 
>> intent is
>> similar to BIND and UNBIND, each of which clearly state in the first
>> sentence what role the Request-URI, segment, and href fields play. In my
>> reading I just jumped right into the spec. at this method (typical 
>> reference
>> reading pattern), and hence I didn't initially see the similarity with 
>> the
>> BIND and UNBIND method operands.
> 
> 
> Agreed.
> 
> Would replacing
> 
> "The REBIND method removes a binding to a resource from one collection, 
> and adds a binding to that resource into another collection. It is 
> effectively an atomic form of a MOVE request."
> 
> by
> 
> "The REBIND method removes a binding to a resource from the collection 
> identified by the Request-URI, and adds a binding to that resource into 
> another collection. It is effectively an atomic form of a MOVE request."
> 
> be sufficient?
> 
> Best regards, Julian

I expanded the replacement further to:

    The REBIND method removes a binding to a resource from the collection
    identified by the Request-URI, and adds a binding to that resource
    into another collection.  The request body specifies the segment to
    be removed and the new binding to be created (href element).  It is
    effectively an atomic form of a MOVE request.

(Issue tracked as 
<http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-issues.html#6_rebind_intro> 
and currently marked as "closed").

Best regards, Julian



-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

Received on Friday, 12 November 2004 16:22:13 UTC