mailto URIs in KEP#17 and libkolabxml

[Thomas Brüderli]

Christian Mollekopf wrote:
> On 2012-03-08 17:39, Thomas Brüderli wrote:
>>> In other places where mailto: uris are required, libkolabxml doesn't
>>> do
>>> anything at all atm. (the string is just passed on) and expects the
>>> client to pass in a valid mailto: uri. The situation is less
>>> complex,
>>> because we don't rely on uri embedded names (because xcal has a cn
>>> parameter). I suppose I can also add automatic mailto: handling
>>> there,
>>> so the clients only have to specify the email address.
>> Using a dedicated mailto struct would simplify things for users of
>> the lib.
>
> There is only the XCard:member property where you can actually make use
> of the name embedding, and there you have a setter/getter for both
> email/name. In all other cases you have only the email address, which is
> now transparently mailto encoded. So there's actually no need for the
> mailto struct (respectively it's not even necessary to expose that
> mailto is involved at all).

Great!

Sorry for the confusion but I was obviously looking at an older version 
of the code where the members list was still a vector of strings:
   DistList::setMembers(const std::vector< std::string > members)

The Member class exactly offers the abstraction I had in mind.

~Thomas