RE: Namespace consistency

> > I think we should require all collections below a DAV-compliant
> >resource to also be DAV-compliant.  So, while it's OK to not be
> >DAV-compliant looking up a hierarchy tree, looking down the tree from a
> >DAV-compliant location should always be DAV-compliant. 
> 
> Strongly agree.

So a DAV-compliant resource can't be, say, a CGI script? Even in
'advanced DAV'?

If I have http://a/b/c/ and I want to add a CGI such that
 http://a/b/c/d is indirectly http://a/b/c/d.cgi, where
'd.cgi' computes a query, you might have http://a/b/c/d?e .
Now, is http://a/b/c/d.cgi a 'member' of http://a/b/c/ ?

Larry
--
http://www.parc.xerox.com/masinter
 
> 
>