Re: new proposed text for locking overview

> 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.