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

Re: [caldav] [VCARDDAV] new webdav sync draft

From: Andrew McMillan <andrew@morphoss.com>
Date: Sat, 21 Nov 2009 20:47:12 +1300
To: w3c-dist-auth@w3.org
Message-ID: <1258789632.32680.382.camel@happy.home.mcmillan.net.nz>
On Sat, 2009-11-21 at 07:56 +0100, Julian Reschke wrote:
> Andrew McMillan wrote:
> > On Fri, 2009-11-20 at 17:13 +0100, Arnaud Quillaud wrote:
> >> On 11/19/09 11:01 PM, Andrew McMillan wrote: 
> >>> In particular when synchronising a calendar collection it would be
> >>> desirable for the report to be able to return 'caldav:calendar-data',
> >>> which in many cases would then save the further round-trip of a
> >>> calendar-multiget report following this report.  I assume there would be
> >>> similar advantages in retrieving the actual changed data in other extensions.
> > 
> >   
> >> A client may ask for any property... as long as it is defined as
> >> such... calendar-data is not one of them. See
> >> http://tools.ietf.org/html/rfc4791#section-9.6 :
> >> << 
> >> However, the CALDAV:calendar-data XML element is
> >>       not a WebDAV property and, as such, is not returned in PROPFIND
> >>       responses
> > 
> > Ah, what a shame.  Can I take it from this that CardDAV will also suffer
> > from this limitation?
> > ...
> Can't resist: "I told you so". Pseudo-properties are bad; they require 
> more special cases, create ambiguities and confusion.

Conceptually, the idea of the actual data just being one element of the
meta-data doesn't seem unreasonable.

I have to confess that in my implementations to date I had just assumed
that the data is only one property within the schema, and it's certainly
much simpler for me to code it that way in my own application.

For webdav sync I would suggest that the caldav:calendar-data and
carddav:address-data (and perhaps other pseudo-properties I don't know
about) should be available to the sync report in the same way as they
are for the caldav:calendar-multiget and carddav:addressbook-multiget

It would also be nice to see a generic DAV:multiget report replacing the
*-multiget reports, since they don't seem to do anything particularly
special within their respective namespaces.

					Andrew McMillan.

http://andrew.mcmillan.net.nz/                     Porirua, New Zealand
Twitter: _karora                                  Phone: +64(272)DEBIAN
       The truth is rarely pure, and never simple. -- Oscar Wilde

Received on Saturday, 21 November 2009 07:48:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:44 UTC