- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 7 Mar 2003 10:06:36 +0100
- To: "Stefan Eissing" <stefan.eissing@greenbytes.de>, "Clemm, Geoff" <gclemm@rational.com>
- Cc: "WebDAV" <w3c-dist-auth@w3.org>
- Message-ID: <JIEGINCHMLABHJBIGKBCEEPOGKAA.julian.reschke@gmx.de>
> From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Stefan Eissing > Sent: Friday, March 07, 2003 9:53 AM > To: Clemm, Geoff > Cc: WebDAV > Subject: Re: bind draft issues > > > > > Am Freitag, 07.03.03, um 00:50 Uhr (Europe/Berlin) schrieb Clemm, Geoff: > > How about the following statement about PROPFIND: > > > > "If two URLs are mapped to the same resource, the property > > values returned by PROPFIND on those two URLs MUST be > > identical." > > Hmm, I think I know what you mean, however there are cases > where you might want this to break: > > 1) variants. /news/english/ and /news/german/ might be the same > resource with different content based on the "access" URL. All > get* properties will probably vary. (They can already vary on > a resource with a single binding) That would mean that entities may vary based on the request URI. Is this the case? > 2) live props with URI References can report different relative uri > references. They are semantically equivalent, but the string value > of such a property will differ. For instance? > What exactly is it, you want to prevent to happen? People falling into the trap of believing in "URL properties", I guess. -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Friday, 7 March 2003 04:06:53 UTC