<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Could be mor simple to put preferred="1" in the <email /> entry
instead<br>
to make a duplicate entry <preferred> that is always hard to
maintains.<br>
Example <br>
<email displayname="aa" preferred="1><a class="moz-txt-link-abbreviated" href="mailto:aa@aa.com">aa@aa.com</a></email><br>
<email displayname="bb"> <a class="moz-txt-link-abbreviated" href="mailto:bb@bb.com">bb@bb.com</a></email><br>
<br>
like that e are sure to not have duplicate infos and false info <br>
in case of : <br>
<email displayname="bb"> <a class="moz-txt-link-abbreviated" href="mailto:bb@bb.com">bb@bb.com</a></email><br>
<preferred><br>
<email><a class="moz-txt-link-abbreviated" href="mailto:toto@toto.com">toto@toto.com</a></email><br>
</preferred><br>
<br>
what should be happen ? <br>
<br>
Alain <br>
Regards<br>
<br>
<br>
<br>
Thomas Brüderli a écrit :
<blockquote cite="mid:4E7326BD.2070005@kolabsys.com" type="cite">
<pre wrap="">Alain Abbas wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello
One missing think is in emails fields the "default email" when there are
more than one email
</pre>
</blockquote>
<pre wrap=""><!---->
I guess that's what the <preferred> section is meant or can be used for.
~Thomas
</pre>
<blockquote type="cite">
<pre wrap="">
Georg C. F. Greve a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Dear all,
A new KEP has just been released into public brainstorming:
KEP #13: Update 'contact' object
<a class="moz-txt-link-freetext" href="http://wiki.kolab.org/User:Greve/Drafts/KEP:13">http://wiki.kolab.org/User:Greve/Drafts/KEP:13</a>
This KEP is about updating the 'contact' object which has some well known
issues that we should resolve, and as these are going to be breaking changes,
of which we've had a couple lined up already, I figured it would make sense to
put them all into one changeset so we avoid having too many breaking
transitions.
The state of the KEP is thus that it outlines several of the issues, and
provides some input on how this could be better modeled on the storage level,
but it is still far from complete - in particular as it changes the underlying
way of modeling some of the aspects.
Input and drafting help is very much welcome!
All of that should go <a class="moz-txt-link-abbreviated" href="mailto:tokolab-format@kolab.org">tokolab-format@kolab.org</a>, please.
Best regards,
Georg
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
Kolab-format mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kolab-format@kolab.org">Kolab-format@kolab.org</a>
<a class="moz-txt-link-freetext" href="https://kolab.org/mailman/listinfo/kolab-format">https://kolab.org/mailman/listinfo/kolab-format</a>
</pre>
</blockquote>
<br>
</body>
</html>