From wrobel at pardus.de Tue Feb 5 11:24:57 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 05 Feb 2008 11:24:57 +0100 Subject: why did you develop kolab xml format? In-Reply-To: <200801232248.13511.thomas@koch.ro> (Thomas Koch's message of "Wed, 23 Jan 2008 22:48:13 +0100") References: <200801232248.13511.thomas@koch.ro> Message-ID: <873as7wvie.fsf@home.pardus.de> Hi, Thomas Koch writes: > 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. > > Maybe you'd like to add this information to your wiki? Yes, will add a reminder to do that once I did digg up the original discussions. Cheers, Gunnar > > Thanks a lot, > > Thomas Koch > http://www.koch.ro > > _______________________________________________ > Kolab-format mailing list > Kolab-format at kolab.org > https://kolab.org/mailman/listinfo/kolab-format -- ______ http://kdab.com _______________ http://kolab-konsortium.com _ p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium ____ http://www.pardus.de _________________ http://gunnarwrobel.de _ E-mail : p at rdus.de Dr. Gunnar Wrobel Tel. : +49 700 6245 0000 Bundesstrasse 29 Fax : +49 721 1513 52322 D-20146 Hamburg ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Mail at ease - Rent a kolab groupware server at p at rdus << ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From martin.konold at erfrakon.de Wed Feb 6 02:20:43 2008 From: martin.konold at erfrakon.de (Martin Konold) Date: Wed, 6 Feb 2008 02:20:43 +0100 Subject: why did you develop kolab xml format? In-Reply-To: <873as7wvie.fsf@home.pardus.de> References: <200801232248.13511.thomas@koch.ro> <873as7wvie.fsf@home.pardus.de> Message-ID: <200802060220.46716.martin.konold@erfrakon.de> 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. Regards, -- martin konold -- e r f r a k o n Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker Sitz: Adolfstra?e 23, 70469 Stuttgart, Partnerschaftsregister Stuttgart PR 126 http://www.erfrakon.com/ From kloecker at kde.org Sat Feb 9 12:33:39 2008 From: kloecker at kde.org (Ingo =?iso-8859-15?q?Kl=F6cker?=) Date: Sat, 09 Feb 2008 11:33:39 -0000 Subject: why did you develop kolab xml format? In-Reply-To: <200802060220.46716.martin.konold@erfrakon.de> References: <200801232248.13511.thomas@koch.ro> <873as7wvie.fsf@home.pardus.de> <200802060220.46716.martin.konold@erfrakon.de> Message-ID: <200802091233.16581@erwin.ingo-kloecker.de> [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 Subject: [Kde-pim] new IETF activity on vCard Date: Sat, 09 Feb 2008 13:49:00 +1100 Size: 9953 Url: http://kolab.org/pipermail/kolab-format/attachments/20080209/0ea6bba8/attachment.txt -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-format/attachments/20080209/0ea6bba8/attachment.bin