Make IMPP more compliant with RFC 4770/ RFC 6350
ClosedPublic

Authored by vkrause on Apr 21 2019, 11:04 AM.

Details

Summary

The payload of IMPP entries is supposed to be a URI, the scheme of which
identifies the corresponding messaging service. This can still read the
pre-RFC 4770 service type parameter if no URI scheme is given, but it now
always produces URIs in the output. With RFC 4770 being twelve years old
already I think that's acceptable.

The removal of the type() method also opens the way for adding API for
the type parameter as we have it for other fields as well.

Note that this does not yet touch pre-IMPP messaging entries as currently
used by KAddressbook, that still has to be changed. This also means that
we currently have no users of this code, making these rather invasive
changes possible.

Diff Detail

Repository
R174 PIM: KContacts
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
vkrause created this revision.Apr 21 2019, 11:04 AM
Restricted Application added a project: KDE PIM. · View Herald TranscriptApr 21 2019, 11:04 AM
Restricted Application added a subscriber: kde-pim. · View Herald Transcript
vkrause requested review of this revision.Apr 21 2019, 11:04 AM
mlaurent accepted this revision.Apr 22 2019, 7:31 AM
This revision is now accepted and ready to land.Apr 22 2019, 7:31 AM
This revision was automatically updated to reflect the committed changes.