W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 1998

RE: Hierarchical URLs and Collections

From: Larry Masinter <masinter@parc.xerox.com>
Date: Tue, 18 Aug 1998 13:01:14 PDT
To: "Yaron Goland" <yarong@microsoft.com>, "'Slein, Judith A'" <JSlein@crt.xerox.com>, "'WebDAV'" <w3c-dist-auth@w3.org>
Cc: "Falkenhainer, Brian" <Brian_Falkenhainer@mc.xerox.com>, "Garnaat, Mitchell" <MGarnaat@crt.xerox.com>, "'Jim Davis'" <jdavis@parc.xerox.com>, "Jim Whitehead (E-mail)" <ejw@ics.uci.edu>
Message-ID: <001301bdcae2$f44abbc0$aa66010d@copper.parc.xerox.com>

I don't understand what's 'quite complex' about suggesting that there
be a DAV:parents property and that interoperable clients that want to
work with the typical document management based systems as well as
file-server based systems should use PROPFIND of DAV:parents in order
to walk up the hierarchy, rather than just trying to parse the URL
tree. It's simple, backward compatible, doesn't cost much in terms of
server implementation, and much more resiliant.

Yes, there's a hierarchy, and yes, if you use it, there's a clear
way to use it, but that's very different from _requiring_ that the
hierarchy be used.

Put the burden of understanding the hierarchical forms on the servers,
not on the clients.

Received on Tuesday, 18 August 1998 16:01:40 UTC

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