[Kolab-devel] CalDAV Collections vs. IMAP Folders

[Georg C. F. Greve]

On 2013-03-28 09:49, Thomas Brüderli wrote:
> Oh, wait a minute: Jeroen suggested to use /private/comment. Is there 
> a
> /shared/comment, too? According to RFC 5464 there is.

Yes. Jeroen also wants to use it shared & private.


> If this annotation contains the display name for a folder, it should 
> be
> readable for other users you share a folder with. I suggest to write 
> the
> display name to /shared/comment for folders in personal namespace and 
> to
> /private/comment for others.

That's a good start.

You also want to defined behaviour for shared folders, though.

So the logic would likely be based upon admin rights for the folder. 
The only question is: If it is a folder that is not in your personal 
name space, and you have admin rights to it, do you write shared or 
private, or do you perhaps even give users an option for either?


> This becomes essential if you create folders via CalDAV clients that 
> will
> use random UIDs for new folder names. Sharing a folder named
> '1A66C52089EF530F5C20174853981687-8C02E7EEB49870A2' doesn't make sense 
> to
> anybody if one does not see it with the annotated display name.

So how do you plan to address this situation? We need such folders to 
end up sensibly in the folder structure, as well.

Do we need an annotation for the UID?


>>> Should we even consider to create a KEP for this? Reading through 
>>> the
>>> discussion in this thread this shall become the generic display name 
>>> for
>>> all clients and not only for *DAV. Otherwise different clients show
>>> different names for the same folder and I don't think this is 
>>> desirable.
>> 
>> Agreed.
> 
> That will be your job then?

Ehrm, no. :)

Whoever works on this part of Kolab, or finds a volunteer. :)

Best regards,
Georg


-- 
Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Zürich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve