- From: Lisa Dusseault <lisa@xythos.com>
- Date: Wed, 12 Nov 2003 09:07:16 -0800
- To: "'Stefan Eissing'" <stefan.eissing@greenbytes.de>
- Cc: <www-webdav-dasl@w3.org>, "'Julian Reschke'" <julian.reschke@gmx.de>, "'Wallmer, Martin'" <Martin.Wallmer@softwareag.com>
> > > 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. > It's not a defined term, I wasn't trying to be rigorous. If you have a system in which a resource has one URL which provides normal access, and other URLs which provide "redirect" or pseudo-bind access, you could consider that normal URL to be the primary mapping. > 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 10:07:41 UTC