Additional note: The Horde applications usually provides a new share 
with a title like: "Addressbook of Max Mustermann". This tends to 
avoid naming conflicts when such shares are made available to other 
users. I feel the Kolab way of approaching this - naming the the 
initial default addressbook "Contacts" - and requiring to distinguish 
the shares by always adding the owner (if not self) is a better way to 
approach this.

Known problem and I consider the Horde applications (or the share 
system) to be the bottleneck here.

I did not analyze the situation in detail again. But as far as I know 
the display of shares does not take duplicate names into account. It 
also varies between the different Horde groupware applications. Within 
the applications the display of share names is usually constructed 
within the specific view. As a result you have some views that display 
the share owner and some don't.

Kolab suggests the following scheme for displaying resources:

http://wiki.kolab.org/UI-Concepts/Folder-Listing

The underlying share system would provide the necessary information to 
render the short hand notation described on the page linked above. But 
I don't think it makes much sense to implement this in each and every 
groupware application.

I think the easiest way to allow Kolab users to distinguish the 
various resources is to extend the Share system so that it can provide 
a clean list of display names. This would then be used within the 
different application.

In any case I think it makes more sense if Jan takes a closer look at 
this one.

Hi,

I just created a notepad called "Foobar". Below that I created another 
notepad in a foreign Kolab client called "Foobar" and another one 
below it called "Foobar".

Currently mnemo / horde will only present one "Foobar" share to me.

I'm not sure yet how we can map the folder machinery in a elegant way.

May be use "Foobar", "Foobar/Foobar" and "Foobar/Foobar/Foobar"?

Cheers,
Thomas