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

Re: new proposed text for locking overview

From: Jason Crawford <ccjason@us.ibm.com>
Date: Thu, 8 Jul 2004 12:00:06 -0400
To: " webdav" <nnw3c-dist-auth___at___w3.org@smallcue.com>
Cc:
Message-ID: <OF335C7F92.D2E73FFE-ON85256ECB.004F8585-85256ECB.0057E684@us.ibm.com>
> But I'm not wedded to the idea of calling a lock a resource, so maybe 
> it would be simplest to just say: 
> 
> ---------------------------------------- 
> 
> 2.5 Status of a lock 
>     A lock is identified by a URI (the lock token URI) but in general, 
it
>    not have a HTTP URL, and thus can not be directly manipulated using
>    HTTP methods.  Instead, this specification defines the new methods
>    LOCK (creating and refreshing locks, see Section 4) and UNLOCK
>    (removing locks, see Section 5) that act indirectly on locks. 
> 
> ----------------------------------------- 
> 
> Since I believe this is the only section that refers to the 
"resourceness" 
> of a lock, we can avoid the contention while keeping all the good stuff 
in 
> the later paragraphs. 

I guess we'd have to see it in context, but if that's the only mention of
resourceness, that should be a significant improvement.  (Don't forget
to include the word "is" between lines 0 and 1.  :-))

J.
Received on Thursday, 8 July 2004 12:01:02 GMT

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