Commit 618591b236c204e97155ab016de60d0d64afaa05 - telepathy-spec

Merge commit 'upstream/0.21.11' into debian Sjoerd Simons 13 years ago

22 changed file(s) with 1186 addition(s) and 111 deletion(s). Raw diff Collapse all Expand all

+326

-0

ChangeLog less more

	0	commit 8270839e6c706be8260917ab9b8d3b1b14c874a6
	1	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	2	Date: Fri Mar 4 13:34:06 2011 +0100
	3
	4	set version of Observer.DelayApprovers
	5
	6	commit a1f56ae563524abe04aa57aa5a1063cc0563420a
	7	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	8	Date: Thu Mar 3 14:33:23 2011 +0100
	9
	10	prepare 0.21.11
	11
	12	commit 177372c96aec2aa3fe9c7ae6c0acbcda220bbb96
	13	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	14	Date: Thu Mar 3 13:23:54 2011 +0100
	15
	16	remove comment regarding DelayApprovers as it has been merged
	17
	18	commit 81de98c91752b64b7d9ce8cc6da69b8768ed5e40
	19	Merge: a27934a 011b586
	20	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	21	Date: Thu Mar 3 13:14:30 2011 +0100
	22
	23	Merge branch 'delay-approver'
	24
	25	commit 011b586edfff7a3f324f05f5f09022fee4df5490
	26	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	27	Date: Thu Mar 3 12:11:41 2011 +0100
	28
	29	document which MC version implements DelayApprovers
	30
	31	commit a27934af2c5fbe246ce201124146f801f6241af7
	32	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	33	Date: Thu Mar 3 12:52:13 2011 +1100
	34
	35	Mark Chan.I.CredentialsStorage as causes-havoc
	36
	37	commit 0de9ca669e9cde36128c20ee1ffadb9640d56c9f
	38	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	39	Date: Tue Mar 1 11:46:50 2011 +0100
	40
	41	document the default value of Observer.DelayApprovers
	42
	43	commit 59c5560ca5ef9e4cffd2ffbb783341fed22d3a4f
	44	Author: Will Thompson <will.thompson@collabora.co.uk>
	45	Date: Thu Feb 24 15:39:58 2011 +0000
	46
	47	ChannelRequest: clear up preamble
	48
	49	commit c6c42a75de9ef578c0d321fe53b0fc18f84cdd3b
	50	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	51	Date: Thu Feb 24 12:29:42 2011 +0100
	52
	53	start dev of next version
	54
	55	commit 06f3aa25a31c8a68b0737c40cf6f98f541590863
	56	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	57	Date: Thu Feb 24 12:26:34 2011 +0100
	58
	59	set version of new API
	60
	61	commit ea5270ab074462386fa6f74e7cc2100824316052
	62	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	63	Date: Thu Feb 24 12:17:11 2011 +0100
	64
	65	prepare 0.21.10
	66
	67	commit 934a0985c4b9757d56bc63b4c9c6b253443c6aed
	68	Merge: 1af47cc e2e7b9b
	69	Author: Will Thompson <will.thompson@collabora.co.uk>
	70	Date: Tue Feb 22 16:23:21 2011 +0000
	71
	72	Merge branch 'unset-DBus_Property-parameter'
	73
	74	Reviewed-by: Danielle Madeley <danielle.madeley@collabora.co.uk>
	75
	76	commit e2e7b9b212efe87eb88de9556b5b39eebe92ef49
	77	Author: Will Thompson <will.thompson@collabora.co.uk>
	78	Date: Mon Feb 21 18:44:14 2011 +0000
	79
	80	Update CM naming rationale for Rakia renaming
	81
	82	commit 92233fb3f1046fbd6df13910b84167961f649d76
	83	Author: Will Thompson <will.thompson@collabora.co.uk>
	84	Date: Mon Feb 21 18:16:43 2011 +0000
	85
	86	Document how unsetting DBus_Property parameters works
	87
	88	What the account manager should do when unsetting parameters which have
	89	the DBus_Property flag was not previously specified. Having fixed MC,
	90	let's fix the spec to match what I implemented: when unsetting, use the
	91	default value if possible; and in general, if the change has no
	92	practical effect, don't claim we need a reconnect.
	93
	94	See: <https://bugs.freedesktop.org/show_bug.cgi?id=34316>
	95
	96	commit 1af47cc711a1924bb135f57a7dd423d1124fcc18
	97	Merge: 64c042f 37d63ee
	98	Author: Jonathon Jongsma <jonathon.jongsma@collabora.co.uk>
	99	Date: Mon Feb 21 11:13:49 2011 -0600
	100
	101	Merge branch 'account-storage'
	102
	103	commit 37d63ee6316537f02c345c60f6383f775d54d605
	104	Author: Jonathon Jongsma <jonathon.jongsma@collabora.co.uk>
	105	Date: Tue Feb 15 22:14:01 2011 -0600
	106
	107	Updates from review
	108
	109	Add some cross-references, clarify some documentation, fix formatting, etc. See
	110	bug #33485 for review comments.
	111
	112	commit 322afbcee805370308605fd1f1627ebe1a55f240
	113	Author: Will Thompson <will.thompson@collabora.co.uk>
	114	Date: Mon Feb 21 12:22:39 2011 +0000
	115
	116	Account.Parameters: clarify reference to Set().
	117
	118	commit 64c042f5fe1ac631059f0383ac976ca1474a7c0f
	119	Merge: 18dc63c de0a103
	120	Author: Will Thompson <will.thompson@collabora.co.uk>
	121	Date: Wed Feb 16 18:00:10 2011 +0000
	122
	123	Merge branch 'hidden'
	124
	125	commit 18dc63c416ba9f56a6c1b83adba0e8b961f05ff1
	126	Author: Will Thompson <will.thompson@collabora.co.uk>
	127	Date: Fri Feb 4 09:36:12 2011 +0100
	128
	129	Remove stale NMC 4.x references in Account rationales
	130
	131	Reviewed-by: Danielle Madeley <danielle.madeley@collabora.co.uk>
	132
	133	commit 86298691fc2ec14c7f8bf617732a0985f4dc438f
	134	Author: Jonathon Jongsma <jonathon.jongsma@collabora.co.uk>
	135	Date: Thu Jan 6 17:02:35 2011 -0600
	136
	137	Add initial Call.Content.I.VideoControl interface
	138
	139	https://bugs.freedesktop.org/show_bug.cgi?id=32900
	140
	141	commit 23d7a8c9c5eb69b2ee914f53f7231fcb7bc8e2a0
	142	Author: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
	143	Date: Tue Feb 1 11:15:26 2011 +0000
	144
	145	s/telepathy-farsight/telepathy-farstream/g for Call
	146
	147	commit 3c68f96ce6504e1829de6e3ccfc0f857df44e2d9
	148	Author: Jonny Lamb <jonny.lamb@collabora.co.uk>
	149	Date: Mon Jan 3 15:46:21 2011 +0000
	150
	151	Observer: document how to implement non-interactive approvers
	152
	153	Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
	154
	155	commit 13cff5d19506aa32097efa730c01e9965d34daee
	156	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	157	Date: Fri Jan 28 15:34:19 2011 +0100
	158
	159	Bump nano-version to 0.21.9.1
	160
	161	commit f460a62bacd2ea44e9da639cfbb52f4b0b862ba7
	162	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	163	Date: Fri Jan 28 15:23:08 2011 +0100
	164
	165	Version 0.21.9
	166
	167	commit 19ed4e30ac7348b070329ab0fb77a9eda6169282
	168	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	169	Date: Fri Jan 28 15:22:59 2011 +0100
	170
	171	Update NEWS for 0.21.9
	172
	173	commit eeb8bf89b410317a3feb0430461999da7a1c7a7e
	174	Merge: 9e6b2b9 059ae85
	175	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	176	Date: Fri Jan 28 15:01:43 2011 +0100
	177
	178	Merge branch 'ft-uri-32434'
	179
	180	commit 059ae852fa9c5ce3c88196851b06e8ee041d5351
	181	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	182	Date: Fri Jan 28 14:55:34 2011 +0100
	183
	184	be more clear about the type of URI stored in FileTransfer.URI
	185
	186	Kudos to Will for this nice explanation.
	187
	188	commit cbd4ca144e8901752c14b9de99a63b111b6cf5c3
	189	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	190	Date: Wed Jan 26 13:08:18 2011 +0100
	191
	192	explain the type of URI
	193
	194	commit 9bbdb6499caedb84ecfc605e2a0d7dd0c34742ab
	195	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	196	Date: Wed Jan 26 12:54:48 2011 +0100
	197
	198	rename FileURI to URI
	199
	200	commit 77e08e0e6c779d79a6bcf984e3171eb8008a397a
	201	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	202	Date: Wed Jan 26 12:52:35 2011 +0100
	203
	204	s/fired/emitted
	205
	206	commit 67d9f7017e58188ba4c5af1397d1c77390a74833
	207	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	208	Date: Wed Jan 26 12:51:01 2011 +0100
	209
	210	rephrase the description of FileURIDefined
	211
	212	commit 27954e0916e82da9ea2e01ca028a1743497da05f
	213	Author: Jonathon Jongsma <jonathon.jongsma@collabora.co.uk>
	214	Date: Tue Jan 25 11:06:38 2011 -0600
	215
	216	Add Channel.Interface.CredentialsStorage
	217
	218	This interface provides a way for a client to instruct the connection manager
	219	that the credentials should be saved in the CM in order to avoid future SASL
	220	negotiations in the future.
	221
	222	commit a9b06fb75a55d9b178123e3c5f996b5e0f73235b
	223	Author: Jonathon Jongsma <jonathon.jongsma@collabora.co.uk>
	224	Date: Tue Jan 25 11:05:28 2011 -0600
	225
	226	Add a flag to SASL channels indicating whether the password can be saved
	227
	228	Sometimes a password should not be stored in the system keyring, so we need a
	229	flag on the SASL authentication channels to indicate when a client may save the
	230	password and when it may not.
	231
	232	commit cf387087279d9a9cc76b53643d53b743cd8282b0
	233	Author: Jonathon Jongsma <jonathon.jongsma@collabora.co.uk>
	234	Date: Tue Jan 25 11:04:30 2011 -0600
	235
	236	Add Account.Interface.ExternalPasswordStorage
	237
	238	An interface for an account whose password can be stored in the connection
	239	manager rather than in the system keyring, etc.
	240
	241	commit f2cf42f66aff9d29bf4b04558b8fa30053bfb186
	242	Author: Jonathon Jongsma <jonathon.jongsma@collabora.co.uk>
	243	Date: Tue Jan 25 11:03:01 2011 -0600
	244
	245	Add ConnectionManager.Interface.AccountStorage
	246
	247	commit 9e6b2b957b144f3d14ce54c3c190429afb33fdd6
	248	Author: David Laban <david.laban@collabora.co.uk>
	249	Date: Tue Jan 25 16:10:52 2011 +0000
	250
	251	Add Stream_Component tp:type
	252
	253	It turns out that farsight complains if you give it anything other than
	254	1 or 2, and magic numbers are bad m'kay.
	255
	256	commit 6ced9b591ee5511cfdb8978ceaf0c8c33a077190
	257	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	258	Date: Tue Jan 25 15:55:50 2011 +0100
	259
	260	FileTransfer: add a FileURI property (fdo #32434)
	261
	262	commit cc2887eb45d6e029de056c8aecad4c368dfbe547
	263	Author: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
	264	Date: Tue Jan 25 14:32:22 2011 +0000
	265
	266	Change the candidate port member from q to u
	267
	268	Unfortunately some binding are unable to create dbus elements with type
	269	q as part of an array (hello, dbus-glib, i'm looking you). To be
	270	nice to such bindings change the type to u (32bit uint instead of 16 bit)
	271
	272	commit ca7a0fc514366fdd9c85d57ab316a738136bf343
	273	Author: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
	274	Date: Mon Jan 17 13:40:26 2011 +0000
	275
	276	Move packetization from Content to Content.Interface.Media
	277
	278	commit de0a103811b43340803fa562c39f0b163e3e3dc5
	279	Author: Will Thompson <will.thompson@collabora.co.uk>
	280	Date: Fri Jan 14 11:12:36 2011 +0000
	281
	282	Account.I.Hidden: Add introduction and rationale.
	283
	284	commit f4f8e25103703f94297db3422e2a074a01afb2ef
	285	Author: Will Thompson <will.thompson@collabora.co.uk>
	286	Date: Wed Dec 1 18:01:29 2010 +0000
	287
	288	Add a first cut at A[M].Interface.Hidden.
	289
	290	commit 3fdfa27deea1b7204d458a126e015bddf87b92dc
	291	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	292	Date: Thu Dec 23 11:23:03 2010 +1100
	293
	294	DTMF may also appear on Call channels, update descriptive text
	295
	296	commit 8d02d9bc48da5822cadac49bc2df9d463723306d
	297	Author: Will Thompson <will.thompson@collabora.co.uk>
	298	Date: Mon Dec 20 17:15:22 2010 +0000
	299
	300	Bump nano-version to 0.21.8.1
	301
0	302	commit d597545bfd2f759f454a03cc655f6b9362489f6b
1	303	Author: Will Thompson <will.thompson@collabora.co.uk>
2	304	Date: Mon Dec 20 17:04:49 2010 +0000

206	508	Date: Fri Dec 10 11:18:05 2010 +1100
207	509
208	510	Merge branch 'sms'
	511
	512	commit 231f722bbeffb857e5df7e1491876631d76342a1
	513	Author: Jonny Lamb <jonny.lamb@collabora.co.uk>
	514	Date: Thu Dec 9 16:20:25 2010 +0000
	515
	516	Observer: add an example of DelayApprovers in a client file
	517
	518	Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
	519
	520	commit 725a947051e7b4e06929578a5f6afb9bfb36a338
	521	Author: Jonny Lamb <jonny.lamb@collabora.co.uk>
	522	Date: Thu Dec 9 16:04:54 2010 +0000
	523
	524	Observer: add tp:added element to DelayApprovers
	525
	526	Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
	527
	528	commit 3efce500ccd1bbbc72795a9b70bdbcae4d95c512
	529	Author: Jonny Lamb <jonny.lamb@collabora.co.uk>
	530	Date: Thu Dec 9 15:52:48 2010 +0000
	531
	532	Observer: add a DelayApprovers property
	533
	534	Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
209	535
210	536	commit 4925e71c8cdf50c650d3c3aed9843678eb2c54e9
211	537	Merge: 04fe7c2 fa92dec

+62

-0

NEWS less more

0	0	This file contains the same edited highlights as the announcement emails.
1	1	For full details, see the ChangeLog in tarballs, or "git log" in Git
2	2	checkouts.
	3
	4	telepathy-spec 0.21.11 (2011-03-04)
	5	===================================
	6
	7	New stable API:
	8
	9	• Add Observer.DelayApprovers property indicating whether the channel dispatcher
	10	should wait for ObserveChannels to return before calling
	11	Approver.AddDispatchOperation on appropriate Approvers.
	12
	13	telepathy-spec 0.21.10 (2011-02-24)
	14	===================================
	15
	16	“Cold as shadows over European eyes”
	17
	18	New stable API:
	19
	20	• Add SASLAuthentication.MaySaveResponse property indicating whether the
	21	password can be saved.
	22
	23	New experimental API:
	24
	25	• Account.Interface.Hidden.DRAFT1 and AccountManager.Interface.Hidden.DRAFT1:
	26	new interfaces for flagging certain accounts as hidden, so that they do not
	27	appear in the account manager's standard lists of accounts.
	28
	29	• ConnectionManager.Interface.AccountStorage.DRAFT: an interface for connection
	30	managers that store account details internally.
	31
	32	• Account.Interface.ExternalPasswordStorage.DRAFT: an interface for Accounts
	33	whose passwords are stored externally.
	34
	35	• Channel.Interface.CredentialsStorage.DRAFT: a channel interface for SASL
	36	authentication channels that can save the credentials in the connection manager.
	37
	38	• Call.Content.Interface.VideoControl.DRAFT: an interface that allows the
	39	connection manager to control the video stream.
	40
	41	Clarifications:
	42
	43	• Document how to implement non-interactive approvers.
	44
	45	• Document how unsetting DBus_Property parameters works in Account and
	46	ConnectionManager.
	47
	48	telepathy-spec 0.21.9 (2011-01-28)
	49	==================================
	50
	51	“Are you ready for what's coming?”
	52
	53	“Ready as I'll ever be.”
	54
	55	New stable API:
	56
	57	• Add a FileTransfer.URI property which can be used to tell other
	58	Telepathy clients about the location of the transferred
	59	file. (fdo#32434, cassidy)
	60
	61	Changes to unstable API:
	62
	63	• Move the Packetization property from Call.Content to
	64	Call.Content.Interface.Media (sjoerd)
3	65
4	66	telepathy-spec 0.21.8 (2010-12-20)
5	67	==================================

+19

-39

spec/Account.xml less more

161	161	user at account creation time. The account creation user interface
162	162	is responsible for setting a reasonable default value in the user's
163	163	locale; something like "Jabber (bob@example.com)" would be sensible.
164
165		<tp:rationale>
166		This approximately corresponds to "display name" in NMC 4.x and
167		Decibel.
168		</tp:rationale>
169	164	</tp:docstring>
170	165	</property>
171	166

176	171	or the empty string to not specify an icon. If the icon is set to
177	172	an empty string, the account manager or any client MAY derive a
178	173	default icon, for instance from the protocol.
179
180		<tp:rationale>
181		This approximately corresponds to mc_profile_get_icon_name
182		(or possibly mc_profile_get_branding_icon_name) in NMC 4.x.
183		It's accessed via the account rather than the profile because
184		we no longer have profiles as a core concept.
185		</tp:rationale>
186	174	</tp:docstring>
187	175	</property>
188	176

255	243	name for them in our contact list (a "handle" or "pet name" as
256	244	described in XEP-0165 and its references). The terminology change
257	245	from alias to nickname here is a step in that direction.
258		This corresponds to NMC 4.x mc_account_get_alias.
259	246	</tp:rationale>
260	247	</tp:docstring>
261	248	</property>

317	304	only those parameters that are stored for this account, and SHOULD
318	305	only include those parameters that the user has explicitly set.
319	306	</p>
320		<p>This property cannot be altered using Set() - use
	307	<p>This property cannot be altered using
	308	<code>org.freedesktop.DBus.Properties.Set()</code>; use
321	309	<tp:member-ref>UpdateParameters</tp:member-ref> instead.</p>
322	310	</tp:docstring>
323	311	</property>

327	315	<p>Change the value of the <tp:member-ref>Parameters</tp:member-ref>
328	316	property.</p>
329	317
330		<p>If any of the changed parameters'
	318	<p>If any of the <var>Set</var> parameters’
331	319	<tp:type>Conn_Mgr_Param_Flags</tp:type> include
332	320	<code>DBus_Property</code>, the change will be applied immediately to
333		the
334		corresponding D-Bus Property on the active
335		<tp:member-ref>Connection</tp:member-ref>, if there is one. Changes to
336		other parameters will not take effect until the next time the account
337		is disconnected and reconnected.</p>
	321	the corresponding D-Bus Property on the active
	322	<tp:member-ref>Connection</tp:member-ref>, if there is one. If any of
	323	the <var>Unset</var> parameters’
	324	<tp:type>Conn_Mgr_Param_Flags</tp:type> include both
	325	<code>DBus_Property</code> and <code>Has_Default</code>, the
	326	corresponding D-Bus Property on the connection will be set to the
	327	default value. Changes to other parameters will not take effect
	328	until the next time the account is disconnected and reconnected. (If
	329	parameters are explicitly set to their default value, or are unset
	330	when previously set to their default value, the account manager MAY
	331	decide that no reconnection is necessary to make the change take
	332	effect.)</p>
338	333
339	334	<tp:rationale>
340	335	<p>In general, reconnecting is a destructive operation that shouldn't

373	368
374	369	<arg name="Reconnect_Required" type="as" direction="out">
375	370	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
376		<p>If all of the parameters had the <code>DBus_Property</code> flag,
	371	<p>If all of the updates could be applied to the active
	372	<tp:member-ref>Connection</tp:member-ref> (if any),
377	373	the empty list, signifying that no reconnection is required for the
378	374	new parameters to take effect. For example, if the only parameter
379	375	updated is <tt>...Cellular.<tp:dbus-ref

440	436	requested by the user (for
441	437	instance, if the user tries to start a conversation using this
442	438	account).
443
444		<tp:rationale>
445		This approximately corresponds to NMC 4.x "enabled" and Decibel
446		"autoreconnect".
447		</tp:rationale>
448	439	</tp:docstring>
449	440	</property>
450	441

481	472	<tp:rationale>
482	473	If the AM is doing some sort of backoff/delay on reconnection
483	474	attempts, the account's status is conceptually "Connecting" even
484		though there is no Connection. This vaguely corresponds to
485		GetCurrentStatus in NMC 4.x.
	475	though there is no Connection.
486	476	</tp:rationale>
487	477	</tp:docstring>
488	478	</property>

498	488
499	489	<tp:rationale>
500	490	If you weren't watching the Connection at the time it failed,
501		you can't tell why - unless the AM can tell you. This is part
502		of GetCurrentStatus in NMC 4.x.
	491	you can't tell why - unless the AM can tell you.
503	492	</tp:rationale>
504	493	</tp:docstring>
505	494	</property>

567	556	interface, the type SHOULD be Connection_Presence_Type_Unset.
568	557	The account manager is expected to set this by observing signals
569	558	from the Connection.
570
571		<tp:rationale>
572		This corresponds to GetPresenceActual in NMC 4.x.
573		</tp:rationale>
574	559	</tp:docstring>
575	560	</property>
576	561

587	572	<p>When the account manager automatically connects an account,
588	573	it must signal this by setting the RequestedPresence to the same
589	574	thing as the <tp:member-ref>AutomaticPresence</tp:member-ref>.</p>
590
591		<tp:rationale>
592		This corresponds to e.g. GetPresence and GetPresenceMessage
593		in NMC 4.x.
594		</tp:rationale>
595	575
596	576	<p>The <tp:type>Connection_Presence_Type</tp:type> in this property
597	577	MUST NOT be Unset, Unknown or Error.</p>

-4

spec/Account_Interface_Avatar.xml less more

53	53	an empty string to indicate no avatar. When the account becomes
54	54	connected, the account manager SHOULD set this avatar using SetAvatar
55	55	if appropriate.
56
57		<tp:rationale>
58		This corresponds to NMC 4.x mc_account_get_avatar.
59		</tp:rationale>
60	56	</tp:docstring>
61	57	</property>
62	58

+52

-0

spec/Account_Interface_External_Password_Storage.xml less more

	0	<?xml version="1.0" ?>
	1	<node name="/Account_Interface_External_Password_Storage"
	2	xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
	3
	4	<tp:copyright>Copyright © 2011 Collabora Ltd.</tp:copyright>
	5	<tp:license xmlns="http://www.w3.org/1999/xhtml">
	6	<p>This library is free software; you can redistribute it and/or
	7	modify it under the terms of the GNU Lesser General Public
	8	License as published by the Free Software Foundation; either
	9	version 2.1 of the License, or (at your option) any later version.</p>
	10
	11	<p>This library is distributed in the hope that it will be useful,
	12	but WITHOUT ANY WARRANTY; without even the implied warranty of
	13	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
	14	Lesser General Public License for more details.</p>
	15
	16	<p>You should have received a copy of the GNU Lesser General Public
	17	License along with this library; if not, write to the Free Software
	18	Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
	19	02110-1301, USA.</p>
	20	</tp:license>
	21
	22	<interface name="org.freedesktop.Telepathy.Account.Interface.ExternalPasswordStorage.DRAFT"
	23	tp:causes-havoc="experimental">
	24	<tp:added version="0.21.10">(draft 1)</tp:added>
	25	<tp:requires interface="org.freedesktop.Telepathy.Account"/>
	26
	27	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	28	<p>An interface for Accounts whose passwords are stored externally and
	29	SHOULD NOT be stored by either the <tp:dbus-ref
	30	namespace="org.freedesktop.Telepathy">AccountManager</tp:dbus-ref> nor
	31	any <tp:dbus-ref
	32	namespace="org.freedesktop.Telepathy.Channel.Type">ServerAuthentication</tp:dbus-ref>
	33	handler.</p>
	34	</tp:docstring>
	35
	36	<method name="ForgetPassword" tp:name-for-bindings="Forget_Password">
	37	<tp:docstring>
	38	<p>Clears any saved password associated with this account.</p>
	39	</tp:docstring>
	40	</method>
	41
	42	<property name="PasswordSaved"
	43	tp:name-for-bindings="Password_Saved"
	44	type="b" access="read">
	45	<tp:docstring>
	46	<p>Indicates whether the account has a saved password or not.</p>
	47	</tp:docstring>
	48	</property>
	49
	50	</interface>
	51	</node>

+65

-0

spec/Account_Interface_Hidden.xml less more

	0	<?xml version="1.0" ?>
	1	<node name="/Account_Interface_Hidden"
	2	xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
	3
	4	<tp:copyright>Copyright © 2010 Collabora Ltd.</tp:copyright>
	5	<tp:license xmlns="http://www.w3.org/1999/xhtml">
	6	<p>This library is free software; you can redistribute it and/or
	7	modify it under the terms of the GNU Lesser General Public
	8	License as published by the Free Software Foundation; either
	9	version 2.1 of the License, or (at your option) any later version.</p>
	10
	11	<p>This library is distributed in the hope that it will be useful,
	12	but WITHOUT ANY WARRANTY; without even the implied warranty of
	13	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
	14	Lesser General Public License for more details.</p>
	15
	16	<p>You should have received a copy of the GNU Lesser General Public
	17	License along with this library; if not, write to the Free Software
	18	Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
	19	02110-1301, USA.</p>
	20	</tp:license>
	21
	22	<interface name="org.freedesktop.Telepathy.Account.Interface.Hidden.DRAFT1"
	23	tp:causes-havoc="outrageous">
	24	<tp:added version="0.21.10">(draft 1)</tp:added>
	25
	26	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	27	<p>An interface for flagging certain accounts as hidden, so that they do
	28	not appear in the account manager's standard lists of accounts.
	29	Accounts whose <tp:member-ref>Hidden</tp:member-ref> property is
	30	<code>True</code> are intended for non-interactive use (by
	31	non-user-visible services), and appear on the <tp:dbus-ref
	32	namespace='ofdT'>AccountManager.Interface.Hidden.DRAFT1</tp:dbus-ref>
	33	interface; in all other respects, they behave like any other
	34	account.</p>
	35
	36	<tp:rationale>
	37	<p>XMPP, in particular, is increasingly used for purposes other than
	38	instant messaging and VoIP. For instance, extensions exist for
	39	inter-device bookmark synchronization.</p>
	40
	41	<p>While obviously these services could re-use connections intended for
	42	instant messaging, in some cases you might want to use a different
	43	account. (Perhaps your bookmark sync provider is not your IM
	44	provider.) This API allows such auxiliary accounts to exist in
	45	Telepathy, while not being displayed in standard user interfaces for
	46	IM, VoIP, and friends.</p>
	47	</tp:rationale>
	48	</tp:docstring>
	49
	50	<property name="Hidden" tp:name-for-bindings="Hidden"
	51	type="b" access="read" tp:immutable='aye'>
	52	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	53	<p>If <code>True</code>, this account is intended for non-interactive
	54	use, and thus should not be presented to the user. It will not appear
	55	in properties and signals on the main <tp:dbus-ref
	56	namespace='ofdT'>AccountManager</tp:dbus-ref> interface; instead, it
	57	will show up on <tp:dbus-ref
	58	namespace='ofdT'>AccountManager.Interface.Hidden.DRAFT1</tp:dbus-ref>.</p>
	59	</tp:docstring>
	60	</property>
	61
	62	</interface>
	63	</node>
	64	<!-- vim:set sw=2 sts=2 et ft=xml: -->

+100

-0

spec/Account_Manager_Interface_Hidden.xml less more

	0	<?xml version="1.0" ?>
	1	<node name="/Account_Manager_Interface_Hidden"
	2	xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
	3	<tp:copyright>Copyright © 2010 Collabora Ltd.</tp:copyright>
	4	<tp:copyright>Copyright © 2010 Nokia Corporation</tp:copyright>
	5	<tp:license xmlns="http://www.w3.org/1999/xhtml">
	6	<p>This library is free software; you can redistribute it and/or
	7	modify it under the terms of the GNU Lesser General Public
	8	License as published by the Free Software Foundation; either
	9	version 2.1 of the License, or (at your option) any later version.</p>
	10
	11	<p>This library is distributed in the hope that it will be useful,
	12	but WITHOUT ANY WARRANTY; without even the implied warranty of
	13	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
	14	Lesser General Public License for more details.</p>
	15
	16	<p>You should have received a copy of the GNU Lesser General Public
	17	License along with this library; if not, write to the Free Software
	18	Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
	19	</p>
	20	</tp:license>
	21	<interface
	22	name="org.freedesktop.Telepathy.AccountManager.Interface.Hidden.DRAFT1"
	23	tp:causes-havoc='kind of sketchy'>
	24	<tp:requires interface='org.freedesktop.Telepathy.AccountManager'/>
	25	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	26	<p>This interface lists accounts whose <tp:dbus-ref
	27	namespace='ofdT.Account.Interface.Hidden.DRAFT1'>Hidden</tp:dbus-ref>
	28	property is <code>True</code>.</p>
	29	</tp:docstring>
	30	<tp:added version="0.21.10">first draft</tp:added>
	31
	32	<property name="ValidHiddenAccounts" type="ao" access="read"
	33	tp:name-for-bindings="Valid_Hidden_Accounts">
	34	<tp:docstring>
	35	A list of valid (complete, usable) <tp:dbus-ref
	36	namespace="org.freedesktop.Telepathy">Account</tp:dbus-ref>s intended
	37	exclusively for noninteractive applications. These accounts are not
	38	included in <tp:dbus-ref
	39	namespace='ofdT'>AccountManager.ValidAccounts</tp:dbus-ref>. Change
	40	notification is via
	41	<tp:member-ref>HiddenAccountValidityChanged</tp:member-ref>.
	42	</tp:docstring>
	43	</property>
	44
	45	<property name="InvalidHiddenAccounts" type="ao" access="read"
	46	tp:name-for-bindings="Invalid_Hidden_Accounts">
	47	<tp:docstring>
	48	A list of incomplete or otherwise unusable <tp:dbus-ref
	49	namespace="org.freedesktop.Telepathy">Account</tp:dbus-ref>s intended
	50	exclusively for noninteractive applications. Change notification is via
	51	<tp:member-ref>HiddenAccountValidityChanged</tp:member-ref>.
	52	</tp:docstring>
	53	</property>
	54
	55	<signal name="HiddenAccountRemoved"
	56	tp:name-for-bindings="Hidden_Account_Removed">
	57	<tp:docstring>
	58	The given account has been removed from
	59	<tp:member-ref>ValidHiddenAccounts</tp:member-ref> or
	60	<tp:member-ref>InvalidHiddenAccounts</tp:member-ref>.
	61	</tp:docstring>
	62
	63	<arg name="Account" type="o">
	64	<tp:docstring>
	65	An Account, which must not be used any more.
	66	</tp:docstring>
	67	</arg>
	68	</signal>
	69
	70	<signal name="HiddenAccountValidityChanged"
	71	tp:name-for-bindings="Hidden_Account_Validity_Changed">
	72	<tp:docstring>
	73	The validity of the given account has changed. New magic
	74	accounts are also indicated by this signal, as an account validity
	75	change (usually to True) on an account that did not previously exist.
	76
	77	<tp:rationale>
	78	This is effectively change notification for the valid and invalid
	79	accounts lists.
	80	</tp:rationale>
	81	</tp:docstring>
	82
	83	<arg name="Account" type="o">
	84	<tp:docstring>
	85	An <tp:dbus-ref
	86	namespace="org.freedesktop.Telepathy">Account</tp:dbus-ref>.
	87	</tp:docstring>
	88	</arg>
	89
	90	<arg name="Valid" type="b">
	91	<tp:docstring>
	92	True if the account is now valid.
	93	</tp:docstring>
	94	</arg>
	95	</signal>
	96
	97	</interface>
	98	</node>
	99	<!-- vim:set sw=2 sts=2 et ft=xml: -->

-36

spec/Call_Content.xml less more

249	249	<tp:member-ref>StreamsRemoved</tp:member-ref> signals.</p>
250	250	</tp:docstring>
251	251	</property>
252
253		<tp:enum name="Call_Content_Packetization_Type" type="u">
254		<tp:added version="0.21.2"/>
255		<tp:docstring>
256		A packetization method that can be used for a content.
257		</tp:docstring>
258
259		<tp:enumvalue suffix="RTP" value="0">
260		<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
261		Real-time Transport Protocol, as documented by RFC 3550.
262		</tp:docstring>
263		</tp:enumvalue>
264
265		<tp:enumvalue suffix="Raw" value="1">
266		<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
267		Raw media.
268		</tp:docstring>
269		</tp:enumvalue>
270
271		<tp:enumvalue suffix="MSN_Webcam" value="2">
272		<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
273		MSN webcam. This is the video-only one-way type which was
274		used in earlier versions of WLM. Although no longer used,
275		modern WLM clients still support the MSN webcam protocol.
276		</tp:docstring>
277		</tp:enumvalue>
278		</tp:enum>
279
280		<property name="Packetization" tp:name-for-bindings="Packetization"
281		type="u" tp:type="Call_Content_Packetization_Type" access="read"
282		tp:immutable="yes">
283		<tp:added version="0.21.2"/>
284		<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
285		<p>The packetization method in use for this content.</p>
286		</tp:docstring>
287		</property>
288	252	</interface>
289	253	</node>
290	254	<!-- vim:set sw=2 sts=2 et ft=xml: -->

+36

-0

spec/Call_Content_Interface_Media.xml less more

325	325	there is no longer any active codec offer) signals.</p>
326	326	</tp:docstring>
327	327	</property>
	328
	329	<tp:enum name="Call_Content_Packetization_Type" type="u">
	330	<tp:added version="0.21.2"/>
	331	<tp:docstring>
	332	A packetization method that can be used for a content.
	333	</tp:docstring>
	334
	335	<tp:enumvalue suffix="RTP" value="0">
	336	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	337	Real-time Transport Protocol, as documented by RFC 3550.
	338	</tp:docstring>
	339	</tp:enumvalue>
	340
	341	<tp:enumvalue suffix="Raw" value="1">
	342	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	343	Raw media.
	344	</tp:docstring>
	345	</tp:enumvalue>
	346
	347	<tp:enumvalue suffix="MSN_Webcam" value="2">
	348	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	349	MSN webcam. This is the video-only one-way type which was
	350	used in earlier versions of WLM. Although no longer used,
	351	modern WLM clients still support the MSN webcam protocol.
	352	</tp:docstring>
	353	</tp:enumvalue>
	354	</tp:enum>
	355
	356	<property name="Packetization" tp:name-for-bindings="Packetization"
	357	type="u" tp:type="Call_Content_Packetization_Type" access="read"
	358	tp:immutable="yes">
	359	<tp:added version="0.21.2"/>
	360	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	361	<p>The packetization method in use for this content.</p>
	362	</tp:docstring>
	363	</property>
328	364	</interface>
329	365	</node>
330	366	<!-- vim:set sw=2 sts=2 et ft=xml: -->

+137

-0

spec/Call_Content_Interface_Video_Control.xml less more

	0	<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
	1	<node name="/Call_Content_Interface_Video_Control"
	2	xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
	3	<tp:copyright>Copyright © 2009-2010 Collabora Ltd.</tp:copyright>
	4	<tp:copyright>Copyright © 2009-2010 Nokia Corporation</tp:copyright>
	5	<tp:license xmlns="http://www.w3.org/1999/xhtml">
	6	<p>This library is free software; you can redistribute it and/or
	7	modify it under the terms of the GNU Lesser General Public
	8	License as published by the Free Software Foundation; either
	9	version 2.1 of the License, or (at your option) any later version.</p>
	10
	11	<p>This library is distributed in the hope that it will be useful,
	12	but WITHOUT ANY WARRANTY; without even the implied warranty of
	13	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
	14	Lesser General Public License for more details.</p>
	15
	16	<p>You should have received a copy of the GNU Lesser General Public
	17	License along with this library; if not, write to the Free Software
	18	Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
	19	02110-1301, USA.</p>
	20	</tp:license>
	21
	22	<interface name="org.freedesktop.Telepathy.Call.Content.Interface.VideoControl.DRAFT"
	23	tp:causes-havoc="experimental">
	24	<tp:added version="0.21.10">(draft 1)</tp:added>
	25	<tp:requires interface="org.freedesktop.Telepathy.Call.Content.Interface.Media.DRAFT"/>
	26
	27	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	28	<p>An interface that allows the connection manager to control the video
	29	stream.</p>
	30	<p>This interface is generally not needed. In cases where the connection
	31	manager handles the network communication and the media is transferred
	32	from the client to the connection manager via shared memory, it can
	33	sometimes be beneficial for the connection manager to be able to
	34	control certain aspects of the video stream.</p>
	35	</tp:docstring>
	36
	37	<signal name="KeyFrameRequested" tp:name-for-bindings="Key_Frame_Requested">
	38	<tp:docstring>
	39	Request that the video encoder produce a new key frame as soon as
	40	possible.
	41	</tp:docstring>
	42	</signal>
	43
	44	<tp:struct name="Video_Resolution"
	45	array-name="Video_Resolution_Struct">
	46	<tp:member type="u" name="Width">
	47	<tp:docstring>
	48	With of the video stream.
	49	</tp:docstring>
	50	</tp:member>
	51	<tp:member type="u" name="Height">
	52	<tp:docstring>
	53	Height of the video stream.
	54	</tp:docstring>
	55	</tp:member>
	56	</tp:struct>
	57
	58	<property name="VideoResolution" type="(uu)" tp:type="Video_Resolution"
	59	access="read" tp:name-for-bindings="Video_Resolution">
	60	<tp:docstring>
	61	The resolution at which the streaming engine should be sending.
	62
	63	<p>Change notification is via the
	64	<tp:member-ref>VideoResolutionChanged</tp:member-ref> signal.</p>
	65	</tp:docstring>
	66	</property>
	67
	68	<signal name="VideoResolutionChanged"
	69	tp:name-for-bindings="Video_Resolution_Changed">
	70	<tp:docstring>
	71	The desired video resolution has changed.
	72	</tp:docstring>
	73	<arg type="(uu)" tp:type="Video_Resolution" name="NewResolution" />
	74	</signal>
	75
	76	<property name="Bitrate" type="u" access="read"
	77	tp:name-for-bindings="Bitrate">
	78	<tp:docstring>
	79	The bitrate the streaming engine should be sending at.
	80
	81	<p>Change notification is via the
	82	<tp:member-ref>BitrateChanged</tp:member-ref> signal.</p>
	83	</tp:docstring>
	84	</property>
	85
	86	<signal name="BitrateChanged"
	87	tp:name-for-bindings="Bitrate_Changed">
	88	<tp:docstring>
	89	The desired bitrate has changed
	90	</tp:docstring>
	91	<arg type="u" name="NewBitrate" />
	92	</signal>
	93
	94	<property name="Framerate" type="u" access="read"
	95	tp:name-for-bindings="Framerate">
	96	<tp:docstring>
	97	The framerate the streaming engine should be sending at.
	98
	99	<p>Change notification is via the
	100	<tp:member-ref>FramerateChanged</tp:member-ref> signal.</p>
	101	</tp:docstring>
	102	</property>
	103
	104	<signal name="FramerateChanged"
	105	tp:name-for-bindings="Framerate_Changed">
	106	<tp:docstring>
	107	The desired framerate has changed
	108	</tp:docstring>
	109	<arg type="u" name="NewFramerate" />
	110	</signal>
	111
	112	<property name="MTU" type="u" access="read"
	113	tp:name-for-bindings="MTU">
	114	<tp:docstring>
	115	The Maximum Transmission Unit
	116
	117	<p>Change notification is via the
	118	<tp:member-ref>MTUChanged</tp:member-ref> signal.</p>
	119	</tp:docstring>
	120	</property>
	121
	122	<signal name="MTUChanged" tp:name-for-bindings="MTU_Changed">
	123	<tp:docstring>
	124	The Maximum Transmission Unit has changed
	125	</tp:docstring>
	126	<arg type="u" name="NewMTU" />
	127	</signal>
	128
	129	<property name="ManualKeyFrames" type="b" access="read"
	130	tp:name-for-bindings="Manual_Key_Frames">
	131	<tp:docstring>
	132	Only send key frames when manually requested
	133	</tp:docstring>
	134	</property>
	135	</interface>
	136	</node>

-5

spec/Call_Stream_Endpoint.xml less more

71	71	</signal>
72	72
73	73	<property name="RemoteCandidates" tp:name-for-bindings="Remote_Candidates"
74		type="a(usqa{sv})" tp:type="Candidate[]" access="read">
	74	type="a(usua{sv})" tp:type="Candidate[]" access="read">
75	75	<tp:docstring>
76	76	A list of candidates for this endpoint.
77	77	</tp:docstring>

84	84	<tp:member-ref>RemoteCandidates</tp:member-ref> property.
85	85	</tp:docstring>
86	86	<arg name="Candidates"
87		type="a(usqa{sv})" tp:type="Candidate[]">
	87	type="a(usua{sv})" tp:type="Candidate[]">
88	88	<tp:docstring>
89	89	The candidates that were added.
90	90	</tp:docstring>

97	97	Emitted when a candidate is selected for use in the stream.
98	98	</tp:docstring>
99	99	<arg name="Candidate"
100		type="(usqa{sv})" tp:type="Candidate">
	100	type="(usua{sv})" tp:type="Candidate">
101	101	<tp:docstring>
102	102	The candidate that has been selected.
103	103	</tp:docstring>

106	106
107	107	<property name="SelectedCandidate"
108	108	tp:name-for-bindings="Selected_Candidate"
109		type="(usqa{sv})" tp:type="Candidate" access="read">
	109	type="(usua{sv})" tp:type="Candidate" access="read">
110	110	<tp:docstring>
111	111	The candidate that has been selected for use to stream packets
112	112	to the remote contact. Change notification is given via the

121	121	<tp:member-ref>CandidateSelected</tp:member-ref>.
122	122	</tp:docstring>
123	123	<arg name="Candidate"
124		type="(usqa{sv})" tp:type="Candidate" direction="in">
	124	type="(usua{sv})" tp:type="Candidate" direction="in">
125	125	<tp:docstring>
126	126	The candidate that has been selected.
127	127	</tp:docstring>

+31

-5

spec/Call_Stream_Interface_Media.xml less more

109	109	</tp:member>
110	110	</tp:mapping>
111	111
	112	<tp:enum type="u" name="Stream_Component">
	113	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	114	Media streams can use more than one UDP socket: one for RTP (data)
	115	and one for RTCP (control). Most of the time, they are adjacent
	116	to each other, but some protocols (xmpp) signal each port separately.
	117	</tp:docstring>
	118	<tp:enumvalue suffix="Unknown" value="0">
	119	<tp:docstring>
	120	The stream transport type is unknown or not applicable
	121	(should not appear over dbus).
	122	</tp:docstring>
	123	</tp:enumvalue>
	124	<tp:enumvalue suffix="Data" value="1">
	125	<tp:docstring>
	126	This is the high-traffic data socket, containing the audio/video
	127	data for the stream.
	128	</tp:docstring>
	129	</tp:enumvalue>
	130	<tp:enumvalue suffix="Control" value="2">
	131	<tp:docstring>
	132	This is the low-traffic control socket, usually containing feedback
	133	about packet loss etc.
	134	</tp:docstring>
	135	</tp:enumvalue>
	136	</tp:enum>
	137
112	138	<tp:struct name="Candidate" array-name="Candidate_List">
113	139	<tp:docstring>A Stream Candidate.</tp:docstring>
114		<tp:member name="Component" type="u">
	140	<tp:member name="Component" type="u" tp:type="Stream_Component">
115	141	<tp:docstring>The component number.</tp:docstring>
116	142	</tp:member>
117	143	<tp:member name="IP" type="s">
118	144	<tp:docstring>The IP address to use.</tp:docstring>
119	145	</tp:member>
120		<tp:member name="Port" type="q">
	146	<tp:member name="Port" type="u">
121	147	<tp:docstring>The port number to use.</tp:docstring>
122	148	</tp:member>
123	149	<tp:member name="Info" type="a{sv}" tp:type="Candidate_Info">

132	158	signal them to the remote contact(s).
133	159	</tp:docstring>
134	160	<arg name="Candidates" direction="in"
135		type="a(usqa{sv})" tp:type="Candidate[]">
	161	type="a(usua{sv})" tp:type="Candidate[]">
136	162	<tp:docstring>
137	163	The candidates to be added.
138	164	</tp:docstring>

215	241	</property>
216	242
217	243	<property name="LocalCandidates" tp:name-for-bindings="Local_Candidates"
218		type="a(usqa{sv})" tp:type="Candidate[]" access="read">
	244	type="a(usua{sv})" tp:type="Candidate[]" access="read">
219	245	<tp:docstring>
220	246	[FIXME]. Change notification is via the
221	247	<tp:member-ref>LocalCandidatesAdded</tp:member-ref> signal.

228	254	Emitted when local candidates are added to the
229	255	<tp:member-ref>LocalCandidates</tp:member-ref> property.
230	256	</tp:docstring>
231		<arg name="Candidates" type="a(usqa{sv})" tp:type="Candidate[]">
	257	<arg name="Candidates" type="a(usua{sv})" tp:type="Candidate[]">
232	258	<tp:docstring>
233	259	Candidates that have been added.
234	260	</tp:docstring>

+59

-0

spec/Channel_Interface_Credentials_Storage.xml less more

	0	<?xml version="1.0" ?>
	1	<node name="/Channel_Interface_Credentials_Storage"
	2	xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
	3	<tp:copyright> Copyright © 2011 Collabora Limited </tp:copyright>
	4	<tp:license xmlns="http://www.w3.org/1999/xhtml">
	5	<p>This library is free software; you can redistribute it and/or
	6	modify it under the terms of the GNU Lesser General Public
	7	License as published by the Free Software Foundation; either
	8	version 2.1 of the License, or (at your option) any later version.</p>
	9
	10	<p>This library is distributed in the hope that it will be useful,
	11	but WITHOUT ANY WARRANTY; without even the implied warranty of
	12	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
	13	Lesser General Public License for more details.</p>
	14
	15	<p>You should have received a copy of the GNU Lesser General Public
	16	License along with this library; if not, write to the Free Software
	17	Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</p>
	18	</tp:license>
	19	<interface name="org.freedesktop.Telepathy.Channel.Interface.CredentialsStorage.DRAFT"
	20	tp:causes-havoc="experimental">
	21	<tp:added version="0.21.10">(draft 1)</tp:added>
	22	<tp:requires interface="org.freedesktop.Telepathy.Channel.Interface.SASLAuthentication"/>
	23	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	24	<p>A channel interface for SASL authentication channels that can save the
	25	credentials in the connection manager.</p>
	26
	27	<p>This interface is unlikely to be present for any SASL channels that are
	28	more complex than a simple password prompt (e.g.
	29	<code>X-TELEPATHY-PASSWORD</code> or <code>PLAIN</code>).</p>
	30
	31	<p>In practice, this interface should only be implemented by connection
	32	managers that implement the <tp:dbus-ref
	33	namespace="ofdT">ConnectionManager.Interface.AccountStorage.DRAFT</tp:dbus-ref>
	34	interface. To clear a password that has been saved in this manner, a
	35	client should call <tp:dbus-ref
	36	namespace="ofdT.ConnectionManager.Interface">AccountStorage.DRAFT.ForgetCredentials</tp:dbus-ref>
	37	on the Account.</p>
	38	</tp:docstring>
	39
	40	<method name="StoreCredentials" tp:name-for-bindings="Store_Credentials">
	41	<arg direction="in" name="Store" type="b">
	42	<tp:docstring>
	43	Whether to store the authentication credentials.
	44	</tp:docstring>
	45	</arg>
	46	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	47	<p>This method tells the connection manager whether to store the
	48	authentication response in order to allow the connection manager to
	49	sign-on automatically in the future.</p>
	50	<p>If credentials have been stored in this way, the client SHOULD NOT
	51	attempt to store the credentials locally in a keyring.</p>
	52	<p>This method MUST be called before <tp:dbus-ref
	53	namespace="org.freedesktop.Telepathy.Channel.Interface.SASLAuthentication">AcceptSASL</tp:dbus-ref>
	54	is called or it will have no effect.</p>
	55	</tp:docstring>
	56	</method>
	57	</interface>
	58	</node>

+19

-0

spec/Channel_Interface_SASL_Authentication.xml less more

365	365	</tp:rationale>
366	366	</tp:docstring>
367	367	</property>
	368
	369	<property name="MaySaveResponse" tp:name-for-bindings="May_Save_Response"
	370	type="b" access="read" tp:immutable="yes">
	371	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	372	<p>Whether or not the client can save the authentication response and
	373	re-use it to automate future authentication challenges.</p>
	374
	375	<p>If this property is <code>False</code>, the client SHOULD NOT attempt
	376	to cache the authentication response in its own keyring.</p>
	377
	378	<p>If this property is not specified, it should be treated as if it were
	379	<code>True</code>.</p>
	380
	381	<tp:rationale>Some protocols or services may have terms and conditions
	382	that prohibit caching a user's credentials.</tp:rationale>
	383
	384	</tp:docstring>
	385	</property>
	386
368	387
369	388	<method name="StartMechanism" tp:name-for-bindings="Start_Mechanism">
370	389	<arg direction="in" name="Mechanism" type="s" tp:type="SASL_Mechanism">

-5

spec/Channel_Request.xml less more

1	1	<node name="/Channel_Request"
2	2	xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
3	3
4		<tp:copyright>Copyright © 2008-2009 Collabora Ltd.</tp:copyright>
5		<tp:copyright>Copyright © 2008-2009 Nokia Corporation</tp:copyright>
	4	<tp:copyright>Copyright © 2008–2011 Collabora Ltd.</tp:copyright>
	5	<tp:copyright>Copyright © 2008–2009 Nokia Corporation</tp:copyright>
6	6	<tp:license xmlns="http://www.w3.org/1999/xhtml">
7	7	<p>This library is free software; you can redistribute it and/or
8	8	modify it under the terms of the GNU Lesser General Public

24	24	<tp:added version="0.17.26">(as a stable interface)</tp:added>
25	25
26	26	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
27		<p>A channel request is an object in the ChannelDispatcher representing
28		an ongoing request for some channels to be created or found. There
	27	<p>A channel request is an object in the <tp:dbus-ref
	28	namespace='ofdT'>ChannelDispatcher</tp:dbus-ref> representing
	29	an ongoing request for some channels to be created or found. They are
	30	created by methods such as <tp:dbus-ref
	31	namespace='ofdT.ChannelDispatcher'>CreateChannel</tp:dbus-ref>. There
29	32	can be any number of ChannelRequest objects at the same time.</p>
30	33
31	34	<p>Its well-known bus name is the same as that of the ChannelDispatcher,
32		"org.freedesktop.Telepathy.ChannelDispatcher".</p>
	35	<code>"org.freedesktop.Telepathy.ChannelDispatcher"</code>.</p>
33	36
34	37	<tp:rationale>
35	38	<p>See

-7

spec/Channel_Type_Call.xml less more

31	31	<p>Handlers are advised against executing all the media
32	32	signalling, codec and candidate negotiation themselves but
33	33	instead use a helper library such as <a
34		href="http://telepathy.freedesktop.org/doc/telepathy-farsight/">telepathy-farsight</a>
	34	href="http://telepathy.freedesktop.org/doc/telepathy-farstream/">telepathy-farstream</a>
35	35	which when given a new Call channel will set up the
36	36	transports and codecs and create GStreamer pads which
37	37	can be added to the handler UI. This is useful as it means

116	116	<tp:type>Call_State</tp:type>_Accepted.</p>
117	117
118	118	<p>At this point <a
119		href="http://telepathy.freedesktop.org/doc/telepathy-farsight/">telepathy-farsight</a>
	119	href="http://telepathy.freedesktop.org/doc/telepathy-farstream/">telepathy-farstream</a>
120	120	will signal that a pad is available for the handler to show
121	121	in the user interface.</p>
122	122

182	182	<p>Once the handler has notified the local user that there is an
183	183	incoming call waiting for acceptance, the handler should call
184	184	<tp:member-ref>SetRinging</tp:member-ref> to let the CM know.
185		The new channel should also be given to telepathy-farsight to
	185	The new channel should also be given to telepathy-farstream to
186	186	work out how the two participants will connect together.
187		telepathy-farsight will call the appropriate methods on the call's
	187	telepathy-farstream will call the appropriate methods on the call's
188	188	<tp:dbus-ref namespace="ofdT.Call">Content.DRAFT</tp:dbus-ref>s
189	189	to negotiate codecs and transports.</p>
190	190

192	192	<tp:member-ref>Accept</tp:member-ref>. The
193	193	<tp:member-ref>CallState</tp:member-ref> property changes to
194	194	<tp:type>Call_State</tp:type>_Accepted and once media is
195		being transferred, telepathy-farsight will notify the
	195	being transferred, telepathy-farstream will notify the
196	196	handler of a new pad to be shown to the local user in the
197	197	UI</p>
198	198

224	224	</blockquote>
225	225
226	226	<p>Assuming no errors, the new video content will be added to
227		the call. telepathy-farsight will pick up the new content and
	227	the call. telepathy-farstream will pick up the new content and
228	228	perform the transport and codec negotiation automatically.
229		telpathy-farsight will signal when the video is ready to
	229	telpathy-farstream will signal when the video is ready to
230	230	show in the handler's user interface.</p>
231	231
232	232	<p>A similar method is used for removing contents from a call,

+49

-0

spec/Channel_Type_File_Transfer.xml less more

256	256
257	257	<p>This property MUST NOT change after the state of the transfer has
258	258	changed to Open.</p>
	259	</tp:docstring>
	260	</property>
	261
	262	<property name="URI" type="s" access="readwrite"
	263	tp:name-for-bindings="URI" tp:immutable="sometimes" tp:requestable="yes">
	264	<tp:added version="0.21.9"/>
	265	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	266	<p>For outgoing file transfers, this requestable property allows the channel
	267	requester to inform observers (and the handler, if it is not the requester
	268	itself) of the URI of the file being transferred. Note that the
	269	connection manager SHOULD NOT read this file directly; the handler
	270	streams the file into the CM through the socket negotiated using
	271	<tp:member-ref>ProvideFile</tp:member-ref>.</p>
	272
	273	<p>On outgoing file transfers, this property MUST NOT change after the channel
	274	is requested.</p>
	275
	276	<p>For incoming file transfers, this property MAY be set by the channel
	277	handler before calling <tp:member-ref>AcceptFile</tp:member-ref> to
	278	inform observers where the incoming file will be saved.
	279	Setting this property once <tp:member-ref>AcceptFile</tp:member-ref>
	280	has been called MUST fail. Once this property has been set
	281	<tp:member-ref>URIDefined</tp:member-ref> is emitted.</p>
	282
	283	<p>If set, this URI SHOULD generally point to a file on the local system, as
	284	defined by <a href='http://www.apps.ietf.org/rfc/rfc1738.html#sec-3.10'>
	285	RFC 1738 §3.10</a>; that is, it should be of the form
	286	<tt>file:///path/to/file</tt> or <tt>file://localhost/path/to/file</tt>.
	287	For outgoing files, this URI MAY use a different scheme, such as
	288	<tt>http:</tt>, if a remote resource is being transferred
	289	to a contact.</p>
	290
259	291	</tp:docstring>
260	292	</property>
261	293

524	556	</arg>
525	557	</signal>
526	558
	559	<signal name="URIDefined"
	560	tp:name-for-bindings="URI_Defined">
	561	<tp:added version="0.21.9"/>
	562	<tp:docstring>
	563	Emitted when the value of the <tp:member-ref>URI</tp:member-ref>
	564	property has been set. This signal MUST only be emitted on
	565	incoming file transfers, and only if the handler sets the
	566	<tp:member-ref>URI</tp:member-ref> property before
	567	accepting the file.
	568	</tp:docstring>
	569	<arg name="URI" type="s">
	570	<tp:docstring>
	571	The value of the <tp:member-ref>URI</tp:member-ref> property.
	572	</tp:docstring>
	573	</arg>
	574	</signal>
	575
527	576	</interface>
528	577
529	578	</node>

-0

spec/Client_Approver.xml less more

76	76	<p>Approvers should usually prompt the user and ask for
77	77	confirmation, rather than dispatching the channel to a handler
78	78	straight away.</p>
	79
	80	<p>Non-interactive approvers can also be implemented as
	81	<tp:dbus-ref namespace="ofdT.Client">Observer</tp:dbus-ref>s as
	82	described in the interface description.</p>
79	83	</tp:docstring>
80	84
81	85	<property name="ApproverChannelFilter"

+68

-0

spec/Client_Observer.xml less more

85	85	destructive happen. Destructive things (e.g. acknowledging messages)
86	86	are defined to be done by handlers, therefore HandleWith and Claim
87	87	aren't allowed to succeed until all observers are ready.</p>
	88
	89	<p>Non-interactive approvers (for instance, to shoot down spam
	90	IM channels before the tray icon blinks at the user, or to grab
	91	a SASL channel before the user is prompted for a password) can
	92	be implemented as observers by following these steps:</p>
	93
	94	<ol>
	95	<li><tp:member-ref>ObserveChannels</tp:member-ref>() is called
	96	on the observer.</li>
	97	<li>The observer calls <tp:dbus-ref
	98	namespace="ofdT.ChannelDispatchOperation">Claim</tp:dbus-ref>()
	99	on the CDO.</li>
	100	<li>The observer then returns from
	101	<tp:member-ref>ObserveChannels</tp:member-ref>().</li>
	102	<li><tp:dbus-ref
	103	namespace="ofdT.ChannelDispatchOperation">Claim</tp:dbus-ref>
	104	will return successfully if the channels were successfully
	105	claimed, or failure if someone else got there first.</li>
	106	</ol>
	107
	108	<p>Non-interactive approvers implemented as observers SHOULD
	109	also set <tp:member-ref>DelayApprovers</tp:member-ref> to TRUE
	110	so that other Approvers are not called on until all observers
	111	return from <tp:member-ref>ObserveChannels</tp:member-ref>.
	112	This gives non-interactive approvers a chance to claim the
	113	channels before Approvers are called.</p>
88	114	</tp:docstring>
89	115
90	116	<property name="ObserverChannelFilter"

373	399
374	400	</method>
375	401
	402	<property name="DelayApprovers" type="b" access="read"
	403	tp:name-for-bindings="Delay_Approvers">
	404	<tp:added version="0.21.11"/>
	405	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	406	<p>If true, the channel dispatcher will wait for
	407	<tp:member-ref>ObserveChannels</tp:member-ref> to return
	408	before calling <tp:dbus-ref
	409	namespace="ofdT.Client">Approver.AddDispatchOperation</tp:dbus-ref>
	410	on appropriate Approvers.</p>
	411
	412	<p>This property SHOULD be false unless there is a reason
	413	why a channel should not be given to approvers. An example
	414	of this is if an Observer is also a Handler and wants to
	415	<tp:dbus-ref
	416	namespace="ofdT.ChannelDispatchOperation">Claim</tp:dbus-ref>
	417	a channel so that it becomes its handler and doesn't want
	418	any approver to be called, this property should be true.</p>
	419
	420	<p>Observers and Approvers should be called at the same time
	421	in normal operation (with this property set to false) to
	422	improve responsiveness. For example, if an incoming call
	423	appears, the approver should get the channel as fast as
	424	possible to show a dialog, but if an approver has to make
	425	round-trips to set itself up, then the approval of the
	426	channel is delayed. As a result, it is recommended for this
	427	property to remain false unless absolutely necessary.</p>
	428
	429	<p>For service-activatable clients, this property should be
	430	specified in the observer's <tt>.client</tt> file as
	431	follows:</p>
	432
	433	<p>If this property is not implemented (telepathy-mission-control
	434	5.7.5 and older), the channel dispatcher SHOULD consider it as
	435	being false.</p>
	436
	437	<pre>
	438	[org.freedesktop.Telepathy.Client.Observer]
	439	DelayApprovers=true
	440	</pre>
	441	</tp:docstring>
	442	</property>
	443
376	444	</interface>
377	445	</node>
378	446	<!-- vim:set sw=2 sts=2 et ft=xml: -->

+11

-6

spec/Connection_Manager.xml less more

44	44	a library on which they are based.</p>
45	45
46	46	<tp:rationale>
47		<p>We often abbreviate, for instance, telepathy-haze as "Haze",
48		but abbreviating telepathy-sofiasip to "Sofia-SIP" would cause
49		confusion between the connection manager and the library it
	47	<p>We often abbreviate, for instance, <i>telepathy-haze</i> as
	48	“Haze”, but abbreviating <i>telepathy-sofiasip</i>—since renamed to
	49	<i>telepathy-rakia</i> for exactly this reason—to “Sofia-SIP”
	50	caused confusion between the connection manager and the library it
50	51	uses. Please don't repeat that mistake.</p>
51	52	</tp:rationale>
52	53	</tp:docstring>

155	156	and possibly changed on an existing Connection using methods on the
156	157	<code>org.freedesktop.DBus.Properties</code> interface.</p>
157	158
158		<p>When a parameter with this flag is changed with <tp:dbus-ref
159		namespace="ofdT">Account.UpdateParameters</tp:dbus-ref>, the
160		account manager will attempt to update its value on any running
	159	<p>When a new value for a parameter with this flag is passed to
	160	<tp:dbus-ref namespace="ofdT">Account.UpdateParameters</tp:dbus-ref>,
	161	the account manager will attempt to update its value on any running
	162	connections. Similarly, if the parameter also has the
	163	<code>Has_Default</code> flag, and is passed in the second argument
	164	to <code>UpdateParameters</code>, the default value will be applied
	165	to any running
161	166	connections. Thus, clients generally do not need to directly access
162	167	or update the connection property; instead, they SHOULD manipulate
163	168	<tp:dbus-ref namespace="ofdT">Account.Parameters</tp:dbus-ref>.</p>

+117

-0

spec/Connection_Manager_Interface_Account_Storage.xml less more

	0	<?xml version="1.0" ?>
	1	<node name="/Connection_Manager_Interface_Account_Storage"
	2	xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
	3
	4	<tp:copyright>Copyright © 2011 Collabora Ltd.</tp:copyright>
	5	<tp:license xmlns="http://www.w3.org/1999/xhtml">
	6	<p>This library is free software; you can redistribute it and/or
	7	modify it under the terms of the GNU Lesser General Public
	8	License as published by the Free Software Foundation; either
	9	version 2.1 of the License, or (at your option) any later version.</p>
	10
	11	<p>This library is distributed in the hope that it will be useful,
	12	but WITHOUT ANY WARRANTY; without even the implied warranty of
	13	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
	14	Lesser General Public License for more details.</p>
	15
	16	<p>You should have received a copy of the GNU Lesser General Public
	17	License along with this library; if not, write to the Free Software
	18	Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
	19	02110-1301, USA.</p>
	20	</tp:license>
	21
	22	<interface name="org.freedesktop.Telepathy.ConnectionManager.Interface.AccountStorage.DRAFT"
	23	tp:causes-havoc="experimental">
	24	<tp:added version="0.21.10">(draft 1)</tp:added>
	25	<tp:requires interface="org.freedesktop.Telepathy.ConnectionManager"/>
	26
	27	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	28	<p>An interface for connection managers that store account details
	29	internally. At the moment this consists only of storing an account's
	30	credentials, but other functionality may be added in the future.</p>
	31	<p><tp:dbus-ref
	32	namespace="org.freedesktop.Telepathy">Account</tp:dbus-ref> objects
	33	representing accounts on a connection manager that implements this
	34	interface should implement the <tp:dbus-ref
	35	namespace="org.freedesktop.Telepathy.Account.Interface">ExternalPasswordStorage.DRAFT</tp:dbus-ref>
	36	interface.</p>
	37
	38	</tp:docstring>
	39
	40	<tp:flags name="Account_Flags" value-prefix="Account_Flag" type="u">
	41	<tp:docstring>
	42	A set of flags representing the status of the Account stored in the Connection Manager.
	43	</tp:docstring>
	44
	45	<tp:flag suffix="Credentials_Stored" value="1">
	46	<tp:docstring>
	47	The associated account has its authentication credentials (password)
	48	stored in the connection manager
	49	</tp:docstring>
	50	</tp:flag>
	51	</tp:flags>
	52
	53	<tp:mapping name="Account_Flags_Map" array-name="Account_Flags_Map_List">
	54	<tp:docstring>A mapping from Account_Ids to account flags.
	55	</tp:docstring>
	56	<tp:member type="s" name="Account_Id"/>
	57	<tp:member type="u" tp:type="Account_Flags" name="Flags"/>
	58	</tp:mapping>
	59
	60	<property name="Accounts"
	61	tp:name-for-bindings="Accounts"
	62	type="a{su}" tp:type="Account_Flags_Map" access="read">
	63	<tp:docstring>
	64	The set of Accounts stored in this connection manager, and flags
	65	indicating their status.
	66	</tp:docstring>
	67	</property>
	68
	69	<method name="ForgetCredentials" tp:name-for-bindings="Forget_Credentials">
	70	<tp:docstring>
	71	Clears any saved credentials associated with the specified Account_Id.
	72	Any other saved data related to the account will be unaffected.
	73	</tp:docstring>
	74
	75	<arg direction="in" name="Account_Id"
	76	type="s">
	77	<tp:docstring>
	78	An account id as returned from <tp:dbus-ref
	79	namespace="org.freedesktop.Telepathy">Protocol.IdentifyAccount</tp:dbus-ref>.
	80	</tp:docstring>
	81	</arg>
	82
	83	<tp:possible-errors>
	84	<tp:error name="org.freedesktop.Telepathy.Error.InvalidArgument">
	85	<tp:docstring>
	86	The account id is invalid.
	87	</tp:docstring>
	88	</tp:error>
	89	</tp:possible-errors>
	90	</method>
	91
	92	<method name="RemoveAccount" tp:name-for-bindings="Remove_Account">
	93	<tp:docstring>
	94	Completely removes all data associated with an account from the
	95	connection manager's internal storage.
	96	</tp:docstring>
	97
	98	<arg direction="in" name="Account_Id"
	99	type="s">
	100	<tp:docstring>
	101	An account id as returned from <tp:dbus-ref
	102	namespace="org.freedesktop.Telepathy">Protocol.IdentifyAccount</tp:dbus-ref>.
	103	</tp:docstring>
	104	</arg>
	105
	106	<tp:possible-errors>
	107	<tp:error name="org.freedesktop.Telepathy.Error.InvalidArgument">
	108	<tp:docstring>
	109	The account id is invalid.
	110	</tp:docstring>
	111	</tp:error>
	112	</tp:possible-errors>
	113	</method>
	114
	115	</interface>
	116	</node>

+11

-4

spec/all.xml less more

2	2	xmlns:xi="http://www.w3.org/2001/XInclude">
3	3
4	4	<tp:title>Telepathy D-Bus Interface Specification</tp:title>
5		<tp:version>0.21.8</tp:version>
	5	<tp:version>0.21.11</tp:version>
6	6
7	7	<tp:copyright>Copyright © 2005-2010 Collabora Limited</tp:copyright>
8	8	<tp:copyright>Copyright © 2005-2010 Nokia Corporation</tp:copyright>

31	31	</p>
32	32	</tp:docstring>
33	33	<xi:include href="Connection_Manager.xml"/>
	34	<xi:include href="Connection_Manager_Interface_Account_Storage.xml"/>
34	35	<xi:include href="Protocol.xml"/>
35	36	<xi:include href="Protocol_Interface_Addressing.xml"/>
36	37	<xi:include href="Protocol_Interface_Avatars.xml"/>

162	163	<xi:include href="Channel_Interface_Password.xml"/>
163	164	<xi:include href="Channel_Interface_Room.xml"/>
164	165	<xi:include href="Channel_Interface_SASL_Authentication.xml"/>
	166	<xi:include href="Channel_Interface_Credentials_Storage.xml"/>
165	167	<xi:include href="Channel_Interface_Securable.xml"/>
166	168	<xi:include href="Channel_Interface_Service_Point.xml"/>
167	169	<xi:include href="Channel_Interface_Tube.xml"/>

178	180	<xi:include href="Channel_Interface_SMS.xml"/>
179	181	</tp:section>
180	182
181		<tp:section name="Streamed Media-related interfaces">
	183	<tp:section name="Streamed Media/Call-related interfaces">
182	184	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
183	185	<p>These interfaces are only applicable to channels of type <tp:dbus-ref
184	186	namespace='ofdT.Channel.Type'>StreamedMedia</tp:dbus-ref>, with the
185	187	exception of the <tp:dbus-ref
186		namespace='ofdT.Channel.Interface'>Hold</tp:dbus-ref> interface, which
187		may also appear on <tp:dbus-ref
	188	namespace='ofdT.Channel.Interface'>Hold</tp:dbus-ref> and
	189	<tp:dbus-ref namespace="ofdT.Channel.Interface">DTMF</tp:dbus-ref>
	190	interfaces, which may also appear on <tp:dbus-ref
188	191	namespace='ofdT.Channel.Type'>Call.DRAFT</tp:dbus-ref> channels.</p>
189	192	</tp:docstring>
190	193

231	234	<xi:include href="Call_Content.xml"/>
232	235	<xi:include href="Call_Content_Interface_Media.xml"/>
233	236	<xi:include href="Call_Content_Interface_Mute.xml"/>
	237	<xi:include href="Call_Content_Interface_Video_Control.xml"/>
234	238	<xi:include href="Call_Content_Codec_Offer.xml"/>
235	239	<xi:include href="Call_Stream.xml"/>
236	240	<xi:include href="Call_Stream_Interface_Media.xml"/>

252	256	</p>
253	257	</tp:docstring>
254	258	<xi:include href="Account_Manager.xml"/>
	259	<xi:include href="Account_Manager_Interface_Hidden.xml"/>
255	260	<xi:include href="Account.xml"/>
256	261	<xi:include href="Account_Interface_Addressing.xml"/>
257	262	<xi:include href="Account_Interface_Avatar.xml"/>
	263	<xi:include href="Account_Interface_Hidden.xml"/>
258	264	<xi:include href="Account_Interface_Storage.xml"/>
	265	<xi:include href="Account_Interface_External_Password_Storage.xml"/>
259	266	</tp:section>
260	267
261	268	<tp:section name="The Channel Dispatcher">