depth in draft-daboo-webdav-sync-01

Hello,

In Section 4.2 
(http://tools.ietf.org/html/draft-daboo-webdav-sync-01#section-4.2), the 
response is defined as:

<<

The response body for a successful DAV:sync-collection REPORT
      request MUST contain a DAV:sync-response element for each resource
      that was created, has changed or been deleted since the last
      synchronization operation as specified by the DAV:sync-token
      provided in the request.

 >>

Given that the depth header should be ignored, and given the ambiguity 
of the term "resource", it would be worth mentioning that this applies 
only to non-collection resources directly contained in the target 
collection.
In other words, creation/modification/deletion of subcollections and 
their children should not be included.

Arnaud