[Kolab-devel] Missing implementation for xcard properties

[Christian Mollekopf]

On 2012-03-14 12:36, Thomas Brüderli wrote:
> Hello Christian
>
> What's the development status of xcard helper structs like Related 
> and
> Crypto? They both exist but don't still lack implementation.
>
> In order to successfully map all contact properties from the old 
> format
> (and the Roundcube UI) I'd need them to be functional anytime soon.
>

Ok, on it.

> And there are some more contact fields from the old format which 
> don't yet
> have an equivalent in the new format: 'profession' and 'initials'
> Shall they be handled with a CustomProperty?
>

For the profession I suggest creating an affiliation with the name 
"profession", and setting the role with the content of 'profession'.
This way the property remains in the same place for KAddressBook 
(business tab, Profession field). On that note, I noticed that I need to 
update the affiliation section in the docs.
I will make the org property optional, and define a default affiliation 
with the name "profession" for clients which support only one 
affiliation. Such as KAddressBook.

I'm not quite sure about initials.
I think we could allow for several nicknames, and then just append the 
initials as nickname.
 From the RFC: "It can also be used to specify a familiar form of a 
proper name specified by the FN or N properties."
Otherwise we would need another x-property and I don't see that 
justified here.


Here is the list of other missing stuff:

* Reading/Writing of Configuration Objects
* Documentation
* Stable API with Binary Compatibility
* Recurrence exceptions (Not exception dates but as described in 
http://wiki.kolab.org/User:Mollekopf/Drafts/KEP:17#Recurrence_exception)
* Journal contact property
* Contact geo property
* Contact crypto property
* Contact related property

Cheers,
Christian

> ~Thomas
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://www.intevation.de/mailman/listinfo/kolab-devel