W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2004

Re: [Bug 3] Bindings draft should specify if all properties MUST have same value on all bindings

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 10 Dec 2004 21:05:50 +0100
Message-ID: <41BA019E.5080209@gmx.de>
To: Lisa Dusseault <lisa@osafoundation.org>
CC: ejw@cs.ucsc.edu, 'webdav' <w3c-dist-auth@w3.org>

Lisa Dusseault wrote:
> What about a live property called "nextPhoto" on a WebDAV collection of 
> photos?  Then it's trivial to do a "slideshow" for that collection, 
> going from one photo to the next.  You can support one photo that 
> appears in multiple slideshows through bindings, and the value for 
> "nextPhoto" depends on which slide show the client is looking at, which 
> is clearly detectable from the URL.

Either use Ordered Collections (RFC3648), add a multi-valued property on 
the collection container, or expose the information as pair 
(parent-collection, next-binding) on the resource.

> This kind of thing could be useful for other applications as well.  It 
> could even work with PROPPATCH, because the server knows to treat this 
> as a "per-binding" property and change only the value that applies for 
> this binding.

So where do you store it? Either on the resource itself (in which case 
you need to maintain that property for each parent collection, so you 
could simply expose that information as well), or on the collection.

> I can even imagine a generic way of the client telling the server to 
> "create me this new dead property as a per-binding property" so that the 
> client can provide a new value per binding.

I can imagine a lot of things as well. The question is: do we really 
need that and how does fit into the model that we're using for WebDAV?

BTW: you seem to be changing positions frequently :-) May I remind you 
that you asked that the BIND spec mandates that properties MUST NOT vary 
across bindings?

Best regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Friday, 10 December 2004 20:06:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:17:51 UTC