- From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
- Date: Fri, 26 Mar 2004 06:56:50 -0500
- To: Webdav WG <w3c-dist-auth@w3c.org>
I agree with Julian's response. Systems that only allow one parent for a resource are free to define/implement properties that only make sense if there is exactly one parent. If they decide to support multiple parents, then they will have to redefine that property. One trivial way to do so is to just say that this property describes one of the paths to the resource, e.g. in the case of "parentname", you would say "this property describes the binding name of this resource in one of its parents". Cheers, Geoff Julian Reschke <julian.reschke@gmx.de> wrote on 03/25/2004 06:04:36 PM: > Lisa Dusseault wrote: > > > I found a reference to the "parentname" property, defined for Exchange > > 2000 and Exchange 2003 in the "DAV:" namespace (no big surprise there > > though it's unfortunate): > > > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/ > > wss/_cdo_schema_dav.asp > > I fail to see the issue. It only means that when Microsoft decides to > support the BIND draft, they'll have to re-think that design decision. > Just because somebody in the past did a poor system design that is > inherently incompatible with having multiple URIs for the same resource > shouldn't prevent *us* from doing things right.
Received on Friday, 26 March 2004 06:57:49 UTC