Re: WebDAV sync informal last call

Hi Cyrus,

Here are my comments:

Section 3.2

A resource must appear only once. What happens when there is more than one binding for a resource? Should
only one of those bindings be reported? If so, should always the same binding be reported (perhaps the
client knows he resource under a specific name)? The latter would have a significant impact on a server implemenation.

Section 3.3 (last paragraph)

When some collection can't be synchronized the status code 405 is put in its DAV:response. However, this
would imply the REPORT method is not allowed for the resource, while it is only this report type that isn't.
Wouldn't the status code 403 be more appropriate in this case?

The paragraph ends by saying that such a fact should be reported only once. What is to be reported then for
this resource when the same report is requested a second time?

Section 3.5.1

second paragraph:

This paragraph states that when a resource is deleted and a new one is created using the same URI only a
changed resource should be reported. However, this would imply a relationship between the deleted and
the newly created resource. This is in contradiction with the BIND-spec, because the resource-id
property would be different. In other words, no such relationship exists. I think a deletion and a
creation should be reported in this case. If the same resource is rebound to the same URI nothing should be reported.

Remark: