why did you develop kolab xml format?

Ingo Klöcker kloecker at kde.org
Sat Feb 9 12:33:39 CET 2008


[Please note, that I'm not subscribed to this mailing list.]

On Wednesday 06 February 2008, you wrote:
> Am Dienstag, 5. Februar 2008 schrieb Gunnar Wrobel:
>
> Hi,
>
> > > I'm interested in groupware developing and just subscribed to ask
> > > you a question. I couldn't find an explanation about your
> > > motivation not to use vCard and vCal anymore, but to develop an
> > > XML format.
> >
> > I think the original reasons were that vCal did not provide all the
> > functionaltiy to match the requirements to cope for the different
> > clients.
>
> No, it was not about lack of functionality but for other reasons
> including but not limited to:
>
> iCal and vCard standards are very complex, featureful, and offer a
> superset of overlapping functionality. (A typical multi-vendor
> standard).
>
> They are difficult to parse and hard to extend. The later is
> especially importand if you intend to match the OL/Ex functionality
> 1:1.

FWIW: The IETF is forming a new working group to look at updates to the 
vCard format (RFC2426). (See attached message.)

I think you should join the working group for making sure that at least 
some of the short-comings of the vCard format you've observed are 
fixed.


Regards,
Ingo
-------------- next part --------------
An embedded message was scrubbed...
From: Brad Hards <bradh at frogmouth.net>
Subject: [Kde-pim] new IETF activity on vCard
Date: Sat, 09 Feb 2008 13:49:00 +1100
Size: 9953
URL: <http://lists.kolab.org/pipermail/format/attachments/20080209/0ea6bba8/attachment.mht>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/format/attachments/20080209/0ea6bba8/attachment.sig>


More information about the format mailing list