From groupdav@opengroupware.org  Fri Jul  3 01:05:06 2009
From: groupdav@opengroupware.org (Helge Hess)
Date: Fri, 3 Jul 2009 02:05:06 +0200
Subject: [GroupDAV] GroupDAVv2 PROPFIND request
In-Reply-To: <012FFAC4-1AB4-4A0F-B702-F864CF794741@opengroupware.org>
References: <012FFAC4-1AB4-4A0F-B702-F864CF794741@opengroupware.org>
Message-ID: <C739CD7C-7C02-41BC-9BD2-1B974BCCCAAE@opengroupware.org>

On 01.08.2008, at 17:02, Helge Hess wrote:
> - I added the GroupDAV:component-set property which
>  replaces the GroupDAV collection tags inside
>  DAV:resourcetype's.
>  (implementors always complained about non-flat props)
>  Sample:
>    <G:component-set>VEVENT,VTODO</G:component-set>


OK, so I'm not sure about this one. Apache mod_dav indeed allows XML  
property values, which would allow us to reuse the CalDAV 'supported- 
calendar-component-set' property. Hence, we could remove all GroupDAV  
namespaces. Which would be a good thing.

The property would look like:

          <C:supported-calendar-component-set
              xmlns:C="urn:ietf:params:xml:ns:caldav">
            <C:comp name="VEVENT"/>
          </C:supported-calendar-component-set>

          <C:supported-calendar-component-set
              xmlns:C="urn:ietf:params:xml:ns:caldav">
            <C:comp name="VCARD"/>
          </C:supported-calendar-component-set>
etc.

This would loose the advantage 'implementors always complained about  
non-flat props' but gains us easier/better CalDAV compat. Its  
certainly not more difficult than GroupDAVv1, which also required  
folder types in the structured resourcetype property.

Suggestions are welcome,
   Helge
-- 
Helge Hess
http://helgehess.eu/