Handling of private/confidential groupware objects

Joon Radley joon at radleys.co.za
Tue Feb 14 13:27:48 CET 2006

Hi Martin,

I find it strange that you want to continue to push this solution as no-one
else except you think that it is a good idea. 

You should create a separate document and include it in your architecture
documentation. This does not pertain to the Kolab-XML format and should not
be included as part of the format specification.

Best regards

Joon Radley
Radley Network Technologies CC
Cell: +27 (0)83 368 8557
Fax: +27 (0)12 998 4346
E-mail: joon at radleys.co.za

> -----Original Message-----
> From: kolab-format-bounces at kolab.org 
> [mailto:kolab-format-bounces at kolab.org] On Behalf Of Martin Konold
> Sent: Tuesday, February 14, 2006 6:26 AM
> To: kolab-format at kolab.org
> Subject: Handling of private/confidential groupware objects
> Hi,
> We need to progress on the format issues and not die in stagnation.
> I hereby want to announce that I am considering to add a 
> section to the Kolab architecture document and the Kolab 
> Format documentation which describes the server side 
> implemented security concept for handling of 
> private/confidential groupware data.
> It will leverage the extra folder hierarchy approach for 
> handling access control.
> I am still undecided if we shall go the practical route using 
> a naming convention or if we shall take the burden to add 
> another namespace to cyrus imapd.
> Most probably I will prefer the former for the initial 
> implementation (Kolab 2 series).
> Do you have any preferences?
> Joon, Johannes and David: Do you want to hint me on any 
> special requirements you are having? 
> Regards,
> -- martin
> --
> http://www.erfrakon.com/
> Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
> _______________________________________________
> Kolab-format mailing list
> Kolab-format at kolab.org
> https://kolab.org/mailman/listinfo/kolab-format

More information about the format mailing list