1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
|
<?xml version="1.0" ?>
<node name="/Connection_Interface_Contact_Groups" xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
<tp:copyright>Copyright © 2009-2010 Collabora Ltd.</tp:copyright>
<tp:copyright>Copyright © 2009 Nokia Corporation</tp:copyright>
<tp:license xmlns="http://www.w3.org/1999/xhtml">
<p>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.</p>
<p>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.</p>
<p>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.</p>
</tp:license>
<interface name="org.freedesktop.Telepathy.Connection.Interface.ContactGroups">
<tp:requires interface="org.freedesktop.Telepathy.Connection"/>
<tp:requires interface="org.freedesktop.Telepathy.Connection.Interface.ContactList"/>
<tp:added version="0.21.0">(as stable API)</tp:added>
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>An interface for connections in which contacts can be placed in
user-defined groups.</p>
<p>The most basic functionality of this interface is to list and monitor
a contact's set of groups. To do this, use the
<tp:member-ref>GroupsChanged</tp:member-ref> signal, and the
<tp:token-ref>groups</tp:token-ref> contact attribute (this should
usually be done by connecting to the GroupsChanged signal, then
calling <tp:dbus-ref
namespace="ofdT.Connection.Interface.ContactList"
>GetContactListAttributes</tp:dbus-ref> with this interface
included in the Interfaces argument). Simple user interfaces can
limit themselves to displaying that information, and ignore the rest
of this interface: to ensure that this works,
<tp:member-ref>GroupsChanged</tp:member-ref> is emitted for every
change, even if that change could be inferred from another signal
such as <tp:member-ref>GroupsRemoved</tp:member-ref>.</p>
<p>Looking at contacts' lists of groups is sufficient to present a
user interface resembling XMPP's data model, in which groups behave
like tags applied to contacts, and so an empty group cannot exist
or is not interesting. However, some protocols model groups as
objects in their own right. User interfaces may either track
the set of groups via the <tp:member-ref>Groups</tp:member-ref>
property and the <tp:member-ref>GroupsCreated</tp:member-ref> and
<tp:member-ref>GroupsRemoved</tp:member-ref> signals, or ignore
this extra information.</p>
<p>Similarly, in some protocols it is possible to rename a group as
a single atomic operation. Simpler user interfaces will
see the new name being created, the old name being removed, and the
members moving to the new name, via the signals described above.
More advanced user interfaces can optionally distinguish between an
atomic rename and a create/remove pair, and display renamed groups
differently, by monitoring the
<tp:member-ref>GroupRenamed</tp:member-ref> signal.</p>
<p>This interface also provides various methods to manipulate
user-defined groups, which can be expected to work if
<tp:member-ref>GroupStorage</tp:member-ref> is not None.</p>
<p>Depending on the protocol, some methods might be implemented by
more than one protocol operation; for instance, in a
"contact-centric" protocol like XMPP,
<tp:member-ref>SetContactGroups</tp:member-ref> is a single
protocol operation and <tp:member-ref>SetGroupMembers</tp:member-ref>
requires a protocol operation per contact, whereas in a more
"group-centric" protocol it might be the other way around. User
interfaces SHOULD call whichever method most closely resembles the
way in which the user's action was represented in the UI, and
let the connection manager deal with the details.</p>
</tp:docstring>
<property name="DisjointGroups" tp:name-for-bindings="Disjoint_Groups"
access="read" type="b">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>True if each contact can be in at most one group; false if each
contact can be in many groups.</p>
<p>This property cannot change after the connection has moved to the
Connected state. Until then, its value is undefined, and it may
change at any time, without notification.</p>
</tp:docstring>
</property>
<property name="GroupStorage" tp:name-for-bindings="Group_Storage"
type="u" tp:type="Contact_Metadata_Storage_Type" access="read">
<tp:docstring>
<p>Indicates the extent to which contacts' groups can be set and
stored.</p>
<p>This property cannot change after the connection has moved to the
Connected state. Until then, its value is undefined, and it may
change at any time, without notification.</p>
</tp:docstring>
</property>
<tp:contact-attribute name="groups" type="as">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>The names of groups of which a contact is a member.</p>
<p>Change notification is via
<tp:member-ref>GroupsChanged</tp:member-ref>; clients can also
get extra context for group membership changes by receiving
<tp:member-ref>GroupRenamed</tp:member-ref> and
<tp:member-ref>GroupsRemoved</tp:member-ref>.</p>
</tp:docstring>
</tp:contact-attribute>
<signal name="GroupsChanged" tp:name-for-bindings="Groups_Changed">
<tp:docstring>
Emitted when contacts' groups change.
</tp:docstring>
<arg name="Contact" type="au" tp:type="Contact_Handle">
<tp:docstring>The relevant contacts.</tp:docstring>
</arg>
<arg name="Added" type="as">
<tp:docstring>The names of groups to which the contacts were
added.</tp:docstring>
</arg>
<arg name="Removed" type="as">
<tp:docstring>The names of groups from which the contacts were
removed.</tp:docstring>
</arg>
</signal>
<property name="Groups" type="as" access="read"
tp:name-for-bindings="Groups">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>The names of all groups that currently exist. This may be a
larger set than the union of all contacts' <code>groups</code>
contact attributes, if the connection allows groups to be
empty.</p>
<p>Change notification is via
<tp:member-ref>GroupsCreated</tp:member-ref> and
<tp:member-ref>GroupsRemoved</tp:member-ref>; clients can also
distinguish between a create/remove pair and a renamed group by
receiving <tp:member-ref>GroupRenamed</tp:member-ref>.</p>
<p>This property's value is not meaningful until the
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>ContactListState</tp:dbus-ref> has become Success.</p>
</tp:docstring>
</property>
<signal name="GroupsCreated" tp:name-for-bindings="Groups_Created">
<tp:docstring>
Emitted when new, empty groups are created. This will often be
followed by <tp:member-ref>GroupsChanged</tp:member-ref> signals that
add some members.
</tp:docstring>
<arg name="Names" type="as">
<tp:docstring>The names of the new groups.</tp:docstring>
</arg>
</signal>
<signal name="GroupRenamed" tp:name-for-bindings="Group_Renamed">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>Emitted when a group is renamed, in protocols where this can
be distinguished from group creation, removal and membership
changes.</p>
<p>Immediately after this signal is emitted,
<tp:member-ref>GroupsCreated</tp:member-ref> MUST signal the
creation of a group with the new name, and
<tp:member-ref>GroupsRemoved</tp:member-ref> MUST signal the
removal of a group with the old name.</p>
<tp:rationale>
<p>Emitting these extra signals, in this order, means that clients
that are interested in the set of groups that exist (but treat a
rename and a create/remove pair identically) can ignore the
GroupRenamed signal entirely.</p>
</tp:rationale>
<p>If the group was not empty, immediately after those signals are
emitted, <tp:member-ref>GroupsChanged</tp:member-ref> MUST signal
that the members of that group were removed from the old name
and added to the new name.</p>
<p>On connection managers where groups behave like tags, renaming a
group MAY be signalled as a set of
<tp:member-ref>GroupsCreated</tp:member-ref>,
<tp:member-ref>GroupsRemoved</tp:member-ref> and
<tp:member-ref>GroupsChanged</tp:member-ref> signals, instead of
emitting this signal.</p>
<tp:rationale>
<p>On protocols like XMPP, another resource "renaming a group" is
indistinguishable from changing contacts' groups individually.</p>
</tp:rationale>
</tp:docstring>
<arg name="Old_Name" type="s">
<tp:docstring>The old name of the group.</tp:docstring>
</arg>
<arg name="New_Name" type="s">
<tp:docstring>The new name of the group.</tp:docstring>
</arg>
</signal>
<signal name="GroupsRemoved" tp:name-for-bindings="Groups_Removed">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>Emitted when one or more groups are removed. If they had members at
the time that they were removed, then immediately after this signal
is emitted, <tp:member-ref>GroupsChanged</tp:member-ref> MUST signal
that their members were removed.</p>
<tp:rationale>
<p>Emitting the signals in this order allows for two modes of
operation. A client interested only in a contact's set of groups
can ignore <tp:member-ref>GroupsRemoved</tp:member-ref> and rely
on the <tp:member-ref>GroupsChanged</tp:member-ref> signal that
will follow; a more elaborate client wishing to distinguish between
all of a group's members being removed, and the group itself
being removed, can additionally watch for
<tp:member-ref>GroupsRemoved</tp:member-ref> and use it to
disambiguate.</p>
</tp:rationale>
</tp:docstring>
<arg name="Names" type="as">
<tp:docstring>The names of the groups.</tp:docstring>
</arg>
</signal>
<method name="SetContactGroups" tp:name-for-bindings="Set_Contact_Groups">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>Add the given contact to the given groups (creating new groups
if necessary), and remove them from all other groups.</p>
<tp:rationale>
<p>This is the easiest and most correct way to implement user
interfaces that display a single contact with a list of groups,
resulting in a user expectation that when they apply the changes,
the contact's set of groups will become exactly what was
displayed.</p>
</tp:rationale>
<p>If the user is removed from a group of which they were the only
member, the group MAY be removed automatically.</p>
<tp:rationale>
<p>In protocols like XMPP where groups behave like tags, a group
with no members has no protocol representation.</p>
</tp:rationale>
<p>Any <tp:member-ref>GroupsCreated</tp:member-ref>,
<tp:member-ref>GroupsChanged</tp:member-ref> and
<tp:member-ref>GroupsRemoved</tp:member-ref> signals that result from
this method call MUST be emitted before the method returns.</p>
<p>This method SHOULD NOT be called until the
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>ContactListState</tp:dbus-ref> changes to Success.
If the ContactListState is Failure, this method SHOULD raise the
same error as
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>GetContactListAttributes</tp:dbus-ref>.</p>
</tp:docstring>
<arg name="Contact" type="u" tp:type="Contact_Handle" direction="in">
<tp:docstring>The contact to alter.</tp:docstring>
</arg>
<arg name="Groups" type="as" direction="in">
<tp:docstring>The set of groups which the contact should be
in.</tp:docstring>
</arg>
<tp:possible-errors>
<tp:error name="org.freedesktop.Telepathy.Error.Disconnected"/>
<tp:error name="org.freedesktop.Telepathy.Error.InvalidHandle"/>
<tp:error name="org.freedesktop.Telepathy.Error.NetworkError"/>
<tp:error name="org.freedesktop.Telepathy.Error.NotAvailable">
<tp:docstring>Raised if <tp:member-ref>DisjointGroups</tp:member-ref>
is true and the list of groups has more than one
member.</tp:docstring>
</tp:error>
<tp:error name="org.freedesktop.Telepathy.Error.NotImplemented">
<tp:docstring>
Raised if <tp:member-ref>GroupStorage</tp:member-ref>
is Contact_Metadata_Storage_Type_None, i.e. groups cannot be edited.
</tp:docstring>
</tp:error>
<tp:error name="org.freedesktop.Telepathy.Error.NotYet"/>
</tp:possible-errors>
</method>
<method name="SetGroupMembers" tp:name-for-bindings="Set_Group_Members">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>Add the given members to the given group (creating it if necessary),
and remove all other members.</p>
<tp:rationale>
<p>This is the easiest and most correct way to implement user
interfaces that display a single group with a list of contacts,
resulting in a user expectation that when they apply the changes,
the groups's set of members will become exactly what was
displayed.</p>
</tp:rationale>
<p>If <tp:member-ref>DisjointGroups</tp:member-ref> is true,
this will also remove each member from their previous group.</p>
<p>If the user is removed from a group of which they were the only
member, the group MAY be removed automatically.</p>
<p>Any <tp:member-ref>GroupsCreated</tp:member-ref>,
<tp:member-ref>GroupsChanged</tp:member-ref> and
<tp:member-ref>GroupsRemoved</tp:member-ref> signals that result from
this method call MUST be emitted before the method returns.</p>
<p>This method SHOULD NOT be called until the
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>ContactListState</tp:dbus-ref> changes to Success.
If the ContactListState is Failure, this method SHOULD raise the
same error as
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>GetContactListAttributes</tp:dbus-ref>.</p>
</tp:docstring>
<arg name="Group" type="s" direction="in">
<tp:docstring>The group to alter.</tp:docstring>
</arg>
<arg name="Members" type="au" tp:type="Contact_Handle[]" direction="in">
<tp:docstring>The set of members for the group. If this set is
empty, this method MAY remove the group.</tp:docstring>
</arg>
<tp:possible-errors>
<tp:error name="org.freedesktop.Telepathy.Error.Disconnected"/>
<tp:error name="org.freedesktop.Telepathy.Error.InvalidHandle"/>
<tp:error name="org.freedesktop.Telepathy.Error.NetworkError"/>
<tp:error name="org.freedesktop.Telepathy.Error.NotImplemented">
<tp:docstring>
Raised if <tp:member-ref>GroupStorage</tp:member-ref>
is Contact_Metadata_Storage_Type_None, i.e. groups cannot be edited.
</tp:docstring>
</tp:error>
<tp:error name="org.freedesktop.Telepathy.Error.NotYet"/>
</tp:possible-errors>
</method>
<method name="AddToGroup" tp:name-for-bindings="Add_To_Group">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>Add the given members to the given group, creating it if
necessary.</p>
<p>If <tp:member-ref>DisjointGroups</tp:member-ref> is true,
this will also remove each member from their previous group.</p>
<tp:rationale>
<p>This is good for user interfaces in which you can edit groups
via drag-and-drop.</p>
</tp:rationale>
<p>Any <tp:member-ref>GroupsCreated</tp:member-ref>,
<tp:member-ref>GroupsChanged</tp:member-ref> and
<tp:member-ref>GroupsRemoved</tp:member-ref> signals that result from
this method call MUST be emitted before the method returns.</p>
<p>This method SHOULD NOT be called until the
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>ContactListState</tp:dbus-ref> changes to Success.
If the ContactListState is Failure, this method SHOULD raise the
same error as
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>GetContactListAttributes</tp:dbus-ref>.</p>
</tp:docstring>
<arg name="Group" type="s" direction="in">
<tp:docstring>The group to alter.</tp:docstring>
</arg>
<arg name="Members" type="au" tp:type="Contact_Handle[]" direction="in">
<tp:docstring>The set of members to include in the group.</tp:docstring>
</arg>
<tp:possible-errors>
<tp:error name="org.freedesktop.Telepathy.Error.Disconnected"/>
<tp:error name="org.freedesktop.Telepathy.Error.InvalidHandle"/>
<tp:error name="org.freedesktop.Telepathy.Error.NetworkError"/>
<tp:error name="org.freedesktop.Telepathy.Error.NotImplemented">
<tp:docstring>
Raised if <tp:member-ref>GroupStorage</tp:member-ref>
is Contact_Metadata_Storage_Type_None, i.e. groups cannot be edited.
</tp:docstring>
</tp:error>
<tp:error name="org.freedesktop.Telepathy.Error.NotYet"/>
</tp:possible-errors>
</method>
<method name="RemoveFromGroup" tp:name-for-bindings="Remove_From_Group">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>Remove the given members from the given group.</p>
<tp:rationale>
<p>This is good for user interfaces in which you can edit groups
via drag-and-drop.</p>
</tp:rationale>
<p>Any <tp:member-ref>GroupsChanged</tp:member-ref> or
<tp:member-ref>GroupsRemoved</tp:member-ref> signals that result from
this method call MUST be emitted before the method returns.</p>
<p>This method SHOULD NOT be called until the
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>ContactListState</tp:dbus-ref> changes to Success.
If the ContactListState is Failure, this method SHOULD raise the
same error as
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>GetContactListAttributes</tp:dbus-ref>.</p>
</tp:docstring>
<arg name="Group" type="s" direction="in">
<tp:docstring>The group to alter. If it does not exist, then it has
no members by definition, so this method SHOULD return
successfully.</tp:docstring>
</arg>
<arg name="Members" type="au" tp:type="Contact_Handle[]" direction="in">
<tp:docstring>The set of members to remove from the group. It is not
an error to remove members who are already not in the group.
If there are no members left in the group afterwards, the group MAY
itself be removed.</tp:docstring>
</arg>
<tp:possible-errors>
<tp:error name="org.freedesktop.Telepathy.Error.Disconnected"/>
<tp:error name="org.freedesktop.Telepathy.Error.InvalidHandle"/>
<tp:error name="org.freedesktop.Telepathy.Error.NetworkError"/>
<tp:error name="org.freedesktop.Telepathy.Error.NotImplemented">
<tp:docstring>
Raised if <tp:member-ref>GroupStorage</tp:member-ref>
is Contact_Metadata_Storage_Type_None, i.e. groups cannot be edited.
</tp:docstring>
</tp:error>
<tp:error name="org.freedesktop.Telepathy.Error.NotYet"/>
</tp:possible-errors>
</method>
<method name="RemoveGroup" tp:name-for-bindings="Remove_Group">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>Remove all members from the given group, then remove the group
itself. If the group already does not exist, this method SHOULD
return successfully.</p>
<p>Any <tp:member-ref>GroupsChanged</tp:member-ref> or
<tp:member-ref>GroupsRemoved</tp:member-ref> signals that result from
this method call MUST be emitted before the method returns.</p>
<p>This method SHOULD NOT be called until the
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>ContactListState</tp:dbus-ref> changes to Success.
If the ContactListState is Failure, this method SHOULD raise the
same error as
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>GetContactListAttributes</tp:dbus-ref>.</p>
</tp:docstring>
<arg name="Group" type="s" direction="in">
<tp:docstring>The group to remove.</tp:docstring>
</arg>
<tp:possible-errors>
<tp:error name="org.freedesktop.Telepathy.Error.Disconnected"/>
<tp:error name="org.freedesktop.Telepathy.Error.NetworkError"/>
<tp:error name="org.freedesktop.Telepathy.Error.NotImplemented">
<tp:docstring>
Raised if <tp:member-ref>GroupStorage</tp:member-ref>
is Contact_Metadata_Storage_Type_None, i.e. groups cannot be edited.
</tp:docstring>
</tp:error>
<tp:error name="org.freedesktop.Telepathy.Error.NotYet"/>
</tp:possible-errors>
</method>
<method name="RenameGroup" tp:name-for-bindings="Rename_Group">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>Rename the given group.</p>
<p>On protocols where groups behave like tags, this is an API
short-cut for adding all of the group's members to a group with
the new name, then removing the old group.</p>
<tp:rationale>
<p>Otherwise, clients can't perform this operation atomically, even
if the connection could.</p>
</tp:rationale>
<p>Any <tp:member-ref>GroupRenamed</tp:member-ref> or
<tp:member-ref>GroupsRemoved</tp:member-ref> signals that result from
this method call MUST be emitted before the method returns.</p>
<p>This method SHOULD NOT be called until the
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>ContactListState</tp:dbus-ref> changes to Success.
If the ContactListState is Failure, this method SHOULD raise the
same error as
<tp:dbus-ref namespace="ofdT.Connection.Interface.ContactList"
>GetContactListAttributes</tp:dbus-ref>.</p>
</tp:docstring>
<arg name="Old_Name" type="s" direction="in">
<tp:docstring>The group to rename.</tp:docstring>
</arg>
<arg name="New_Name" type="s" direction="in">
<tp:docstring>The new name for the group.</tp:docstring>
</arg>
<tp:possible-errors>
<tp:error name="org.freedesktop.Telepathy.Error.Disconnected"/>
<tp:error name="org.freedesktop.Telepathy.Error.NetworkError"/>
<tp:error name="org.freedesktop.Telepathy.Error.NotImplemented">
<tp:docstring>
Raised if <tp:member-ref>GroupStorage</tp:member-ref>
is Contact_Metadata_Storage_Type_None, i.e. groups cannot be edited.
</tp:docstring>
</tp:error>
<tp:error name="org.freedesktop.Telepathy.Error.DoesNotExist">
<tp:docstring>Raised if there is no group with that
name.</tp:docstring>
</tp:error>
<tp:error name="org.freedesktop.Telepathy.Error.NotAvailable">
<tp:docstring>Raised if there is already a group with the new
name.</tp:docstring>
</tp:error>
<tp:error name="org.freedesktop.Telepathy.Error.NotYet"/>
</tp:possible-errors>
</method>
</interface>
</node>
<!-- vim:set sw=2 sts=2 et ft=xml: -->
|
