GroupDAV

GroupDAV is a computer protocol used to connect Open Source groupware clients with Open Source groupware servers. It is a lightweight protocol whose primary design goal is to be as simple as possible to implement, focusing more on real world issues with open source applications than on an extremely extensive command set. It is based on a subset of WebDAV.

Client side GroupDAV implementations exist for KDE Kontact, Novell Evolution, Thunderbird and Outlook, work on the Mozilla Calendar Project is in progress. Servers includeOpenGroupware.org, SOGo, the Citadel system and eGroupWare. In addition every WebDAV (and therefore CalDAV/CardDAV) server is implicitly a GroupDAV v2 server^{[citation needed]}.

GroupDAV's relationship to CalDAV varies from developer to developer. Some of the earliest implementors intended it as a protocol complementary to the CalDAV effort, because CalDAV provides more extensive operations on calendar folders. Others have positioned GroupDAV as the leading protocol, citing CalDAV's excessive complexity as a source of interoperability bugs. This dichotomy is likely to become irrelevant in the future, however, as it is straightforward for a server to simultaneously support all variants.

GroupDAV is now considered by some to be a subset of CalDAV (RFC 4791) and CardDAV (RFC 6352) intended for less complex applications.

[edit]See also

• WebDAV
• CalDAV
• CardDAV

[edit]External links

• http://www.groupdav.org/

출처 - http://en.wikipedia.org/wiki/GroupDAV

---

GroupDAV was an effort to create a "down-to-the-earth" protocol to connect OpenSource groupware clients with OpenSource groupware servers. By the means of reusing the iCalendar (RFC5545) and vCard (RFC 2425) formats to represent data, and the WebDAV (RFC 4918) protocol to retrieve records and apply changes. 
A major goal of GroupDAV was to keep the protocol as simple as possible and to stay focused on real world issues with OpenSource and free software applications. 
Unfortunately, though, this didn't completely fly ;-)

More precisely, GroupDAV got superseded by CalDAV (RFC 4791) and CardDAV (soon to be an RFC). In fact the basic idea of using iCalendar and vCard on top of WebDAV turned out to be a great success with a lot of support from even the largest companies, Apple, Google, Oracle, Sun, Yahoo, Zimbra but also from a lot of small companies, say Kerio, Zarafa, or OpenSource projects like ScalableOGo, DAViCal, Bedework or Mozilla Lightning. 
CalDAV and CardDAV are more complex, but apparently people want that - just check the list of implementors :-)

The CalDAV/CardDAV development is driven by the CalConnect consortium. Everyone is welcome to join!

Status

GroupDAV isn't developed any further. Its superseded by CalDAV (RFC 4791) and CardDAV.

FOSDEM

Helge did a talk on CalDAV/GroupDAV at FOSDEM, you can grab the Video over here: CalDAV - the open groupware protocol

From the early stages of GroupDAV: Cornelius Schumacher interviewed

KDE Kontact guru Cornelius Schumacher got interviewed during the Dutch KDE-PIM meeting. The interview contains a nice introduction into the motivations of GroupDAV and why it doesn't conflict with CalDAV [read it!]. Cornelius was part of the KDE team that joined with participants of OGo to create the first version of the draft.

The Draft (deprecated)

The draft-01 is the very first version of the draft. It has a set of issues which need to get resolved - we will need some iterations until this is a sound document. 
Be sure that you understand the limited scope of this effort prior drawing incorrect conclusions. You are invited to join our mailing list to ask any question you have.

So what is it about?

GroupDAV had a very specific focus which is connecting the three popular OpenSource clients - Kontact, Evolution and Sunbird - with the broad range of OpenSource "groupware" servers. Whatever "groupware" means to the ~200 projects listed on Freshmeat. 
This is a very specific focus because all the three clients have no legacy issues and are 100% iCalendar based while the far majority of the OpenSource servers started as RDBMS web applications which did not care about iCalendar at all. 
Our goal was to connect them to native clients in a useful way despite their legacy issues. As an example consider the Bugzilla bugtracking system to expose its bugs as iCalendar tasks. Bugzilla can't represent a recurring task in the iCalendar concept nor does it feature alarms. 
GroupDAV is supposed to deal with such setups in a graceful and pragmatic way. 

출처 - http://www.groupdav.org/