- From: Stefan Eissing <stefan.eissing@greenbytes.de>
- Date: Wed, 12 Nov 2003 09:56:28 +0100
- To: "Lisa Dusseault" <lisa@xythos.com>
- Cc: <www-webdav-dasl@w3.org>, "'Julian Reschke'" <julian.reschke@gmx.de>, "'Wallmer, Martin'" <Martin.Wallmer@softwareag.com>
Am 12.11.2003 um 08:26 schrieb Lisa Dusseault: > > Well, it's a little more complicated than that. I agree most existing > properties refer to the resource. Which ones do not? > However the spec actually says properties > describe "the state of" the resource. That state could include its URL > mappings or primary mapping or current mapping. What is the meaning of "primary mapping"? I have never seen that. Regards, Stefan > lisa > >> -----Original Message----- >> From: Julian Reschke [mailto:julian.reschke@gmx.de] >> Sent: Tuesday, November 11, 2003 4:57 PM >> To: Lisa Dusseault >> Cc: 'Wallmer, Martin'; www-webdav-dasl@w3.org >> Subject: Re: SEARCH for displayname >> >> >> Lisa Dusseault wrote: >>> Julian, you keep saying there are no URL properties. Where >> do you get >>> this dogma from? URL properties could be useful, are >> implemented, and >>> are not forbidden as far as I know. >>> >>> You may feel there *should* be no URL properties but it's >> misleading >>> to state that as fact. >> >> RFC2518 clearly states that it's the resource that has >> properties, not >> the URL (section 4). >> >> Regards, Julian >> >> -- >> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 >> >>
Received on Wednesday, 12 November 2003 03:59:29 UTC