1. Multiple URI/URL per resource (1)
Long discussion on list, key issues were:
Can a WebDAV resource have more than one URI?
Can a WebDAV collection resource have more than one URI?
Resolution: yes, any WebDAV resource can have more than one URI.
Are terms URI/URL used consistently?
Resolution: some inconsistent use was fixed in -10, some may linger. Needs review.

2. Multiple URI/URL per resource (2)
Does the draft distinguish between URI/URL and resource correctly?
Resolution: The draft was changed so that URI/URL and resource are properly distinguished so its clear when requirements affect URI/URL, and when they affect resources.
Open issues:
Discussion of collections can use some work to make intent more clear.
Others?

3. Namespace Consistency (1)
There was significant discussion/confusion on the list about WebDAV requirements for namespace consistency.
“An HTTP URL namespace is said to be consistent if it meets the following conditions: for every URL in the HTTP hierarchy there exists a collection that contains that URL as an internal member. The root, or top-level collection of the namespace under consideration is exempt from the previous rule.”

4. Namespace Consistency (2)
“Neither HTTP/1.1 nor WebDAV require that the entire HTTP URL namespace be consistent. However, certain WebDAV methods are prohibited from producing results that cause namespace inconsistencies.”
For example, COPY and MOVE have require the destination namespace to be consistent.

5. Namespace Consistency (3)
“For all WebDAV compliant resources A and B, identified by URIs U and V, for which U is immediately relative to V, B MUST be a collection that has U as an internal member URI.”
So, if the resource with URL is WebDAV compliant
and if the resource with URL is WebDAV compliant
then the resource with URL must be a collection and must contain URL as an internal member.

6. Namespace Consistency (4)
“Collection resources MAY list the URLs of non-WebDAV compliant children in the HTTP URL namespace hierarchy as internal members but are not required to do so.”
For example, if the resource with URL is not WebDAV compliant
and the URL identifies a collection
then URL may or may not be an internal member of the collection with URL

7. Namespace Consistency (5)
“If a WebDAV compliant resource has no WebDAV compliant children in the HTTP URL namespace hierarchy then the WebDAV compliant resource is not required to be a collection.”

8. XML attributes in property values
If a property value contained in a PROPPATCH “set” instruction contains XML attributes associated with the XML elements of the property, what should the server do with them?
1. Store them, and return them on later retrievals
2. Throw them away
Spec. is currently silent on this issue.