This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
This interface deals with the multiple address types that can refer to the same contact, such as vCard fields and URIs.
It can be used to retrieve contacts with a specific addresses
through
The vCard field of the addresses we are requesting. The
field name SHOULD be in lower case. Supported
fields can be found in
The url
vCard field MUST NOT appear here; see
In practice, protocols have a limited set of URI schemes that make sense to resolve as a contact.
A list of strings indicating which D-Bus interfaces the calling process is interested in. All supported attributes from these interfaces, whose values can be obtained without additional network activity, will be in the reply.
Attributes from this interface and from
The behavior of this parameter is similar to the same
parameter in
A mapping from requested vCard addresses to the corresponding contact handles.
Requested addresses that are not valid or understood for this protocol MUST be omitted from the mapping.
A dictionary mapping the contact handles to contact attributes. If any of the requested addresses are in fact invalid, they are simply omitted from this mapping. If contact attributes are not immediately known, the behaviour is defined by the interface; the attribute should either be omitted from the result or replaced with a default value.
Requested addresses that are not valid or understood for this protocol MUST be omitted from the mapping.
Each contact's attributes will always include at least the
identifier that would be obtained by inspecting the handle
(im.telepathy.v1.Connection/contact-id
).
Request contacts and retrieve their attributes using a given field in their vCards.
A list of strings indicating which D-Bus interfaces the calling process is interested in. All supported attributes from these interfaces, whose values can be obtained without additional network activity, will be in the reply.
Attributes from this interface and from
The behavior of this parameter is similar to the same
parameter in
A mapping of requested URIs to the corresponding contact handles.
Requested URIs that are not valid or understood for this protocol MUST be omitted from the mapping.
A dictionary mapping the contact handles to contact attributes. If any of the requested addresses are in fact invalid, they are simply omitted from this mapping. If contact attributes are not immediately known, the behaviour is defined by the interface; the attribute should either be omitted from the result or replaced with a default value.
Requested URIs that are not valid or understood for this protocol MUST be omitted from the mapping.
Each contact's attributes will always include at least the
identifier that would be obtained by inspecting the handle
(im.telepathy.v1.Connection/contact-id
).
Request contacts and retrieve their attributes using URI addresses.
A mapping of vCard fields and addresses equivalent to a
particular contact's protocol identifier. For instance,
on XMPP this would contain x-jabber
for all
contacts, and x-facebook-id
for contacts on
Facebook's server.
x-jabber
.