[Kolab-devel] No x-uid please.

[Christian Mollekopf]

Hey,

After a good talk we have come to the following conclusion:
The format should allow for any uri. Kolab clients SHOULD support both mailto 
and urn, and SHOULD avoid using any other uri format than mailto and urn.

This way we stay within the bounds of xCard and don't need the x-uid property 
while having a clean way to reference contacts (urn) and allow for trivial 
distlist-contacts using mailto.

If a contact has several email addresses, the one marked as preferred SHALL be 
used.

Also this keeps the door open for possible future enhancements (ideas by 
courtesy of Jeroeen):
- distribution list with a single IMAP uri, pointing to an IMAP conversation, 
therefore automatically having everyone in the distribution list involved in 
the conversation so far.
- ldap query as uri, for query based distribution list.
- ....

That's future stuff though

We'd like to apply the same approach for other places where an x-uid element 
was introduced:
- xCal Attendee
- xCard Related

That gives us a bit more development effort in the beginning but gives us the 
powerful solution we need.

Cheers,
Christian

On Wednesday 14 March 2012 10.41:55 Christian Mollekopf wrote:
> On 2012-03-14 9:38, Aleksander Machniak wrote:
> > On 14.03.2012 09:19, Christian Mollekopf wrote:
> >> - The Contact might be moved, breaking the imap link. Additional
> >> complexity we
> >> rather stay away from I think.
> > 
> > The same for change of contact's email address. The same for contact
> > deletion. In all cases distlist must be updated, no matter which
> > method
> > would you choose (Jeroen's or your's). Right?
> 
> When using mailto and x-uid:
> 
> Depends on how you see it. For me the distribution list is fairly
> disconnected from the contact, so no, I wouldn't require updating the
> distlist when changing a contacts email address.
> There is clearly a usecase in such functionality though. If the contact
> is deleted doesn't matter, the mailto remains useful and valid, the
> reference using the UID remains valid, and the contact might reappear,
> reestablishing the link.
> 
> When using a UID for the Member and no x-uid:
> 
> No updates are needed, as the link remains valid, even if the contact
> has been deleted. Again, the link might be reestablished. Of course a
> client would need to cope with not found contacts gracefully.
> In this scenario the Member is dis-functional as there is no mailto
> address available.
> 
> When using a an imap uri for the Member and no x-uid:
> 
> Largely the same as using a UID. The link must be updated though if the
> contact is moved, and the reappearing contact is somewhat problematic as
> it would need to reappear in the same location. So one would need to
> differentiate between move and delete/reappear. One could of course
> fallback to searching the contact based on UID if the imap link is
> broken, and then update the link.
> 
> Cheers,
> Christian
> 
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://www.intevation.de/mailman/listinfo/kolab-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20120314/e6b9e2cd/attachment.sig>