RE: Status code for creating lock-null resource

"Jim Whitehead" <ejw@cse.ucsc.edu> wrote:
> One of the features you need for document management is
> the ability to set a large number of properties when the
> body of a resource is first created.

The implication is that a lock-null resource has properties but does not
have a body!

> If the 201 doesn't come back, then a client wouldn't know
> that this is the first time the resource body state is being
> set.
>
> Of course, this isn't the only way to address the issue --
> a client could allow properties to be set internal to the
> document format (like .doc and .pdf files), and then the
> server could extract the metadata from the document. But,
> this requires document-specific knowledge, and that implies
> brittleness over time.

Not good I agree.

Tim