W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 1997

RE: INDEX vs. PROPFIND

From: Yaron Goland <yarong@microsoft.com>
Date: Wed, 3 Dec 1997 10:52:50 -0800
Message-ID: <11352BDEEB92CF119F3F00805F14F485043F8B2B@red-44-msg.dns.microsoft.com>
To: "'Judith Slein'" <slein@wrc.xerox.com>, w3c-dist-auth@w3.org
1. There is currently no way to get just a list of URLs without any
properties. As this information wouldn't even contain an indication if a
resource was an empty collection or a normal resource this wasn't considered
a compelling requirement.

2. You WILL get the href for every member, even if it doesn't have the
property you are looking for. This is a limited search so knowing that a
resource doesn't have a particular property is just as important as knowing
its value for resources that do. I will put in language to make this
clearer.

		Yaron

> -----Original Message-----
> From:	Judith Slein [SMTP:slein@wrc.xerox.com]
> Sent:	Wednesday, December 03, 1997 7:38 AM
> To:	w3c-dist-auth@w3.org
> Subject:	INDEX vs. PROPFIND
> 
> I have a couple of questions about what it will mean to get rid of INDEX
> and use PROPFIND instead.
> 
> 1.  What if all I want is the list of URLs of the members of the
> collection, and I don't want to see any properties?  The Propfind request
> header currently requires at least one property to be requested.
> 
> 2.  What will PROPFIND behavior be if I ask for, say, the author property
> and the title property, and some of the members of the collection have
> those properties while others do not?  What I want to happen if I'm using
> PROPFIND as a substitute for INDEX is that I get at least the href for
> every member of the collection, whether or not it has the properties I
> requested.
> 
> --Judy
> 
> 
> Name:		Judith A. Slein
> E-Mail:		slein@wrc.xerox.com
> Phone:  	(716) 422-5169
> Fax:		(716) 422-2938
> 
> Xerox Corporation
> Mail Stop 105-50C
> 800 Phillips Road
> Webster, NY 14580
Received on Wednesday, 3 December 1997 13:53:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:44 GMT