RE: Namespace consistency

My reading of the DAV spec is that both Jim's statement (the parents of a
DAV resource do not have to be a DAV resource) and Larry's language (the
child of a DAV resource doesn't have to be a DAV resource) are BOTH correct
and BOTH supported by the spec. The language in the spec is phrased as "If a
resource is DAV compliant THEN ....."

In the particular case Larry lists my understanding of the spec is that if
http://a/b/c IS DAV compliant then http://a/b/c/d.cgi WOULD be listed as a
member of http://a/b/c EVEN THOUGH it isn't itself DAV compliant. The
requirement for listing is only on http://a/b/c because it is DAV compliant
but this puts no onus on http://a/b/c/d.cgi to be DAV compliant.

				Yaron

> -----Original Message-----
> From: Larry Masinter [mailto:masinter@parc.xerox.com]
> Sent: Monday, September 14, 1998 8:44 PM
> To: Jim Davis; WebDAV WG
> Subject: 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
>  
> > 
> > 
>