W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > January to March 2002

RE: QSD

From: Lisa Dusseault <lisa@xythos.com>
Date: Mon, 28 Jan 2002 15:11:21 -0800
To: "Jim Davis" <jrd3@alum.mit.edu>, <www-webdav-dasl@w3.org>
Message-ID: <HPELJFCBPHIPBEJDHKGKIEPLDEAA.lisa@xythos.com>
I don't have time this week to read the draft.  It may well meet the need I
articulated.  However, is anybody besides me disturbed by the fact that this
property which refers to all properties is indistinguishable from a
property?  That seems error prone to me.

HTTP/DAV has other instances of needing to refer to "any" instead of a
specific thing, and * is more typically used for that.  For example, in
	OPTIONS * HTTP/1.1
the * refers to the server as a whole and not any resource in particular.
Should we use * instead of something which looks like a valid prop name?

Lisa

> -----Original Message-----
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Jim Davis
> Sent: Monday, January 28, 2002 10:14 AM
> To: www-webdav-dasl@w3.org
> Subject: RE: QSD
>
>
> At 10:04 AM 1/28/2002 +0100, Julian Reschke wrote:
> > > At 11:30 AM 1/27/02 +0100, Julian Reschke wrote:
> > > >> From: www-webdav-dasl-request@w3.org
> > > >> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Jim Davis
> >
> > >>That said, the use case you propose is, I think, the ability
> for a server
> > >>to disclose how it handles properties (you call them "custom
> properties",
> > >>but I am not sure if you mean live or dead, not that it
> matters much) *as a
> > >>whole*, as opposed to on an individual basis.
> >
> >That's what I added.
>
> Oh, okay.  Yes, I saw that.  It's cool.  Lisa, do you agree that it meets
> the need you articulated?
>
Received on Monday, 28 January 2002 18:13:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:08 GMT