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:09:25 +0100
Message-ID: <41BA0275.2090302@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.
> 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.
> 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.
> Lisa

Forgot to mention...: what you describe here (to me) clearly is a case 
of where the information you want to expose is part of the state of the 
slide show, not of an individual picture. So it seems to be quite 
obvious to model the slide show as WebDAV collection, and to maintain 
ordering and other defaults (display time, effects, whatever) as state 
of that collection.


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

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:31 UTC