Members of the kdepim and OpenGroupware.org teams met at Magdeburg on the last
weekend of October to implement OpenGroupware.org support in Kontact. The effort
turned out to be a full success. After two days of ferocious hacking the team
consisting of Till Adam and Cornelius Schumacher from KDE and Helge Heß andMarcus Müller from OpenGroupware.org had completed a first
working implementation for accessing the OpenGroupware.org server through Kontact.
This adds another Free Software system to the growing list of groupware servers
supported by KDE. A special aspect of this implementation is that it is
completely based on existing open standards like HTTP, WebDAV, iCalendar and
vCard and could serve as a model for a standard access to groupware servers. The
used protocol is documented as a draft RFC.

Vital makes sense, but can be interpreted in two wildly different ways, both of which could make sense. Vital could mean the community is active or it could mean that the community is essential, either of which could make sense in one way or another. By contrast, lively only means the first, making it a more pointed and reliable term (assuming that the second meaning was not what was meant).

You can read/write with the WebDAV KIO to the OGo document store. Versioning needs to be controlled in the web interface though. I'm not sure whether versioning can be properly done at such a low level - AFAIK in SharePoint the versioning is also done at application plugin level (using Office plugins) and is not supported in WebFolders.

Something which would be cool (and probably not very difficult) for the WebDAV slave is the ability to maintain a local cache of the server documents similiar to Apple iDisk - using the same (standard!) mechanism described in the RFC and implemented by the Kontact resource.

I think it would be quite possible to integrate locking, setting attributes and versioning into Konqueror and the standard file dialig without having to use a special application plugin.

This could be done for WebDAV in general as well as for Subversion. And Cervisia is a good example how one could even integrate diffing and more advanced versioning commands directly into the file management view.

Sounds cool! If someone wants to work on such a file management extension for OpenGroupware.org, let me know :-) I would be pleased to discuss that.

BTW: while WebDAV as a V in its name, it does not support versioning itself. There is an extension for WebDAV which does that, but I don't think it is widely implemented by servers (even if the provide a versioned document store).

Besides a simplistic filesystem storage OGo currently provides a RDBMS based one which has fast meta data, ACLs and a simple versioning system.
As mentioned OGo currently does not support the WebDAV version extension mostly due to the lack of clients - if KDE would support that, it might be worth consideration.

Maybe this is really getting off-topic, but does Svn really use a strict subset of RFC 3253? I had the impression that some concepts are shared but that Svn has its own extensions to WebDAV making it useless as a basis to start a standards implementation.

"So how 'compatible' is Subversion with other DeltaV software? In two words: not very."

But there is some common ground. Basically you can use Subversion via pure WebDAV if you can live with automatically generated checkin messages. If one only uses WebDAV clients (which is an option for a repository that is only used for shared document storage) even locking can be made to work.

I wouldn't say that Subversion can be a reference server for a fully DeltaV-compliant versioned document backend, but I think that it would be quite possible to write a configurable KDE extension as the basis for both a Subversion-aware and a fully DeltaV-compliant frontend.

I know that I'm getting more and more off topic, but an interesting question would be how well the different backend approaches (Subversion with its two backend implementations, OpenGroupware's two implementations, etc.) perform. If used as a document storage for a department or SOHO network such a backend should have throughputs that come close to NFS or SMB, at least for retrieving the most current version of the stored documents ...

While the name suggest that, WebDAV (RFC 2518) does *not* implement any operation related to versioning (point to the section inside the spec ;-).
It does support locking, both optimistic (etags as used in the Kontact resource) as well as pessimistic (LOCK HTTP method).

I think I saw on a mailing list that somebody had started implementing RFC 3253 for the KDE webdav KIO but I don't know if it is finished.

Adding integrated versioning capacity to KDE file operation be it for a local Reiser4 filesystem (maybe RFC 3253 could be implemented as a Reiser4 plugin) or a Webdav server like OGo would be a "killing" feature alonside with a better support for metadata.

Ah, it is sad but, in a way, quite normal. If most WebDaV servers don't support the versioning addition,it is hard to create a community to develop a client and vice-versa. The classical chicken and egg problem.

What are your plan Christian for Cervisia ? Could it be possible to extract from it a light universal versioning client targeted to regular office workers ?

BTW, Looking at the RFC, is there any intention to handle localization issues? AFAIK OGo's libFoundation is 8 bit (problem with Hebrew/Arabic etc.) Does it mean that with the new protocol there's no need to use libFoundation?

The protocol has nothing to do with the Foundation library being used, actually its even independend of the groupware server being used and only relies on HTTP, some WebDAV, iCalendar and vCard.
Maybe it should be made explicit in the RFC, the client and server are supposed to support UTF-8 as the encoding for the iCalendar and vCard entities (text/calendar;charset=utf-8 MIME type).

PS: OGo already works fine with Cocoa Foundation and probably does with the GNUstep one. Also, libFoundation does support UTF-8 and the OGo API was always based on Unicode. The pending localization issues are mostly in code which connects to plain-C libraries. There are detailed reports on them in the OGo developer list, feel free to join! ;-)

I know it's a bit of a long shot, but I'd like to know whether anyone is offering sample demo accounts for opengroupware. I'd rather do a quick test over the net than install the software on my computer or download a full ISO to test it!