Re: rfc2518bis-14: locking terminology

Hi,

this thread contains lots of thoughtful comments, in particular:

- make sure that we properly use the terminology we have introduced

- make sure that if we need other terminology, we properly define it upfront

- define *once* what the lockable state of a resource/collections is, 
and simplify the remainder of section 6/7 based on that

- clearly say once what a lock is (it is a resource, identified by a 
URI) and give those aspects of a lock proper names, such as in 
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-locking-latest.html#rfc.section.2.5>:

-- lock access type (currently only write)

-- lock scope (exclusive/shared)

-- lock root (URL)

-- lock depth

-- client supplied owner information

-- lock creator

-- timeout

...these aspects fully describe a lock. As Manfred correctly stated, 
there's no such thing as moving a lock, as in general, a lock doesn't 
have a location.


Best regards,

Julian