W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2006

Possible problem in collection definition

From: Lisa Dusseault <lisa@osafoundation.org>
Date: Thu, 16 Feb 2006 18:46:20 -0800
Message-Id: <5C8E554A-AB8C-4340-9320-6F3EF7DF72D1@osafoundation.org>
To: webdav WG <w3c-dist-auth@w3.org>

 From bug 227 <http://ietf.webdav.org:8080/bugzilla/show_bug.cgi? 

     For all WebDAV compliant resources A and B, identified by URLs "U"
     and "V" respectively, such that "V" is equal to "U/SEGMENT", A MUST
     be a collection that contains a mapping from "SEGMENT" to B. So, if
     resource B with URL "http://example.com/bar/blah" is WebDAV  
     and if resource A with URL "http://example.com/bar/" is WebDAV
     compliant, then resource A must be a collection and must contain a
     mapping from "blah" to B.

and an example from just after:

     An example for this case are servers that support multiple alias  
     for each WebDAV compliant resource.  For instance, a server may
     implement case-insensitive URLs, thus "/col/a" and "/col/A"  
     the same resource, yet only either "a" or "A" are reported upon
     listing the members of "/col".

This example may be inconsistent with the requirement just stated.   
We can argue that '/col/a' maps to a WebDAV compliant resource and "/ 
col" maps to a WebDAV collection, thus "/col" MUST have a mapping  
from "a" to the child resource.  We can argue the same for "/col/ 
A".   Following that logic could make URL-case-insensitive servers  
rather difficult ...

It may *not* be inconsistent if we claim that "/col/a" and "/col/A"  
are the same URL. It also may not be inconsistent if we say that  
resource B is identified by one of "/col/a" or "/col/A" but not the  
other, but that wouldn't be the meaning of "identified by" that I'd  
Not proposing what to do about this just yet.

Received on Friday, 17 February 2006 02:46:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:35 UTC