Commit 9aa4b6d75289a24ff3e968be9d42d15f3d54cced - telepathy-spec

Merge commit 'upstream/0.23.1' into debian Sjoerd Simons 12 years ago

28 changed file(s) with 1875 addition(s) and 530 deletion(s). Raw diff Collapse all Expand all

+732

-0

ChangeLog less more

	0	commit f5c94a44de0013990ad6754b92ead72882efdefa
	1	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	2	Date: Mon May 9 14:58:42 2011 +0200
	3
	4	prepare 0.23.1
	5
	6	commit 13214250f1ca26b36b8ec4201722b38588ffe159
	7	Merge: 6aaa96b 02374d4
	8	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	9	Date: Mon May 9 14:50:02 2011 +0200
	10
	11	Merge branch 'telepathy-spec-0.22'
	12
	13	commit 02374d4198712ac87943ccb32f4a76c169582085
	14	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	15	Date: Mon May 9 14:47:20 2011 +0200
	16
	17	bump
	18
	19	commit 405a6f0eb89f897545e086a046d81818f43587c2
	20	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	21	Date: Mon May 9 14:37:42 2011 +0200
	22
	23	prepare 0.22.3
	24
	25	commit 6aaa96bd87d9fa3ff7afee5579e3f09126d5e826
	26	Merge: 2a1bb2b 2d281a4
	27	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	28	Date: Mon May 9 14:27:39 2011 +0200
	29
	30	Merge branch 're-handle-25293'
	31
	32	commit 2d281a43201341b23de97e659c1a3349dcd12efa
	33	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	34	Date: Mon May 9 14:19:11 2011 +0200
	35
	36	Use the <var> markup when referring to arguments.
	37
	38	commit 2a1bb2bdefa3fc7dce3dda3453e19fd1fb545e47
	39	Merge: c517249 5f3afbf
	40	Author: Will Thompson <will.thompson@collabora.co.uk>
	41	Date: Mon May 9 13:11:48 2011 +0100
	42
	43	Merge branch 'telepathy-spec-0.22'
	44
	45	commit 5f3afbf819fa7f65958412da6a14ca0d103edab6
	46	Author: Will Thompson <will.thompson@collabora.co.uk>
	47	Date: Mon May 9 13:09:14 2011 +0100
	48
	49	Correct DBus_Property-parameter boilerplate.
	50
	51	Simon pointed out that the boilerplate claimed that the name of the
	52	parameter should be just the interface name, rather than the
	53	fully-qualified name of the property.
	54
	55	Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=37005>
	56	Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
	57
	58	commit d3ee1440c30e4b74d76a4423684fadc1d848f586
	59	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	60	Date: Wed Mar 23 12:08:02 2011 +0100
	61
	62	add ChannelDispatcher.PresentChannel()
	63
	64	commit 4248d7ef3e805523ba20a06f0cdd839f58ae0489
	65	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	66	Date: Wed Mar 23 12:06:52 2011 +0100
	67
	68	add ChannelDispatcher.DelegateChannels() (fdo #25293)
	69
	70	commit c517249741c68a55e159eae8472728dc77104f2a
	71	Author: Jonny Lamb <jonny.lamb@collabora.co.uk>
	72	Date: Wed Apr 27 15:36:25 2011 +0100
	73
	74	location: use unsigned type for enum values
	75
	76	This enum isn't even in use, it was just annoying me.
	77
	78	Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
	79
	80	commit ff4416f67e9392dd4d4a0ae28702f6e67840919e
	81	Merge: 0b9a36b c006fd4
	82	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	83	Date: Wed Apr 27 09:48:26 2011 +1000
	84
	85	Merge branch 'get-sms-length-36011'
	86
	87	commit c006fd45267864d308a6c06528810ff8e2b2fb1f
	88	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	89	Date: Thu Apr 21 09:26:29 2011 +1000
	90
	91	Update Remaining_Characters to handle truncation
	92
	93	commit 488310dae6ccb003f2ef88128bcab3c555d8491d
	94	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	95	Date: Thu Apr 21 09:16:19 2011 +1000
	96
	97	Change the content to a Message_Part[]
	98
	99	This allows us to get length estimates and costings for rich messages, such as
	100	vCards.
	101
	102	commit 20f3fa2b4fb42c63724c2be43e6a2e214e97cb89
	103	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	104	Date: Thu Apr 21 09:12:09 2011 +1000
	105
	106	Add missing comma
	107
	108	commit 838b2c1c8f406f7b306cad35b253f44ba6da775c
	109	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	110	Date: Thu Apr 21 09:11:21 2011 +1000
	111
	112	Add more docstrings
	113
	114	commit 0b9a36bd23b0ccb4ed99cc3857aafe6c52710861
	115	Author: Will Thompson <will.thompson@collabora.co.uk>
	116	Date: Wed Apr 20 16:45:36 2011 +0100
	117
	118	bump
	119
	120	commit 415f9cf8ea7c0b3b8dcfb7108ec164d7057ee6be
	121	Merge: 0a54dcc 9d6988f
	122	Author: Will Thompson <will.thompson@collabora.co.uk>
	123	Date: Wed Apr 20 16:41:11 2011 +0100
	124
	125	Merge branch 'Makefile-rule-clarifications' into telepathy-spec-0.22
	126
	127	Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=35951>
	128	Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
	129
	130	commit 0a54dccca0ed04a554c3ff1078fff4d7feb5b434
	131	Author: Will Thompson <will.thompson@collabora.co.uk>
	132	Date: Wed Apr 20 16:36:16 2011 +0100
	133
	134	Version 0.22.2
	135
	136	commit 5376afef500ebfaf7d4fc84955b22ade26ced0a8
	137	Author: Will Thompson <will.thompson@collabora.co.uk>
	138	Date: Wed Apr 20 16:28:02 2011 +0100
	139
	140	NEWS for 0.22.2
	141
	142	commit 8d8156d13bef1d840827774166be25b37a9fe7bd
	143	Merge: 227ab7a b59ef2f
	144	Author: Will Thompson <will.thompson@collabora.co.uk>
	145	Date: Wed Apr 20 16:29:57 2011 +0100
	146
	147	Merge branch 'manage-credit-36254' into telepathy-spec-0.22
	148
	149	Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=36254>
	150
	151	commit 227ab7ac0da9ec1ef429059ef6b90b18d0e20dad
	152	Merge: 2b84482 e3ebab0
	153	Author: Will Thompson <will.thompson@collabora.co.uk>
	154	Date: Wed Apr 20 16:29:42 2011 +0100
	155
	156	Merge branch 'more-status-identifiers' into telepathy-spec-0.22
	157
	158	Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=36159>
	159	Reviewed-by: Danielle Madeley <danielle.madeley@collabora.co.uk>
	160
	161	commit b59ef2fb0afbef471966ed5c06339d3319e97627
	162	Author: Will Thompson <will.thompson@collabora.co.uk>
	163	Date: Wed Apr 20 16:11:40 2011 +0100
	164
	165	ManageCreditURI: undefined before Connected.
	166
	167	commit 2b844829f43baa4b55b0c89353ab4eca5a6f35d1
	168	Merge: 735fb9a 531fc51
	169	Author: Andre Moreira Magalhaes (andrunko) <andre.magalhaes@collabora.co.uk>
	170	Date: Wed Apr 20 12:06:09 2011 -0300
	171
	172	Merge branch 'presence-status-max'
	173
	174	Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
	175
	176	commit 531fc512966c45b06b84f9d9c316e64096662496
	177	Author: Andre Moreira Magalhaes (andrunko) <andre.magalhaes@collabora.co.uk>
	178	Date: Tue Apr 19 12:42:10 2011 -0300
	179
	180	Add tp:added to Conn.SimplePresence.MaximumStatusMessageLength.
	181
	182	commit 9344af486f3550ff0f032ed5286fee63c7601940
	183	Author: Andre Moreira Magalhaes (andrunko) <andre.magalhaes@collabora.co.uk>
	184	Date: Tue Apr 19 12:36:57 2011 -0300
	185
	186	Reword the doc for Conn.SimplePresence.MaximumStatusMessageLength.
	187
	188	commit e3ebab0b2f6a5bc0bbdc2f7cb122824922681654
	189	Author: Will Thompson <will.thompson@collabora.co.uk>
	190	Date: Fri Apr 15 13:26:49 2011 +0100
	191
	192	Style tables in docstrings more pleasingly
	193
	194	The colours and styles are designed to match the summary at the start of
	195	each interface page.
	196
	197	The tr:nth-child(even) rule styles every other row with a slightly
	198	darker background, which makes it easier to read the only two tables we
	199	have (the well-known status identifiers, and the many states of Call
	200	channels). :nth-child is from CSS3. It looks fine without it, but better
	201	with it.
	202
	203	border-collapse: collapse; is like cellspacing='0'.
	204
	205	commit c9063da61205f902ac074d906c7b7f9d6589a638
	206	Author: Will Thompson <will.thompson@collabora.co.uk>
	207	Date: Fri Apr 15 13:23:19 2011 +0100
	208
	209	SimplePresence: prettify the well-known identifier table
	210
	211	commit 5974895cc0fc0922fbc71aab9e641e93f98ab252
	212	Author: Will Thompson <will.thompson@collabora.co.uk>
	213	Date: Fri Apr 15 11:48:58 2011 +0100
	214
	215	SimplePresence: add 'pstn'.
	216
	217	Thanks to Danni for the idea!
	218
	219	Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=36159>
	220
	221	commit 02a317533ee3208827212d0663827df7fe4197ca
	222	Author: Will Thompson <will.thompson@collabora.co.uk>
	223	Date: Fri Apr 15 11:44:51 2011 +0100
	224
	225	SimplePresence: specify 'chat'
	226
	227	Gabble's implemented this forever. ICQ also has this concept. It should
	228	be written down.
	229
	230	commit b2cb2280710f38563125f5d57df850393461be41
	231	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	232	Date: Fri Apr 15 15:22:01 2011 +1000
	233
	234	Add property ManageCreditURI
	235
	236	Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=36254
	237
	238	commit 87142f587b1bebbd06bb144dc9795cef83433eb5
	239	Author: Andre Moreira Magalhaes (andrunko) <andre.magalhaes@collabora.co.uk>
	240	Date: Thu Apr 14 02:59:26 2011 -0300
	241
	242	Add Conn.SimplePresence.MaximumStatusMessageLength.
	243
	244	commit 735fb9a40fee31112f1100ab16a45bdde70cf727
	245	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	246	Date: Mon Apr 11 15:04:46 2011 +0200
	247
	248	Properties on Protocol.Interface.Avatars should be immutables
	249
	250	commit 14345ebf68847d66b09c693472650c7ff3f5872c
	251	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	252	Date: Wed Apr 6 12:25:15 2011 +1000
	253
	254	Add method GetSMSLength() to allow SMS message chunking to be shown to the user
	255
	256	commit 5feaec96b1cd2a13d09b8250cb29c9ac70d1eb82
	257	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	258	Date: Mon Apr 4 15:30:20 2011 +1000
	259
	260	Clarify contact capabilities for SMS channels
	261
	262	commit 1e12c8f10863011c93e43b863045e701374a4996
	263	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	264	Date: Mon Apr 4 15:08:18 2011 +1000
	265
	266	Clarify ofdT.Error.InsufficientBalance can be used in message delivery reports
	267
	268	commit 9d6988fcd59c49f8925b671bf1d66f066c683be9
	269	Author: Will Thompson <will.thompson@collabora.co.uk>
	270	Date: Wed Mar 30 18:01:08 2011 +0100
	271
	272	Makefile: clarify check and dist rules
	273
	274	Currently large swathes of 'check' and 'dist' are a series of shell
	275	commands chained together into one command for make's purposes, with set
	276	-e to make the first error fatal. This makes it hard to see what's wrong
	277	when they fail. For instance, the case I hit today was that I'd
	278	forgotten to sign the tarball; I had no way of knowing that it was the
	279	`test -f telepathy-spec-$$version.tar.gz.asc` command that had failed.
	280
	281	In some realities the right solution would be to import
	282	maintainer-make-release from tp-glib, but I don't really fancy
	283	disentangling the Automakey bits from that right now. So this patch
	284	basically just breaks the über-commands into individual commands.
	285
	286	(This syntax:
	287
	288	FOO := bar
	289
	290	is a GNU Make-ism which means “evaluate bar once, and then assign its
	291	result to FOO”. If we instead used:
	292
	293	VERSION = `sed ...`
	294
	295	then the sed invocation would be evaluated once for each use of
	296	$(VERSION). Since we already depend on GNU Make for things like
	297	$(filter-out) I see no reason not to use the eminently-sensible :=
	298	syntax.)
	299
	300	commit 25d0bd3b5739d7cea6c41080bddf2a25d56793db
	301	Author: Will Thompson <will.thompson@collabora.co.uk>
	302	Date: Wed Mar 30 15:39:30 2011 +0100
	303
	304	Post-release version bump to 0.22.1.1
	305
	306	commit b7f4755f48df80588631ded8a66f559355689325
	307	Author: Will Thompson <will.thompson@collabora.co.uk>
	308	Date: Wed Mar 30 14:19:58 2011 +0100
	309
	310	Annotate new API with tp:added
	311
	312	commit 1bb0c2e897fbd9b7e2527454cf8dac667fea76db
	313	Author: Will Thompson <will.thompson@collabora.co.uk>
	314	Date: Wed Mar 30 14:17:51 2011 +0100
	315
	316	Surprise! Version 0.22.1
	317
	318	commit 3cf218bc9cd3e9cefb695b43645a71ddc967ecf9
	319	Author: Will Thompson <will.thompson@collabora.co.uk>
	320	Date: Wed Mar 30 13:48:31 2011 +0100
	321
	322	StreamHandler: ugly-case Header_Extensions arguments
	323
	324	commit a24eed537e20d2b174a6b3b89ecf2dac07b18fe3
	325	Author: Will Thompson <will.thompson@collabora.co.uk>
	326	Date: Wed Mar 30 13:48:05 2011 +0100
	327
	328	StreamHandler: remove evil tabs
	329
	330	commit 62da921ae728247dd7ac1aa59423cddee289fa6e
	331	Merge: c3c49f9 4fe991f
	332	Author: Will Thompson <will.thompson@collabora.co.uk>
	333	Date: Wed Mar 30 13:40:00 2011 +0100
	334
	335	Merge remote-tracking branch 'ocrete/streamhandler-exthdr-rtcpfb'
	336
	337	commit c3c49f90161d76a2f3c8454c49f6580fc60b220b
	338	Author: Simon McVittie <simon.mcvittie@collabora.co.uk>
	339	Date: Fri Dec 17 10:52:58 2010 +0000
	340
	341	Describe the (unusual!) expected channel class for ContactSearch channels
	342
	343	Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
	344
	345	commit de8d9a98e1502d740d43cbfb63b47ce89008fa4f
	346	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	347	Date: Tue Mar 29 10:15:54 2011 +1100
	348
	349	New error InsufficientBalance
	350
	351	Used as a CallStateReason.
	352
	353	Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=35755
	354
	355	commit bedca93acdc4d80a770f2519cebe2db763095ddd
	356	Author: Will Thompson <will.thompson@collabora.co.uk>
	357	Date: Tue Mar 22 14:32:35 2011 +0000
	358
	359	Clarify GetParameters and Protocol.Parameters docs more
	360
	361	commit c1abbbfc956c93c6b35af7ade3519b219f92f303
	362	Author: Will Thompson <will.thompson@collabora.co.uk>
	363	Date: Tue Mar 22 14:10:19 2011 +0000
	364
	365	RequestConnection: document that apps should use AM instead
	366
	367	It wasn't previously obvous from looking at the RequestConnection method
	368	that applications shouldn't actually use it … so let's fix that. While
	369	we're here, refer to Account.Parameters from GetParameters and from
	370	Protocol.Parameters (which post-dates the AccountManager and yet doesn't
	371	reference it!).
	372
	373	commit 76a555859e0e531ed7bd3a058a0f055f1537c526
	374	Author: Will Thompson <will.thompson@collabora.co.uk>
	375	Date: Mon Mar 21 17:45:36 2011 +0000
	376
	377	post-release version bump
	378
	379	commit e19047ae32094d8a33b3f90ecb3418794097690b
	380	Author: Will Thompson <will.thompson@collabora.co.uk>
	381	Date: Mon Mar 21 17:27:56 2011 +0000
	382
	383	Version 0.22.0
	384
	385	commit b4da6dd51807749bfe2de8274fa71f299074d1aa
	386	Author: Will Thompson <will.thompson@collabora.co.uk>
	387	Date: Mon Mar 21 17:22:46 2011 +0000
	388
	389	NEWS for 0.22
	390
	391	commit ceeac58cf83a22c54bdc89ef70706b14c280d4eb
	392	Author: Will Thompson <will.thompson@collabora.co.uk>
	393	Date: Mon Mar 21 17:03:36 2011 +0000
	394
	395	README: expunge Merge Monkey reference
	396
	397	commit 3f8a69d0b6938bed57e2b37df2cd64215fed9613
	398	Author: Will Thompson <will.thompson@collabora.co.uk>
	399	Date: Mon Mar 21 14:01:43 2011 +0000
	400
	401	ConnectionError: define server-message key.
	402
	403	Really? We didn't have a well-defined key for a human-readable message
	404	from the server already? This was part of the point of this signal.
	405
	406	Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
	407
	408	commit 8024150ae2f9d08343700d9a47b83fd3fe89236c
	409	Author: Will Thompson <will.thompson@collabora.co.uk>
	410	Date: Fri Mar 18 15:04:01 2011 +0000
	411
	412	Bump nano-version
	413
	414	commit bd99f1cc73c3bff64051d9d62d5308ce6d859c18
	415	Author: Will Thompson <will.thompson@collabora.co.uk>
	416	Date: Fri Mar 18 13:55:54 2011 +0000
	417
	418	Version 0.21.13
	419
	420	commit 0ed690148724fca3be8c508c15071d659eba2b10
	421	Author: Will Thompson <will.thompson@collabora.co.uk>
	422	Date: Fri Mar 18 13:42:33 2011 +0000
	423
	424	NEWS for ReferenceIdentities.
	425
	426	commit 4b16e9b7a2416a9342ee22343bebffe9ee3d39ac
	427	Author: Will Thompson <will.thompson@collabora.co.uk>
	428	Date: Fri Mar 18 14:18:57 2011 +0000
	429
	430	Re-re-re-clarify ReferenceIdentities
	431
	432	commit 778f47d4867567d9e04403e50215d0ecd7cf527a
	433	Author: Will Thompson <will.thompson@collabora.co.uk>
	434	Date: Fri Mar 18 14:10:32 2011 +0000
	435
	436	ServerTLSConnection: be stricter about ReferenceIdentities
	437
	438	There's no reason for this property to be implemented but empty. Also, I
	439	think it should be mandatory to include the Hostname in this property.
	440
	441	commit ee19030d9f71a8219f94cf0256881b7baee5e36a
	442	Author: Will Thompson <will.thompson@collabora.co.uk>
	443	Date: Fri Mar 18 13:39:36 2011 +0000
	444
	445	ServerTLSConnection: improve ReferenceIdentities docs
	446
	447	commit 8c3c52fc9e84c05173fcf61717709f7ab89bf1a0
	448	Author: Will Thompson <will.thompson@collabora.co.uk>
	449	Date: Fri Mar 18 12:47:06 2011 +0000
	450
	451	ServerTLSConnection: annotate properties as immutable.
	452
	453	commit 4aa5249c4b78df0f3e842f46521c39ca22c9a521
	454	Author: Stef Walter <stefw@collabora.co.uk>
	455	Date: Fri Mar 18 12:42:09 2011 +0100
	456
	457	Doc and naming fixes for ServerTLSConnection.ReferenceIdentities
	458
	459	commit 19d4def6459766b82277eab506b5fb770d912c57
	460	Author: Stef Walter <stefw@collabora.co.uk>
	461	Date: Fri Mar 11 11:14:11 2011 +0100
	462
	463	Add ServerTLSConnection.ReferenceIdentities property.
	464
	465	The certificate identity can be checked against more than just
	466	one piece of information. Add a property to ServerTLSConnection
	467	which will contain all the identities that the certificate identity
	468	can match.
	469
	470	https://bugs.freedesktop.org/show_bug.cgi?id=35408
	471
	472	commit f30d22efb6353b661833cf6fb1c259564bdca03a
	473	Author: Will Thompson <will.thompson@collabora.co.uk>
	474	Date: Tue Mar 15 09:33:35 2011 +0000
	475
	476	Correct em dash HTML entities in page titles.
	477
	478	commit 3f4cc5bf050ee7e3452d3ede8f18b2cccde26bf2
	479	Author: Will Thompson <will.thompson@collabora.co.uk>
	480	Date: Mon Mar 14 11:27:28 2011 +0000
	481
	482	NEWS for ContactBlocking
	483
	484	commit 09c38753e6e865785a236b51c7dfdf6f1224c557
	485	Author: Will Thompson <will.thompson@collabora.co.uk>
	486	Date: Mon Mar 14 11:17:02 2011 +0000
	487
	488	Blocking: <code>ify /blocked attribute definition.
	489
	490	commit ecd136f47d4137391507b9a8a1b7e6bd016b3024
	491	Author: Will Thompson <will.thompson@collabora.co.uk>
	492	Date: Mon Mar 14 11:14:53 2011 +0000
	493
	494	Blocking: add identifiers to signalled handle sets
	495
	496	commit 76307699f1948b3748035d266108ff7d5d2a94f3
	497	Merge: 4c55d49 fd0f17e
	498	Author: Will Thompson <will.thompson@collabora.co.uk>
	499	Date: Mon Mar 14 10:55:40 2011 +0000
	500
	501	Merge branch 'blocking'
	502
	503	Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=28423>
	504
	505	commit fd0f17ecbca2b6d22e31b2d17acb79dbf87c8aee
	506	Author: Will Thompson <will.thompson@collabora.co.uk>
	507	Date: Mon Mar 14 10:54:24 2011 +0000
	508
	509	Undraft ContactBlocking.
	510
	511	commit 4c55d49925a90fd026370057df18d1b8d860dbec
	512	Merge: 3a77d9c 131d606
	513	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	514	Date: Fri Mar 11 20:49:05 2011 +1100
	515
	516	Merge branch 'fixes-33485'
	517
	518	commit 3a77d9c9a518b1614ee174dff553bd4b9a39e03a
	519	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	520	Date: Wed Mar 9 14:06:51 2011 +0100
	521
	522	start dev of next release
	523
	524	commit e98ce4f01690d5ffb081b5da725afeee31b189af
	525	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	526	Date: Wed Mar 9 13:54:08 2011 +0100
	527
	528	document when Cellular.MessageNationalCharacterSet has been added
	529
	530	commit d3fca2c6163cb7f0446841528ffa46bce8680228
	531	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	532	Date: Wed Mar 9 13:52:20 2011 +0100
	533
	534	prepare 0.21.12
	535
	536	commit 1f75b7dd55cbba6cceec12df393354023b989bb1
	537	Author: Jonathon Jongsma <jonathon.jongsma@collabora.co.uk>
	538	Date: Mon Mar 7 17:26:42 2011 -0600
	539
	540	Add EmergencyCallsNotSupported error
	541
	542	https://bugs.freedesktop.org/show_bug.cgi?id=35098
	543
	544	commit c054588a9a4397d3332767df50948a368590cc16
	545	Merge: d81aa5a f30cd5c
	546	Author: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
	547	Date: Wed Mar 9 11:12:40 2011 +0000
	548
	549	Merge remote-tracking branch 'danni/software-upgrade-required-35100' into new-errors
	550
	551	commit f30cd5c12eed59610395675c87367fa0272bd4f9
	552	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	553	Date: Wed Mar 9 09:43:07 2011 +1100
	554
	555	Add appropriate Connection_Status_Reason to the description
	556
	557	commit ced5456d598f050dcaae3b399384d2403d297dc8
	558	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	559	Date: Tue Mar 8 12:03:52 2011 +1100
	560
	561	Add error SoftwareUpgradeRequired
	562
	563	Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=35100
	564
	565	commit 18bcb88da3d05fa8e03f5a09a9275435eed18811
	566	Author: Will Thompson <will.thompson@collabora.co.uk>
	567	Date: Tue Mar 8 18:34:24 2011 +0000
	568
	569	BlockContacts: remove unnecessary rationale.
	570
	571	commit d81aa5a223c5754a66995e1884fe16ddb3a3fa87
	572	Author: Marco Barisione <marco@barisione.org>
	573	Date: Thu Mar 3 18:41:48 2011 +0000
	574
	575	Add C.I.Cellular.MessageNationalCharacterSet
	576
	577	Add the MessageNationalCharacterSet property for
	578	country/language-specific encodings and document how it interacts with
	579	the MessageReducedCharacterSet property.
	580
	581	commit 97ee740bae02746ced600fc0ff4029f235191fa5
	582	Author: Will Thompson <will.thompson@collabora.co.uk>
	583	Date: Tue Mar 8 14:32:12 2011 +0000
	584
	585	Update interface index for ContactBlocking
	586
	587	commit dcfc081f9af5f992c8b71e38cdf17ae770165264
	588	Author: Will Thompson <will.thompson@collabora.co.uk>
	589	Date: Tue Mar 8 14:21:14 2011 +0000
	590
	591	ContactBlocking: bump copyright year
	592
	593	commit be333848f7e9262ffc68dffc680539ddfcdb59b2
	594	Author: Will Thompson <will.thompson@collabora.co.uk>
	595	Date: Tue Mar 8 14:20:04 2011 +0000
	596
	597	ContactBlocking: remove unhelpful possible-errors list.
	598
	599	All of these errors are completely standard; if we're not adding any
	600	useful information about why they might occur, let's just bin them.
	601
	602	commit 49cf01d5331ee2f2b267d64c65fdb46738623cff
	603	Author: Will Thompson <will.thompson@collabora.co.uk>
	604	Date: Tue Mar 8 14:17:07 2011 +0000
	605
	606	ContactBlocking: require ignoring no-op requests
	607
	608	commit 87e1697a250feaee6b3e5ab70b174ffb8c110a7b
	609	Author: Will Thompson <will.thompson@collabora.co.uk>
	610	Date: Tue Mar 8 14:13:15 2011 +0000
	611
	612	BlockedContactsChanged: Ugly_Case argument names
	613
	614	commit 0420972ed0e8895a4fd8cfaf4f2656f6301e0ce1
	615	Author: Will Thompson <will.thompson@collabora.co.uk>
	616	Date: Tue Mar 8 13:45:33 2011 +0000
	617
	618	Clarify ContactBlockingCapabilities documentation
	619
	620	commit e3245628a711300f7bf599fafbb7435d6b94227d
	621	Author: Will Thompson <will.thompson@collabora.co.uk>
	622	Date: Tue Mar 8 13:43:02 2011 +0000
	623
	624	ContactBlocking: add a brief overview.
	625
	626	commit 33b21d7dcc3f98a7ca06ab3a83622b3e5ae325b1
	627	Author: Will Thompson <will.thompson@collabora.co.uk>
	628	Date: Tue Mar 8 13:42:39 2011 +0000
	629
	630	ContactBlocking: note that this is for persistent blocking
	631
	632	commit ba1474f553e030ca57879eb8b040ec9559b1087b
	633	Author: Will Thompson <will.thompson@collabora.co.uk>
	634	Date: Tue Mar 8 13:25:12 2011 +0000
	635
	636	BlockContacts: CMs SHOULD ignore Report_Abusive if unsupported
	637
	638	I agree with Sjoerd's rationale at
	639	<https://bugs.freedesktop.org/show_bug.cgi?id=28423#c7>, which I've
	640	included in a rationale block.
	641
	642	commit e396bc304c2d25b08da46db05a34c71f763b185d
	643	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	644	Date: Mon Feb 14 10:24:12 2011 +1100
	645
	646	Support for reporting abusive contacts
	647
	648	commit 983bfb2707ff3d26c7976eddd7dffd39791fa39b
	649	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	650	Date: Mon Feb 14 10:07:39 2011 +1100
	651
	652	Add xmlnses to docstrings, fix pluralisation
	653
	654	commit f8436f1a34a04203c4a7ce1ba533d47798ff5a58
	655	Author: Simon McVittie <simon.mcvittie@collabora.co.uk>
	656	Date: Wed Nov 24 17:10:45 2010 +0000
	657
	658	ContactBlocking: mark as experimental
	659
	660	commit 92ca7997909ff9b4d382dea1dbf5cadcd7111e4e
	661	Author: Simon McVittie <simon.mcvittie@collabora.co.uk>
	662	Date: Mon Jun 7 13:12:04 2010 +0100
	663
	664	Add Connection.Interface.Blocking draft
	665
	666	commit 2b76dfc602af9367feced6793eb6db715e4a936d
	667	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
	668	Date: Fri Mar 4 13:39:06 2011 +0100
	669
	670	start dev of next version
	671
0	672	commit 8270839e6c706be8260917ab9b8d3b1b14c874a6
1	673	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
2	674	Date: Fri Mar 4 13:34:06 2011 +0100

8	680	Date: Thu Mar 3 14:33:23 2011 +0100
9	681
10	682	prepare 0.21.11
	683
	684	commit 4fe991f019faad398a91ef130e730afc45111b36
	685	Author: Olivier Crête <olivier.crete@collabora.co.uk>
	686	Date: Thu Feb 10 17:41:10 2011 +0000
	687
	688	StreamHandler: Add method and signal for RTP Header Extensions
	689
	690	commit eac621244f99d694669bb3e2665535d94965b09d
	691	Author: Olivier Crête <olivier.crete@collabora.co.uk>
	692	Date: Thu Feb 10 13:06:18 2011 +0000
	693
	694	StreamHandler: Add method and signal for RTCP Feedback Messages (aka rtcp-fb)
	695
	696	commit 96f1880c411e0b7b999dbf03a710a2f302b3ffca
	697	Author: Olivier Crête <olivier.crete@collabora.co.uk>
	698	Date: Thu Feb 10 12:00:17 2011 +0000
	699
	700	StreamHandler: Add types for rtp-hdrext
	701
	702	commit 006274077a0b8190741344b7dce36af94462e6cd
	703	Author: Olivier Crête <olivier.crete@collabora.co.uk>
	704	Date: Thu Feb 10 11:17:17 2011 +0000
	705
	706	StreamHandler: Add types for rtcp-fb
	707
	708	commit d1511d25a3d707508b55084c7a24adc336e90984
	709	Author: Olivier Crête <olivier.crete@collabora.co.uk>
	710	Date: Thu Feb 10 12:56:18 2011 +0000
	711
	712	StreamHandler: Move docstring to the top
11	713
12	714	commit 177372c96aec2aa3fe9c7ae6c0acbcda220bbb96
13	715	Author: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>

63	765	Date: Thu Feb 24 12:17:11 2011 +0100
64	766
65	767	prepare 0.21.10
	768
	769	commit 131d6067cf1213de7b9d675ee067bc7da4151a13
	770	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	771	Date: Wed Feb 23 11:33:10 2011 +1100
	772
	773	Note how change notification is done for Accounts
	774
	775	commit a66e5a176c65f6d8407382b8f59e39667faec821
	776	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	777	Date: Wed Feb 23 11:28:36 2011 +1100
	778
	779	Note how change of the property should be heralded.
	780
	781	commit 9fe3e0c93827d91f406bcef52146c570447b549a
	782	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	783	Date: Wed Feb 23 11:15:32 2011 +1100
	784
	785	Remove HTML from unnamespaced tp:docstring
	786
	787	commit 80fdb1c87fa7dc3218033b6a591f547d43ee625c
	788	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	789	Date: Wed Feb 23 11:08:54 2011 +1100
	790
	791	Clarify when objects should implement this interface
	792
	793	commit 8901755d9972732bac060c67b2884182bd93ef71
	794	Author: Danielle Madeley <danielle.madeley@collabora.co.uk>
	795	Date: Wed Feb 23 11:04:14 2011 +1100
	796
	797	Use shorthand for D-Bus namespaces
66	798
67	799	commit 934a0985c4b9757d56bc63b4c9c6b253443c6aed
68	800	Merge: 1af47cc e2e7b9b

+24

-27

Makefile less more

8	8
9	9	XMLS = $(wildcard spec/*.xml)
10	10	TEMPLATES = $(wildcard doc/templates/*)
	11
	12	VERSION := $(shell sed -ne s'!<tp:version>$.*$</tp:version>!\1!p' spec/all.xml)
	13	DISTNAME := telepathy-spec-$(VERSION)
11	14
12	15	GENERATED_FILES = \
13	16	doc/spec/index.html \

30	33
31	34	check: all FIXME.out
32	35	$(PYTHON) test/test-specparser.py
33		@version="`sed -ne s'!<tp:version>$.*$</tp:version>!\1!p' spec/all.xml`";\
34		case "$$version" in \
	36	@case "$(VERSION)" in \
35	37	...) ;; \
36	38	*) \
	39	echo "Grepping spec for UNRELEASED..."; \
37	40	if grep -r UNRELEASED $(CHECK_FOR_UNRELEASED); \
38	41	then \
39	42	echo "^^^ This is meant to be a release, but some files say UNRELEASED" >&2; \

61	64
62	65	maintainer-upload-release: doc/spec/index.html check
63	66	@install -d tmp
64		set -e ; \
65		version="`sed -ne s'!<tp:version>$.*$</tp:version>!\1!p' spec/all.xml`";\
66		if ! echo $$version \| egrep '[0-9]+\.[0-9]+\.[0-9]+'; then \
67		echo 'This does not look like a spec release'; \
	67	@if ! echo $(VERSION) \| egrep '[0-9]+\.[0-9]+\.[0-9]+'; then \
	68	echo $(VERSION) 'does not look like a spec release'; \
68	69	exit 1; \
69		fi; \
70		test -f telepathy-spec-$$version.tar.gz; \
71		test -f telepathy-spec-$$version.tar.gz.asc; \
72		gpg --verify telepathy-spec-$$version.tar.gz.asc; \
73		rsync -vzP telepathy-spec-$$version.tar.gz telepathy.freedesktop.org:/srv/telepathy.freedesktop.org/www/releases/telepathy-spec/ ; \
74		rsync -vzP telepathy-spec-$$version.tar.gz.asc telepathy.freedesktop.org:/srv/telepathy.freedesktop.org/www/releases/telepathy-spec/ ; \
75		rsync $(DOC_RSYNC_FLAGS) doc/spec/ telepathy.freedesktop.org:/srv/telepathy.freedesktop.org/www/spec/ ; \
	70	fi
	71	test -f telepathy-spec-$(VERSION).tar.gz
	72	test -f telepathy-spec-$(VERSION).tar.gz.asc
	73	gpg --verify telepathy-spec-$(VERSION).tar.gz.asc
	74	rsync -vzP telepathy-spec-$(VERSION).tar.gz telepathy.freedesktop.org:/srv/telepathy.freedesktop.org/www/releases/telepathy-spec/
	75	rsync -vzP telepathy-spec-$(VERSION).tar.gz.asc telepathy.freedesktop.org:/srv/telepathy.freedesktop.org/www/releases/telepathy-spec/
	76	rsync $(DOC_RSYNC_FLAGS) doc/spec/ telepathy.freedesktop.org:/srv/telepathy.freedesktop.org/www/spec/
76	77	rsync $(DOC_RSYNC_FLAGS) doc/spec/ telepathy.freedesktop.org:/srv/telepathy.freedesktop.org/www/spec-snapshot/
77	78
78	79	dist: check
79	80	@install -d tmp
80		set -e ;\
81		version="`sed -ne s'!<tp:version>$.*$</tp:version>!\1!p' spec/all.xml`";\
82		distname="telepathy-spec-$$version";\
83		rm -f tmp/ChangeLog "$$distname".tar "$$distname".tar.gz; \
84		$(GIT) archive --format=tar --prefix="$$distname"/ "HEAD^{tree}" \
85		> "$$distname".tar;\
86		rm -rf tmp/"$$distname";\
87		mkdir tmp/"$$distname";\
88		$(GIT) log telepathy-spec-0.16.0.. > tmp/"$$distname"/ChangeLog; \
89		$(TAR) -rf "$$distname".tar -C tmp --owner 0 --group 0 --mode 0664 \
90		"$$distname"/ChangeLog;\
91		$(GZIP) -9 "$$distname".tar;\
92		$(TAR) -ztvf "$$distname".tar.gz;\
93		rm -rf tmp/"$$distname"
	81	rm -f tmp/ChangeLog "$(DISTNAME)".tar "$(DISTNAME)".tar.gz
	82	$(GIT) archive --format=tar --prefix="$(DISTNAME)"/ "HEAD^{tree}" \
	83	> "$(DISTNAME)".tar
	84	rm -rf tmp/"$(DISTNAME)"
	85	mkdir tmp/"$(DISTNAME)"
	86	$(GIT) log telepathy-spec-0.16.0.. > tmp/"$(DISTNAME)"/ChangeLog
	87	$(TAR) -rf "$(DISTNAME)".tar -C tmp --owner 0 --group 0 --mode 0664 \
	88	"$(DISTNAME)"/ChangeLog
	89	$(GZIP) -9 "$(DISTNAME)".tar
	90	rm -rf tmp/"$(DISTNAME)"
94	91
95	92	BRANCH = $(shell sh tools/git-which-branch.sh misc \| tr -d '\n' \| tr -C "[:alnum:]" _)
96	93	UPLOAD_BRANCH_TO = people.freedesktop.org:public_html/telepathy-spec

+104

-391

NEWS less more

1	1	For full details, see the ChangeLog in tarballs, or "git log" in Git
2	2	checkouts.
3	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)
	4	telepathy-spec 0.23.1 (2011-05-09)
49	5	==================================
50	6
51		“Are you ready for what's coming?”
	7	This first release in the 0.23 development branch contains all the fixes and
	8	additions from 0.22.3.
52	9
53		“Ready as I'll ever be.”
	10	Enhancements:
54	11
55		New stable API:
	12	• Channel.Interface.SMS.GetSMSLength() to allow SMS message chunking to be
	13	shown to the user. (Danni)
56	14
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)
	15	• ChannelDispatcher.DelegateChannels() to move channels between handlers.
	16	(fdo #25293, Guillaume)
60	17
61		Changes to unstable API:
	18	• ChannelDispatcher.PresentChannel(): convenient API to re-ensure an existing
	19	channel. (fdo #25293, Guillaume)
62	20
63		• Move the Packetization property from Call.Content to
64		Call.Content.Interface.Media (sjoerd)
65	21
66		telepathy-spec 0.21.8 (2010-12-20)
	22	telepathy-spec 0.22.3 (2011-05-09)
67	23	==================================
68	24
69		The “I own a high-powered assault rifle; I own a 12-guage double-barrel
70		shotgun” release.
	25	Fixes:
71	26
72		New stable API:
	27	• Correct DBus_Property-parameter boilerplate. (fdo #37005, Will)
73	28
74		• Add a ContactList.ContactsChangedByID signal, which supplements
75		ContactList.ContactsChanged by providing contact IDs along with
76		handles. Accordingly, ContactsChanged is now deprecated. (fd.o#32467,
77		smcv)
78
79		Changes to unstable API:
80
81		• Remove the once-implemented but never-used
82		Account.Interface.MinimumPresence. (fd.o#29811, wjt)
83
84		Tools changes:
85
86		• Allow <annotation>s on interfaces, and interpret standard
87		<annotation>s. (Alex Merry)
88
89		• Don't generate ‘Generic Types’ and ‘Errors’ if there's no content for
90		them. (Alex Merry)
91
92		telepathy-spec 0.21.7 (2010-12-10)
	29	telepathy-spec 0.22.2 (2011-04-20)
93	30	==================================
94	31
95		The "health, safety and Grolsch at work" release.
	32	The “every cell stayed the same” release.
96	33
97		New stable API:
	34	Once again, this release in the stable series includes some minor API
	35	additions.
98	36
99		• Add ability to explicitly request an SMS channel to a contact. (danni)
	37	Enhancements:
100	38
101		• Add AuthenticationTypes Protocol property. (jonny)
	39	• Channel.Interface.SMS now includes some sample contact capabilities.
	40	(Danni)
102	41
103		• The MessageSent signal should include message-sender etc. (smcv)
	42	• Connection.Interface.Balance now has a ManageCreditURI property.
	43	(fd.o#36254, Danni)
104	44
105		Clarifications:
	45	• Connection.Interface.SimplePresence now has a
	46	MaximumStatusMessageLength property. (fd.o#33054, André)
106	47
107		• Explicitly forbid message-sender etc. when calling SendMessage, matching
108		how telepathy-glib behaves (smcv)
	48	• SimplePresence defines two new well-known status identifiers: "pstn"
	49	and "chat". (fd.o#36159, Danni vs. Will)
109	50
110		Tools changes:
	51	Fixes:
111	52
112		• Produce two devhelp index entries for each symbol. (smcv)
	53	• Protocol.Interface.Avatars properties are documented to be immutable.
	54	(Guillaume)
113	55
114		telepathy-spec 0.21.6 (2010-12-01)
	56	• The tables in SimplePresence and Call's HTML documentation look nicer.
	57
	58	telepathy-spec 0.22.1 (2011-03-30)
115	59	==================================
116	60
117		The "recent change in the nature of fish" release.
	61	The “we can change the things we know” release.
118	62
119		Changes to stable API:
	63	Unconventionally, this release in the 0.22 stable series of the
	64	specification contains minor API additions. This is not intended to
	65	become a trend; once major changes land in the specification and a
	66	release is made in the 0.23.x unstable series, no new API will be added
	67	to the stable branch.
	68
	69	• A new error code, InsufficientBalance, has been added, along with a
	70	balance-required key for the CallStateDetails dictionary. (Danni)
	71
	72	• Media.StreamHandler has grown two new method/signal pairs, namely
	73	SetRemoteFeedbackMessages/SupportedFeedbackMessages and
	74	SetRemoteHeaderExtensions/SupportedHeaderExtensions, plus some related
	75	types, for enabling exciting RTP header extensions and RTCP feedback
	76	messages.
	77
	78	telepathy-spec 0.22.0 (2011-03-21)
	79	==================================
	80
	81	The “literate small talk” release.
	82
	83	This is a new stable version of telepathy-spec, intended to serve as a
	84	reference point for future work. There were no API changes since
	85	development release 0.21.13; significant additions and changes to
	86	non-DRAFT interfaces from the year-and-a-half of development since
	87	0.20.0 are summarized below.
	88
	89	The versions of libraries, connection managers and Mission Control
	90	recommended for use with GNOME 3.0 (such as the upcoming telepathy-glib
	91	0.14) can be expected to support most of the API from this spec release.
	92
	93	Changes to existing API
	94	-----------------------
120	95
121	96	• Handles are no longer expected to be reference-counted - instead, they
122		persist as long as the Connection does. A new property HasImmortalHandles
123		indicates whether this is the case. telepathy-glib 0.13.8 will implement
124		these semantics automatically for most connection managers. (smcv)
	97	persist as long as the Connection does. A new property,
	98	HasImmortalHandles, indicates whether this is the case. Versions of
	99	telepathy-glib since 0.13.8 implement these semantics, and set that
	100	property, automatically for most connection managers.
125	101
126		Tools changes:
127
128		• add support for tp:immutable="sometimes" (smcv)
129
130		• add support for <tp:client-interest/> (danni)
131
132		telepathy-spec 0.21.5 (2010-11-25)
133		==================================
134
135		The "For the fictional pink sentient fungus, see Mi-go" release.
136
137		Changes to stable API:
138
139		• fd.o #29376: Chan.T.Text now requires Chan.I.Messages (cassidy, smcv)
140
141		• fd.o #23155: message-token has been redefined from "globally unique"
	102	• message-token has been redefined from "globally unique"
142	103	to "whatever's in the underlying protocol", replacing the unimplemented
143	104	protocol-token. This makes it feasible to implement message-token again.
144	105	Note that connection managers implementing message-token should not be
145	106	backported to Maemo 5, since its event logger assumes that message-token
146		is guaranteed to be unique, which is usually unimplementable. (wjt)
	107	is guaranteed to be unique, which is usually unimplementable.
147	108
148		Deprecations:
149
150		• Most of Chan.T.Text has been superseded by Chan.I.Messages and so is now
151		deprecated (smcv)
152
153		• GetPendingMessageContent is deprecated (wjt)
154
155		New stable API:
156
157		• fd.o #14003: Chan.T.ServerAuthentication and Chan.I.SASLAuthentication
158		provide interactive querying for credentials, allowing connection without
159		saving a password if there is a handler for these channels (eeejay, smcv,
160		jonny)
161
162		• Chan.I.Securable indicates whether a channel is secure (smcv, jonny)
163
164		• fd.o #28866: ChannelDispatcher and ChannelRequest now support
165		"request hints" (metadata passed through from the requester to the handler),
166		and the SucceededWithChannel signal (wjt, smcv)
167
168		• fd.o #20775: Protocol.I.Avatars indicates the expected requirements for
169		avatars (eeejay)
170		· no changes since draft 1
171
172		• message-sender-id key in Messages headers, complementing
173		message-sender (smcv)
174
175		• Messages.MessageTypes property, superseding GetMessageTypes (smcv)
176
177		• Contact_Info_Field_Flag_Overwritten_By_Nickname, indicating that this
178		field will be overwritten when we set the nickname (jonner)
179
180		• Account.I.Addressing stores user preferences for use of accounts for
181		non-primary protocols, such as using SIP for telephony (fledermaus)
182
183		• fd.o #29914: Conn.I.Powersaving allows connections to be placed in a
184		lower-power-consumption state when a portable device is not in active use
185		· no changes since draft 1
186
187		• new errors: Confused, ServerConfused (smcv)
188
189		Fixes and clarifications:
190
191		• fd.o #27183: mutual subscription is a job for servers or UIs, and should not
192		be enforced by CMs (smcv)
193
194		• MIME types produced by CMs must be lower-case; MIME types provided by
195		clients should be normalized to lower-case before comparison (mikhailz)
196
197		• Improve wording of requestability templates and add markup for
198		sometimes-requestable properties (wjt)
199
200		• fd.o #29560: clarify how Messages signals errors (smcv)
201
202		• fd.o #29474: adjust TargetHandleType and Chan.T.Text documentation to
203		reflect the Conference-based approach to MSN used since 0.20 (smcv)
204
205		• Delete unused code-generation tools and their tests, and various outdated
206		documents (smcv)
207
208		• Update test-specparser.py so it actually passes, and run it in
209		"make check" (smcv)
210
211		• fd.o #31661: editorial improvements (wjt)
212
213		Changes to experimental API:
214
215		• Hints and SucceededWithChannel moved to ChannelDispatcher.I.Hints and
216		ChannelRequest.I.Hints
217
218		• More Call changes (jonny, sjoerd, danni)
219		· make CodecOffer and Codec_Offering specific to one contact
220		· fd.o #28725: add InitialTransport
221		· fd.o #28690: add PleaseRestartICE and document ICE restarts
222		· fd.o #31279: add Unknown and Multicast transport types
223
224		telepathy-spec 0.21.4 (2010-10-29)
225		==================================
226
227		The "I had to take out doors, AI, the level boss and levels" release.
228
229		New stable API:
230
231		• add NewActiveTransportPair method to StreamHandler (lfrb)
232
233		Fixes:
234
235		• remove ".DRAFT" from MailNotification (smcv)
236
237		Changes to experimental API:
238
239		• clarify more of Call, and add a Content.Removed signal (jonny)
240
241		telepathy-spec 0.21.3 (2010-10-25)
242		==================================
243
244		The "I used a goto today, gleefully and intentionally" release.
245
246		New stable API:
247
248		• fd.o #27835: Conn.AddClientInterest, Conn.RemoveClientInterest allow
249		clients to subscribe to specialized interfaces in a generic way (smcv)
250
251		• fd.o #30703: Chan.I.DTMF.TonesDelayed and support for 'p', 'x', ',' and 'w'
252		in dialstrings (smcv)
253
254		• fd.o #13349: Conn.I.MailNotification is now considered stable. Changes
255		since draft 1:
256		· remove the Subscribe and Unsubscribe methods: you should call
257		AddClientInterest and RemoveClientInterest instead
258
259		• fd.o #30088: Protocol.I.Presence is now considered stable, with no
260		changes since draft 1
261
262		• a new error code, PickedUpElsewhere, used by Call (jonny)
263
264		Changes to experimental API:
265
266		• more changes to Call and its related interfaces (jonny)
267		· fd.o #28720: remove Early_Media disposition
268		· fd.o #28719: document Call.Stream.Endpoint
269		· fd.o #28735: document local state of Pending_Send
270		· fd.o #28704: add signals for relay info and STUN servers
271		· fd.o #29595: add Call.Stream.LocalSendingStateChanged
272		· fd.o #29596: split Call.Stream.Members into RemoteMembers and
273		LocalSendingState
274
275		Tools changes:
276
277		• <tp:xor-requires> allows interfaces to be shared between Call and StreamedMedia
278		(jonny)
279
280		telepathy-spec 0.21.2 (2010-10-15)
281		==================================
282
283		The "Ponderer of Witty Job Titles" release.
284
285		New stable API:
286
287		• Rejected error code for use with Call (jonny)
288
289		• StreamHandler now has StartNamedTelephonyEvent and StartSoundTelephonyEvent
290		signals (ocrete)
291
292		Clarifications:
293
294		• Chan.I.Messages' three capability-discovery properties
295		(DeliveryReportingSupport, MessagePartSupportFlags and SupportedContentTypes)
296		are now stated to be immutable (smcv)
297
298		New experimental API:
299
300		• fd.o #30512: Conn.I.Keepalive, an interface to vary keepalive intervals at
301		runtime (wjt)
302
303		• fd.o #30043: Handler.FUTURE.BypassObservers indicates that channels handled
304		by the given handler shouldn't cause observers to be invoked (ptlo)
305
306		Changes to experimental API:
307
308		• Numerous changes to Call and its related interfaces (jonny)
309
310		Tools changes:
311
312		• fd.o #30511: add markup for immutable properties, requestable channel
313		properties, and connection properties that are also parameters (jonny, wjt)
314
315		• Reject <tp:flag> values that are not a power of two, <tp:flags> that are
316		not uint32, and duplicate flag and enum values (jonny)
317
318		• Warn on unexpected XML elements and dangling cross-references to errors,
319		and optionally also on dangling cross-references to D-Bus interfaces (jonny)
320
321		telepathy-spec 0.21.1 (2010-09-29)
322		==================================
323
324		The "it's Wednesday, so this must be a spec release" release.
325
326		Changes to stable API:
327
328		• Account.RequestedPresence must not be Unset, Unknown or Error, while
329		Account.AutomaticPresence must not be any of those or Offline, matching
330		the behaviour that Mission Control has implemented in practice since
331		version 5.1.2 (smcv)
332
333		• Account.CurrentPresence now allows a non-empty status or message for
334		accounts that are offline or don't support SimplePresence (smcv)
335
336		New stable API:
337
338		• Conn.I.ClientTypes is now considered stable, with minor clarifications
339		since draft 1, and the 'game' and 'sms' client types removed pending
340		XMPP Registrar inclusion (jonny)
341
342		• The Access_Control_Type enum is a superset of
343		Rich_Presence_Access_Control_Type, which it will supersede in future
344		interfaces; similarly, Access_Control supersedes
345		Rich_Presence_Access_Control (eeejay)
346
347		New experimental API:
348
349		• Conn.I.CommunicationPolicy allows incoming channels from particular
350		contacts to be forbidden (eeejay)
351
352		• Conn.I.Resources allows connections with multiple resources or points of
353		presence, such as on XMPP and MSN, to be represented (jonny)
354
355		telepathy-spec 0.21.0 (2010-09-22)
356		==================================
357
358		The "canteen DoS" release.
359
360		New stable API:
361
362		• ContactList and ContactGroups are now considered stable, with some
363		clarifications to the wording, but no semantic changes since the drafts in
364		version 0.20.0. (smcv)
365
366		telepathy-spec 0.20.1 (2010-09-15)
367		==================================
368
369		The "I can't build there!" release.
370
371		Fixes:
372
373		• Correct the tp:name-for-bindings on ServerCertificate to be
374		Server_Certificate, leading to the intended names (server_certificate
375		rather than servercertificate, etc.) in generated bindings. (smcv)
376
377		telepathy-spec 0.20.0 (2010-09-14)
378		==================================
379
380		This is a new stable version of telepathy-spec, intended to serve as a
381		reference point for future work. There were no API changes since development
382		release 0.19.13; changes from the year of development since 0.18.0 are
383		summarized below.
384
385		The versions of libraries, connection managers and Mission Control recommended
386		for use with GNOME 2.32 (the upcoming telepathy-glib 0.12, telepathy-gabble 0.10
387		and Mission Control 5.6 stable branches) can be expected to support most of
388		the API from this spec release.
389
390		Semantic changes
391		----------------
392
393		• The timestamps used for "user action time", intended for focus-stealing
394		prevention, are no longer interpreted as seconds since 1970. Instead, they
395		should be interpreted as X-server time on X GUI platforms,
396		with two special values (0 and the maximum 64-bit signed integer) having
397		their own semantics.
	109	• The Messages interface is now mandatory for Text channels.
398	110
399	111	Enhancements to core API
400	112	------------------------
401	113
402		• Connection now has Status, Interfaces properties
403		• ConnectionManager now has Protocol objects with more information about
404		protocols (at the time of release, this is supported in telepathy-gabble
405		0.9.x but not in most other connection managers)
406		• Account.ChangingPresence indicates when changes are being attempted
407		• Account.Service indicates a specific service such as "google-talk"
408		• Account has extensible details of the last connection error
409		• Observers can have a Recover flag, which provides best-effort crash recovery
410		• ChannelDispatchOperation.HandleWithTime can pass through a timestamp for
411		focus-stealing prevention
412		• various new error codes
	114	• The Connection has a pair of new methods, AddClientInterest and
	115	RemoveClientInterest, to allow clients to subscribe to potentially
	116	bandwidth-costly interfaces (such as MailNotification) in a generic
	117	way.
	118
	119	• ChannelDispatcher and ChannelRequest now support "request hints"
	120	(metadata passed through from the requester to the handler), and the
	121	SucceededWithChannel signal.
413	122
414	123	New optional interfaces
415	124	-----------------------
416	125
417		• Account.I.Storage indicates which backend an account is stored in
418		• Conn.I.Anonymity, Chan.I.Anonymity — controlling caller-ID and similar
419		features
420		• Conn.I.Balance — machine-readable account balance, e.g. SkypeOut credit
421		• Conn.I.Cellular — extra information about cellular connections
422		• Conn.I.ContactInfo — information that contacts provide about themselves,
423		in a vCard-like format
424		• Conn.I.ServicePoint, Chan.I.ServicePoint — emergency contact points
425		• Chan.T.ServerTLSConnection — interactive approval of any problematic
426		TLS/SSL certificates
427		• Chan.T.ContactSearch — searching for contacts by name, address etc.
428		• Chan.I.Conference — multi-user text or media conferences
429		which can be made by merging or upgrading 1-1 channels
430		• Chan.I.SMS — SMS-specific extensions to Text channels (currently only
431		one property, indicating class 0 "flash" SMSs)
	126	• The ContactList and ContactGroups interfaces for
	127	connections are now considered stable, and a new ContactBlocking
	128	interface has been added. Between them, these interfaces replace
	129	ContactList channels.
	130
	131	• The Connection.Interface.ClientTypes,
	132	Connection.Interface.MailNotification,
	133	Connection.Interface.Powersaving, and Protocol.Interface.Presence
	134	interfaces are now considered stable.
	135
	136	• Chan.T.ServerAuthentication and Chan.I.SASLAuthentication provide
	137	interactive querying for credentials, allowing connection without
	138	saving a password if there is a handler for these channels
	139
	140	• Chan.I.Securable indicates whether a channel is secure
	141
	142	• Account.Interface.Addressing stores user preferences for use of
	143	accounts for non-primary protocols, such as using SIP for telephony.
432	144
433	145	Enhancements to optional interfaces
434	146	-----------------------------------
435	147
436		• chat states are state-recoverable
437		• a new flag indicates whether Location can be set
	148	• Add a FileTransfer.URI property which can be used to tell other
	149	Telepathy clients about the location of the transferred
	150	file.
438	151
439		Changes since 0.19.13
	152	Changes since 0.21.13
440	153	---------------------
441	154
442		• improve wording of experimental Conn.I.ClientTypes and Conn.I.PowerSaving
443		interfaces (danni, wjt)
	155	• A server-message key for the Details dictionary in the ConnectionError
	156	signal has been defined. (wjt)

-2

README less more

89	89	Stable branches are available from branches with names like
90	90	'telepathy-spec-0.16' in the same repository.
91	91
92		Proposed patches awaiting review can usually be found in Merge Monkey:
93		<http://monkey.collabora.co.uk/>
	92	Proposed patches awaiting review can usually be found in the freedesktop.org
	93	bugzilla with the ‘patch’ keyword, which can be listed using the following
	94	formidible URL:
	95	<https://bugs.freedesktop.org/buglist.cgi?keywords=patch&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=tp-spec&product=Telepathy>

-1

doc/templates/index.html less more

1	1	<!DOCTYPE html PUBLIC "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" "">
2	2	<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
3	3	<head>
4		<title>$spec.title &mdash v$spec.version</title>
	4	<title>$spec.title — v$spec.version</title>
5	5	<link rel="stylesheet" href="style.css" type="text/css"/>
6	6	</head>
7	7	<body>

-1

doc/templates/interface.html less more

439	439	<div class="annotation connection-parameter">
440	440	<p><span class='note'>Note:</span> Connections implementing this
441	441	property SHOULD provide a corresponding parameter named
442		<tt>$interface.name</tt> with the <a
	442	<tt>$property.name</tt> with the <a
443	443	href="Connection_Manager.html#Conn_Mgr_Param_Flags">DBus_Property</a>
444	444	flag. Clients SHOULD update this property by
445	445	calling <a

-1

doc/templates/interfaces.html less more

1	1	<!DOCTYPE html PUBLIC "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" "">
2	2	<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
3	3	<head>
4		<title>$spec.title &mdash v$spec.version</title>
	4	<title>$spec.title — v$spec.version</title>
5	5	<link rel="stylesheet" href="style.css" type="text/css"/>
6	6	</head>
7	7	<body>

+20

-0

doc/templates/style.css less more

326	326	pre {
327	327	margin: 0.5em 0 0 0;
328	328	}
	329
	330	.docstring table {
	331	border: 1px solid #d3d7cf;
	332	background-color: #eeeeec;
	333	margin: 0.5em 0 0 0;
	334	border-collapse: collapse;
	335	}
	336
	337	.docstring th,
	338	.docstring td {
	339	padding: 4px;
	340	}
	341
	342	.docstring th {
	343	border-bottom: 1px dotted #d3d7cf;
	344	}
	345
	346	.docstring tr:nth-child(even) {
	347	background-color: #dddddc;
	348	}

+12

-6

spec/Account_Interface_External_Password_Storage.xml less more

26	26
27	27	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
28	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>
	29	SHOULD NOT be stored by either the
	30	<tp:dbus-ref namespace="ofdT">AccountManager</tp:dbus-ref> nor any
	31	<tp:dbus-ref namespace="ofdT.Channel.Type">ServerAuthentication</tp:dbus-ref>
33	32	handler.</p>
	33
	34	<p>This interface SHOULD only appear on accounts for which the
	35	related Connection Manager implements
	36	<tp:dbus-ref namespace="ofdT">ConnectionManager.Interface.AccountStorage.DRAFT</tp:dbus-ref>.</p>
34	37	</tp:docstring>
35	38
36	39	<method name="ForgetPassword" tp:name-for-bindings="Forget_Password">
37	40	<tp:docstring>
38		<p>Clears any saved password associated with this account.</p>
	41	Clears any saved password associated with this account.
39	42	</tp:docstring>
40	43	</method>
41	44
42	45	<property name="PasswordSaved"
43	46	tp:name-for-bindings="Password_Saved"
44	47	type="b" access="read">
45		<tp:docstring>
	48	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
46	49	<p>Indicates whether the account has a saved password or not.</p>
	50
	51	<p>Change notification for this property is provided by the
	52	standard D-Bus <code>PropertiesChanged</code> signal.</p>
47	53	</tp:docstring>
48	54	</property>
49	55

+135

-12

spec/Channel_Dispatcher.xml less more

167	167	<tp:possible-errors>
168	168	<tp:error name="org.freedesktop.Telepathy.Error.InvalidArgument">
169	169	<tp:docstring>
170		The Preferred_Handler is syntactically invalid or does
	170	The <var>Preferred_Handler</var> is syntactically invalid or does
171	171	not start with <code>org.freedesktop.Telepathy.Client.</code>,
172		the Account does not exist, or one of the Requested_Properties
173		is invalid
	172	the <var>Account</var> does not exist, or one of the
	173	<var>Requested_Properties</var> is invalid
174	174	</tp:docstring>
175	175	</tp:error>
176	176	</tp:possible-errors>

239	239	<tp:possible-errors>
240	240	<tp:error name="org.freedesktop.Telepathy.Error.InvalidArgument">
241	241	<tp:docstring>
242		The Preferred_Handler is syntactically invalid or does
	242	The <var>Preferred_Handler</var> is syntactically invalid or does
243	243	not start with <code>org.freedesktop.Telepathy.Client.</code>,
244		the Account does not exist, or one of the Requested_Properties
245		is invalid
	244	the <var>Account</var> does not exist, or one of the
	245	<var>Requested_Properties</var> is invalid
246	246	</tp:docstring>
247	247	</tp:error>
248	248	</tp:possible-errors>

417	417	<tp:possible-errors>
418	418	<tp:error name="org.freedesktop.Telepathy.Error.InvalidArgument">
419	419	<tp:docstring>
420		The Preferred_Handler is syntactically invalid or does
	420	The <var>Preferred_Handler</var> is syntactically invalid or does
421	421	not start with <code>org.freedesktop.Telepathy.Client.</code>,
422		the Account does not exist, or one of the Requested_Properties
423		is invalid
	422	the <var>Account</var> does not exist, or one of the
	423	<var>Requested_Properties</var> is invalid
424	424	</tp:docstring>
425	425	</tp:error>
426	426	</tp:possible-errors>

558	558	<tp:possible-errors>
559	559	<tp:error name="org.freedesktop.Telepathy.Error.InvalidArgument">
560	560	<tp:docstring>
561		The Preferred_Handler is syntactically invalid or does
	561	The <var>Preferred_Handler</var> is syntactically invalid or does
562	562	not start with <code>org.freedesktop.Telepathy.Client.</code>,
563		the Account does not exist, or one of the Requested_Properties
564		is invalid
	563	the <var>Account</var> does not exist, or one of the
	564	<var>Requested_Properties</var> is invalid
565	565	</tp:docstring>
566	566	</tp:error>
567	567	</tp:possible-errors>
568	568
	569	</method>
	570
	571	<method name="DelegateChannels"
	572	tp:name-for-bindings="Delegate_Channels">
	573	<tp:added version="0.23.1" />
	574	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	575	<p>Called by a
	576	<tp:dbus-ref namespace="org.freedesktop.Telepathy.Client">Handler</tp:dbus-ref>
	577	to redispatch a bunch of channels it is currently handling.</p>
	578
	579	<p>If another
	580	<tp:dbus-ref namespace="org.freedesktop.Telepathy.Client">Handler</tp:dbus-ref>
	581	can be found,
	582	<tp:dbus-ref namespace="org.freedesktop.Telepathy.Client.Handler">HandleChannels</tp:dbus-ref>
	583	will be called on it and this function will succeed. In that case,
	584	the original <tp:dbus-ref namespace="org.freedesktop.Telepathy.Client">Handler</tp:dbus-ref>
	585	does not longer handle those channels.</p>
	586
	587	<p>If this method fails, the original
	588	<tp:dbus-ref namespace="org.freedesktop.Telepathy.Client">Handler</tp:dbus-ref>
	589	is still handling the channels.</p>
	590
	591	</tp:docstring>
	592
	593	<arg direction="in" name="Channels" type="ao">
	594	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	595	<p>The list of channels to redispatch. The caller has to be the current
	596	<tp:dbus-ref namespace="org.freedesktop.Telepathy.Client">Handler</tp:dbus-ref>
	597	of all of these channels
	598	</p>
	599	</tp:docstring>
	600	</arg>
	601
	602	<arg direction="in" name="User_Action_Time" type="x"
	603	tp:type="User_Action_Timestamp">
	604	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	605	<p>The time at which user action occurred, or 0 if this channels
	606	delegation is for some reason not involving user action.</p>
	607
	608	<p>This parameter is used in the same way as the corresponding
	609	parameter to
	610	<tp:member-ref>CreateChannelWithHints</tp:member-ref>.</p>
	611	</tp:docstring>
	612	</arg>
	613
	614	<arg direction="in" name="Preferred_Handler" type="s"
	615	tp:type="DBus_Well_Known_Name">
	616	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	617	<p>Either the well-known bus name (starting with
	618	<code>org.freedesktop.Telepathy.Client.</code>)
	619	of the preferred new handler for these
	620	channels, or an empty string to indicate that any handler would be
	621	acceptable. The behaviour and rationale are the same as for the
	622	corresponding parameter to
	623	<tp:member-ref>CreateChannelWithHints</tp:member-ref>.</p>
	624
	625	</tp:docstring>
	626	</arg>
	627
	628	<tp:possible-errors>
	629	<tp:error name="org.freedesktop.Telepathy.Error.InvalidArgument">
	630	<tp:docstring>
	631	The Preferred_Handler is syntactically invalid or does
	632	not start with <code>org.freedesktop.Telepathy.Client.</code> or
	633	the Account does not exist.
	634	</tp:docstring>
	635	</tp:error>
	636
	637	<tp:error name="org.freedesktop.Telepathy.Error.NotYours">
	638	<tp:docstring>
	639	The caller is not currently handling the channels.
	640	</tp:docstring>
	641	</tp:error>
	642
	643	<tp:error name="org.freedesktop.Telepathy.Error.NotCapable">
	644	<tp:docstring>
	645	There is no other suitable Handler.
	646	</tp:docstring>
	647	</tp:error>
	648	</tp:possible-errors>
	649
	650	</method>
	651
	652	<method name="PresentChannel"
	653	tp:name-for-bindings="Present_Channel">
	654	<tp:added version="0.23.1" />
	655	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	656	<p>Equivalent of calling
	657	<tp:dbus-ref namespace="org.freedesktop.Telepathy.ChannelDispatcher">EnsureChannel</tp:dbus-ref>
	658	with a <var>Requested_Properties</var> which would result in ensuring
	659	<var>Channel</var>.</p>
	660
	661	<p>If <var>Channel</var> is handled, its handler will be asked to present it the user
	662	(e.g. bring it into the foreground).</p>
	663	</tp:docstring>
	664
	665	<arg direction="in" name="Channel" type="o">
	666	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	667	<p>The channel to present.</p>
	668	</tp:docstring>
	669	</arg>
	670
	671	<arg direction="in" name="User_Action_Time" type="x"
	672	tp:type="User_Action_Timestamp">
	673	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	674	<p>The time at which user action occurred, or 0 if this channel
	675	request is for some reason not involving user action.</p>
	676
	677	<p>This parameter is used in the same way as the corresponding
	678	parameter to
	679	<tp:member-ref>EnsureChannelWithHints</tp:member-ref>.</p>
	680	</tp:docstring>
	681	</arg>
	682
	683	<tp:possible-errors>
	684	<tp:error name="org.freedesktop.Telepathy.Error.InvalidArgument">
	685	<tp:docstring>
	686	The Account does not exist, the Channel does not exist or it
	687	does not belong to the Account.
	688	</tp:docstring>
	689	</tp:error>
	690
	691	</tp:possible-errors>
569	692	</method>
570	693
571	694	<property name="SupportsRequestHints"

+108

-0

spec/Channel_Interface_SMS.xml less more

58	58	namespace='ofdT.Client.Handler'>BypassApproval</tp:dbus-ref> property
59	59	to <code>True</code>, so that it is invoked immediately for new
60	60	channels.</p>
	61
	62	<h4>Contact Capabilities</h4>
	63
	64	<p>Contacts to whom SMSes can be sent SHOULD indicate this via a
	65	requestable channel class with
	66	<tp:member-ref>SMSChannel</tp:member-ref> = True as a fixed
	67	property.</p>
	68
	69	<p>For instance, a contact that can accept both text and SMS channels:</p>
	70
	71	<blockquote><code>
	72	[<br/>
	73	({ ...<tp:dbus-ref namespace='ofdT.Channel'>ChannelType</tp:dbus-ref>:
	74	...<tp:dbus-ref namespace='ofdT.Channel.Type'>Text</tp:dbus-ref>,<br/>
	75	...<tp:dbus-ref namespace='ofdT.Channel'>TargetHandleType</tp:dbus-ref>:
	76	<tp:type>Handle_Type</tp:type>_Contact,<br/>
	77	},<br/>
	78	[ ...<tp:dbus-ref namespace='ofdT.Channel'>TargetHandle</tp:dbus-ref>,
	79	...<tp:dbus-ref namespace='ofdT.Channel'>TargetID</tp:dbus-ref> ]),<br/>
	80	<br/>
	81	({ ...<tp:dbus-ref namespace='ofdT.Channel'>ChannelType</tp:dbus-ref>:
	82	...<tp:dbus-ref namespace='ofdT.Channel.Type'>Text</tp:dbus-ref>,<br/>
	83	...<tp:dbus-ref namespace='ofdT.Channel'>TargetHandleType</tp:dbus-ref>:
	84	<tp:type>Handle_Type</tp:type>_Contact,<br/>
	85	...<tp:member-ref>SMSChannel</tp:member-ref>: True,<br/>
	86	},<br/>
	87	[ ...<tp:dbus-ref namespace='ofdT.Channel'>TargetHandle</tp:dbus-ref>,
	88	...<tp:dbus-ref namespace='ofdT.Channel'>TargetID</tp:dbus-ref> ]),<br/>
	89	]
	90	</code></blockquote>
61	91	</tp:docstring>
62	92
63	93	<property name="Flash" tp:name-for-bindings="Flash"

174	204	<tp:member-ref>SMSChannel</tp:member-ref> property.
175	205	</tp:docstring>
176	206	</signal>
	207
	208	<method name="GetSMSLength"
	209	tp:name-for-bindings="Get_SMS_Length">
	210	<tp:added version="0.23.1"/>
	211
	212	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	213	<p>Returns the number of 140 octet chunks required to send a message
	214	via SMS, as well as the number of remaining characters available in
	215	the final chunk and, if possible, an estimate of the cost.</p>
	216
	217	<tp:rationale>
	218	<p>There are a number of different SMS encoding mechanisms, and the
	219	client doesn't know which mechanisms an individual CM might support.
	220	This method allows the client, without any knowledge of the
	221	encoding mechanism, to provide length details to the user.</p>
	222	</tp:rationale>
	223
	224	<p>Clients SHOULD limit the frequency with which this method is called
	225	and SHOULD NOT call it for every keystroke. Clients MAY estimate the
	226	remaining size between single keystrokes.</p>
	227	</tp:docstring>
	228
	229	<arg name="Message" type="aa{sv}" tp:type="Message_Part[]" direction="in">
	230	<tp:docstring>
	231	The message the user wishes to send.
	232	</tp:docstring>
	233	</arg>
	234
	235	<arg name="Chunks_Required" type="u" direction="out">
	236	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	237	<p>The number of 140 octet chunks required to send this message.</p>
	238
	239	<p>For example, in the GSM standard 7-bit encoding, a 162 character
	240	message would require 2 chunks.</p>
	241	</tp:docstring>
	242	</arg>
	243
	244	<arg name="Remaining_Characters" type="i" direction="out">
	245	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	246	<p>The number of further characters that can be fit in the final
	247	chunk. A negative value indicates that the message will be
	248	truncated by <code>abs(Remaining_Characters)</code>. The value
	249	<code>MIN_INT32</code> (<code>-2<sup>31</sup></code>)
	250	indicates the message will be truncated by an unknown amount.</p>
	251
	252	<p>For example, in the GSM standard 7-bit encoding, a 162 character
	253	message would return 144 remaining characters (because of the
	254	space required for the multipart SMS header).</p>
	255	</tp:docstring>
	256	</arg>
	257
	258	<arg name="Estimated_Cost" type="i" direction="out">
	259	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	260	<p>The estimated cost of sending this message. The currency and
	261	scale of this value are the same as the
	262	<tp:dbus-ref namespace="ofdT.Connection.Interface">Balance.AccountBalance</tp:dbus-ref>
	263	property.</p>
	264
	265	<p>A value of <code>-1</code> indicates the cost could not be
	266	estimated.</p>
	267
	268	</tp:docstring>
	269	</arg>
	270
	271	<tp:possible-errors>
	272	<tp:error name="org.freedesktop.Telepathy.Error.NotImplemented">
	273	<tp:docstring>
	274	Raised when the method is not available on this channel.
	275	Clients MAY choose to make their own estimation.
	276	</tp:docstring>
	277	</tp:error>
	278	<tp:error name="org.freedesktop.Telepathy.Error.InvalidArgument">
	279	<tp:docstring>
	280	Raised when the content cannot be encoded into a valid SMS.
	281	</tp:docstring>
	282	</tp:error>
	283	</tp:possible-errors>
	284	</method>
177	285	</interface>
178	286	</node>

-0

spec/Channel_Type_Call.xml less more

835	835	normally be localized or suitable for display to users, and is only
836	836	applicable when the call state is
837	837	<tp:type>Call_State</tp:type>_Ended.</dd>
	838
	839	<dt>balance-required - i</dt>
	840	<dd>Optionally included when a call cannot be connected because
	841	there is <tp:error-ref>InsufficientBalance</tp:error-ref>,
	842	indicating what the required balance would be to place this call.
	843	The value of this key has the same units and scale as
	844	<tp:dbus-ref namespace="ofdT.Connection.Interface.Balance">AccountBalance</tp:dbus-ref>.
	845	</dd>
838	846	</dl>
839	847	</tp:docstring>
840	848	</property>

+21

-2

spec/Channel_Type_Contact_Search.xml less more

30	30	<p>A channel type for searching server-stored user directories. A new
31	31	channel should be requested by a client for each search attempt, and
32	32	closed when the search is completed or the required result has been
33		found. Channels of this type should have <tp:dbus-ref
	33	found.</p>
	34
	35	<p>Connections that support contact search channels SHOULD have an entry
	36	in <tp:dbus-ref namespace='ofdT.Connection.Interface.Requests'
	37	>RequestableChannelClasses</tp:dbus-ref> with the <tp:dbus-ref
	38	namespace='ofdT.Channel'>ChannelType</tp:dbus-ref> fixed to this
	39	interface, and no other fixed properties. That requestable
	40	channel class MAY also have the Server and Limit properties in its
	41	list of allowed properties, depending on the protocol.</p>
	42
	43	<tp:rationale>
	44	<p>The requestable channel class would normally also have <tp:dbus-ref
	45	namespace='ofdT.Channel'>TargetHandleType</tp:dbus-ref> fixed to
	46	<code>None</code>, but the initial implementation of ContactSearch
	47	(in telepathy-gabble) didn't do this.</p>
	48	</tp:rationale>
	49
	50	<p>All channels of this type should have <tp:dbus-ref
34	51	namespace='ofdT.Channel'>TargetHandleType</tp:dbus-ref>
35	52	<code>None</code> (and hence <tp:dbus-ref
36	53	namespace='ofdT.Channel'>TargetHandle</tp:dbus-ref> <code>0</code> and
37	54	<tp:dbus-ref namespace='ofdT.Channel'>TargetID</tp:dbus-ref>
38		<code>""</code>). Requests for channels of this type need only
	55	<code>""</code>).</p>
	56
	57	<p>Requests for channels of this type need only
39	58	optionally specify the <tp:member-ref>Server</tp:member-ref> property
40	59	(if it is an allowed property in the connection's <tp:dbus-ref
41	60	namespace='ofdT.Connection.Interface.Requests'>RequestableChannelClasses</tp:dbus-ref>).</p>

+54

-6

spec/Channel_Type_Server_TLS_Connection.xml less more

43	43	</tp:docstring>
44	44
45	45	<property name="ServerCertificate" type="o" access="read"
46		tp:name-for-bindings="Server_Certificate">
	46	tp:name-for-bindings="Server_Certificate"
	47	tp:immutable='yeah'>
47	48	<tp:docstring>
48	49	<p>A <tp:dbus-ref
49	50	namespace="org.freedesktop.Telepathy.Authentication">TLSCertificate</tp:dbus-ref>
50	51	containing the certificate chain as sent by the server,
51	52	and other relevant information.</p>
52		<p>This property is immutable.</p>
53	53	</tp:docstring>
54	54	</property>
55	55
56	56	<property name="Hostname" type="s" access="read"
57		tp:name-for-bindings="Hostname">
	57	tp:name-for-bindings="Hostname"
	58	tp:immutable='sharks'>
58	59	<tp:added version="0.19.12"/>
59	60	<tp:docstring>
60		The hostname of the server we expect <tp:member-ref>ServerCertificate</tp:member-ref>
61		to certify; clients SHOULD verify <tp:member-ref>ServerCertificate</tp:member-ref> against
62		this hostname when checking its validity.
	61	<p>The hostname or domain that the user expects to connect to. Clients
	62	SHOULD use the <tp:member-ref>ReferenceIdentities</tp:member-ref>
	63	property to verify the identity of the certificate. Clients MAY display
	64	this hostname to the user as the expected identity. Clients SHOULD use
	65	this property to lookup pinned certificates or other user preferences
	66	for the connection.</p>
	67	</tp:docstring>
	68	</property>
	69
	70	<property name="ReferenceIdentities" type="as" access="read"
	71	tp:name-for-bindings="Reference_Identities"
	72	tp:immutable='plz'>
	73	<tp:added version="0.21.10">
	74	If this property is not present, clients SHOULD use the
	75	<tp:member-ref>Hostname</tp:member-ref> property as the reference
	76	identity to validate server certificates against.
	77	</tp:added>
	78
	79	<tp:docstring>
	80	<p>The identities of the server we expect
	81	<tp:member-ref>ServerCertificate</tp:member-ref> to certify; clients
	82	SHOULD verify that <tp:member-ref>ServerCertificate</tp:member-ref>
	83	matches one of these identities when checking its validity.</p>
	84
	85	<p>This property MUST NOT be the empty list; it MUST
	86	contain the value of the <tp:member-ref>Hostname</tp:member-ref>
	87	property. All other identities included in this property MUST be derived from
	88	explicit user input or choices, such as <tp:dbus-ref
	89	namespace='ofdT.Account'>Parameters</tp:dbus-ref> passed to
	90	<tp:dbus-ref
	91	namespace='ofdT.ConnectionManager'>RequestConnection</tp:dbus-ref>.</p>
	92
	93	<tp:rationale>
	94	<p>The primary use for this property is for XMPP services hosted by
	95	<a href='http://www.google.com/apps/intl/en/business/gmail.html'>Google
	96	Apps</a>. When connecting to Google Talk using an
	97	<tt>@gmail.com</tt> JID, the server correctly presents a
	98	certificate for <tt>gmail.com</tt>; however, for domains hosted via
	99	Google Apps, a certificate for <tt>talk.google.com</tt> is
	100	offered, due to unresolved technical limitations.</p>
	101
	102	<p>If the user has explicitly chosen to create a <q>Google Talk</q>
	103	account, then trusting a certificate for <tt>talk.google.com</tt>
	104	is reasonable. To handle this case, the connection manager may add
	105	the values of any or all of the <tt>server</tt>,
	106	<tt>fallback-server</tt> and <tt>extra-identities</tt> parameters;
	107	the Google Talk account creation user interface may set these
	108	parameters appropriately, or the user may set them for accounts
	109	with other services.</p>
	110	</tp:rationale>
63	111	</tp:docstring>
64	112	</property>
65	113

-0

spec/Connection.xml less more

1032	1032	<dd>Debugging information on the change, corresponding to the
1033	1033	message part of a D-Bus error message, which SHOULD NOT be
1034	1034	displayed to users under normal circumstances</dd>
	1035
	1036	<dt>server-message (s)</dt>
	1037	<dd>A human-readable message from the server explaining what
	1038	happened. This may be in the user's native language, or in the
	1039	server operator's native language, or even in Lojban.</dd>
	1040
1035	1041	<dt>user-requested (b), expected-hostname (s), certificate-hostname (s)</dt>
1036	1042	<dd>The same details defined in <tp:type>TLS_Certificate_Rejection</tp:type>.</dd>
1037	1043	</dl>

+20

-0

spec/Connection_Interface_Balance.xml less more

92	92	</tp:docstring>
93	93	</property>
94	94
	95	<property name="ManageCreditURI"
	96	tp:name-for-bindings="Manage_Credit_URI"
	97	access="read" type="s">
	98	<tp:added version="0.22.2"/>
	99	<tp:docstring>
	100	A URI the user may visit via the web browser to manage and top-up their
	101	account balance. This property is not guaranteed to be well-defined
	102	until the connection becomes Connected; there is no change
	103	notification.
	104
	105	<tp:rationale>
	106	Different protocols and even servers or gateways (e.g. SIP and XMPP
	107	PSTN gateways) will have a different website used to manage a user's
	108	account balance. This property enables the client to provide that
	109	to the user. A Connection Manager MAY set this itself (because it is
	110	static or discoverable), or expose it as a connection parameter.
	111	</tp:rationale>
	112	</tp:docstring>
	113	</property>
	114
95	115	<signal name="BalanceChanged" tp:name-for-bindings="Balance_Changed">
96	116	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
97	117	<p>Emitted when the user's balance has changed.</p>

+33

-7

spec/Connection_Interface_Cellular.xml less more

116	116	type="b" access="readwrite"
117	117	tp:is-connection-parameter='no... just kidding! yes!'>
118	118	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
119		<p>Determines whether SMSes containing characters that do not fit into
120		a 7‐bit GSM character set should be sent as UCS‐2, or lossily
121		recoded. If <code>False</code> (which SHOULD be the default),
122		messages will be sent with no loss of fidelity (at the potential
123		financial cost of using twice as many SMSes); if <code>True</code>,
124		the message will be recoded in an implementation‐specific way to fit
125		into a country‐specific GSM reduced character set.</p>
	119	<p>Determines how to encode SMSes containing characters that do not
	120	fit into a non-Unicode character set.
	121	If <code>False</code> (which SHOULD be the default), messages will
	122	be encoded as UCS-2 and sent with no loss of fidelity (at the
	123	potential financial cost of using twice as many SMSes); if
	124	<code>True</code>, the message will be recoded in an
	125	implementation‐specific way to fit into a GSM reduced character
	126	set.</p>
	127	</tp:docstring>
	128	</property>
	129
	130	<property name="MessageNationalCharacterSet"
	131	tp:name-for-bindings="Message_National_Character_Set"
	132	type="s" access="readwrite"
	133	tp:is-connection-parameter='affirmative'>
	134	<tp:added version="0.21.12"/>
	135	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	136	<p>Hint for the connection manager for the GSM character set that
	137	should be used to send SMSes. The connection manager SHOULD follow
	138	this hint unless it has other ways to determine a better encoding.
	139	If the value is <code>"gsm"</code> (which SHOULD be the default),
	140	SMSes will be encoded in the normal 7-bit GSM character set,
	141	eventually falling back to UCS-2; see the
	142	<tp:member-ref>MessageReducedCharacterSet</tp:member-ref> property
	143	for details.
	144	Other valid character sets are specified in the
	145	<a href="http://www.3gpp.org/ftp/specs/archive/23_series/23.038/"
	146	>GSM standard</a> and are, for instance, <code>"turkey"</code>,
	147	<code>"spain"</code> or <code>"portugal"</code>.
	148	If the SMS cannot be encoded using the requested character set the
	149	behaviour is implementation-specific, but it is RECOMMENDED that
	150	the connection manager should behave as if this property was set
	151	to <code>"gsm"</code>.</p>
126	152	</tp:docstring>
127	153	</property>
128	154	</interface>

+207

-0

spec/Connection_Interface_Contact_Blocking.xml less more

	0	<?xml version="1.0" ?>
	1	<node name="/Connection_Interface_Contact_Blocking" xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
	2	<tp:copyright>Copyright © 2009–2011 Collabora Ltd.</tp:copyright>
	3	<tp:copyright>Copyright © 2009 Nokia Corporation</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,
	18	USA.</p>
	19	</tp:license>
	20	<interface name="org.freedesktop.Telepathy.Connection.Interface.ContactBlocking">
	21	<tp:requires interface="org.freedesktop.Telepathy.Connection"/>
	22	<tp:requires interface="org.freedesktop.Telepathy.Connection.Interface.ContactList"/>
	23	<tp:added version='0.21.13'>Changes from the draft:
	24	methods and signals now return <tp:type>Handle_Identifier_Map</tp:type>
	25	(<code>a{us}</code>) rather than bare lists of contact handles
	26	(<code>au</code>)</tp:added>
	27
	28	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	29	<p>An interface for connections where contacts can be blocked from
	30	communicating with this user and receiving this user's presence.
	31	Clients may retrieve a list of currently-blocked contacts using
	32	<tp:member-ref>RequestBlockedContacts</tp:member-ref>, and listen for
	33	<tp:member-ref>BlockedContactsChanged</tp:member-ref> to be notified
	34	when contacts are blocked and unblocked. The
	35	<tp:member-ref>BlockContacts</tp:member-ref> and
	36	<tp:member-ref>UnblockContacts</tp:member-ref> methods do what they say
	37	on the tin; depending on the value of the
	38	<tp:member-ref>ContactBlockingCapabilities</tp:member-ref> property,
	39	contacts may be reported for spam or other abuse when calling
	40	<tp:member-ref>BlockContacts</tp:member-ref>.</p>
	41
	42	<p>This interface is intended for protocols where blocking contacts
	43	persists on the server between connections; connection managers for
	44	protocols with no server-side support for blocking contacts MAY choose
	45	to implement this interface using an on-disk file of blocked
	46	contacts or some other means to store blocked contacts between
	47	connections.</p>
	48
	49	<p>This interface is intended to replace the
	50	<tp:dbus-ref namespace="ofdT.Channel.Type">ContactList</tp:dbus-ref>
	51	channel with <tp:dbus-ref
	52	namespace='ofdT.Channel'>TargetHandleType</tp:dbus-ref>
	53	<code>List</code> and <tp:dbus-ref
	54	namespace='ofdT.Channel'>TargetID</tp:dbus-ref> <code>"deny"</code>
	55	(along with the <tp:dbus-ref
	56	namespace='ofdT.Connection.Interface'>ContactList</tp:dbus-ref> and
	57	<tp:dbus-ref
	58	namespace='ofdT.Connection.Interface'>ContactGroups</tp:dbus-ref>
	59	interfaces replacing other channels with <tp:dbus-ref
	60	namespace='ofdT.Channel'>TargetHandleType</tp:dbus-ref>
	61	<code>List</code> and <tp:dbus-ref
	62	namespace='ofdT.Channel'>TargetHandleType</tp:dbus-ref>
	63	<code>Group</code>, respectively).</p>
	64	</tp:docstring>
	65
	66	<method name="BlockContacts" tp:name-for-bindings="Block_Contacts">
	67	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	68	<p>Direct the server to block some contacts. The precise effect is
	69	protocol-dependent, but SHOULD include ignoring all current and
	70	subsequent communications from the given contacts, avoiding sending
	71	presence to them in future, and if they were already receiving the
	72	local user's presence, behaving as if the local user went
	73	offline.</p>
	74	</tp:docstring>
	75
	76	<arg name="Contacts" type="au" direction="in" tp:type="Contact_Handle[]">
	77	<tp:docstring>Some contacts to block. If some of the contacts in this
	78	list are already blocked, the connection manager MUST act as if they
	79	were not specified in this list.</tp:docstring>
	80	</arg>
	81
	82	<arg name="Report_Abusive" type="b" direction="in">
	83	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	84	<p>In addition to blocking, report these contacts as abusive to the
	85	server administrators.</p>
	86
	87	<p>Clients can determine whether this capability is available by
	88	checking the
	89	<tp:member-ref>ContactBlockingCapabilities</tp:member-ref>
	90	property. If this argument is set to <code>True</code> by a client
	91	despite <tp:member-ref>ContactBlockingCapabilities</tp:member-ref>
	92	not containing the <code>Can_Report_Abusive</code> flag, the
	93	connection manager SHOULD act as if it were <code>False</code> and
	94	simply block the supplied contacts.</p>
	95
	96	<tp:rationale>
	97	<p>A correct user interface shouldn't get this far without knowing
	98	that reporting abusive contacts is not supported. If it does,
	99	then the user has expressed their intention to block these
	100	contacts. Returning an error would leave the UI with three
	101	options:</p>
	102
	103	<ul>
	104	<li>Ignore the error, leaving the contacts not actually blocked;</li>
	105	<li>Display an error to the user;</li>
	106	<li>Call this method again, passing <code>False</code> for this
	107	argument.</li>
	108	</ul>
	109
	110	<p>None of these seem preferable to the CM just ignoring this flag
	111	if it doesn't support it: that way, the contacts will be blocked,
	112	as the user requested, and UIs have fewer ways to mess up
	113	entirely.</p>
	114	</tp:rationale>
	115	</tp:docstring>
	116	</arg>
	117	</method>
	118
	119	<method name="UnblockContacts" tp:name-for-bindings="Unblock_Contacts">
	120	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	121	<p>Direct the server to unblock some contacts.</p>
	122	</tp:docstring>
	123
	124	<arg name="Contacts" type="au" direction="in" tp:type="Contact_Handle[]">
	125	<tp:docstring>Some contacts to unblock. If some of the contacts in this
	126	list are not currently blocked, the connection manager MUST act as if
	127	they were not specified in this list.</tp:docstring>
	128	</arg>
	129	</method>
	130
	131	<method name="RequestBlockedContacts"
	132	tp:name-for-bindings="Request_Blocked_Contacts">
	133	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	134	<p>List the contacts that are blocked.</p>
	135
	136	<p>Clients SHOULD allow a relatively long timeout for calls to this
	137	method, since on some protocols contact blocking is part of the
	138	contact list, which can take a significant time to retrieve.</p>
	139	</tp:docstring>
	140
	141	<arg name="Contacts" type="a{us}" direction="out"
	142	tp:type="Handle_Identifier_Map">
	143	<tp:docstring>The blocked contacts’ handles, together with their
	144	identifiers.</tp:docstring>
	145	</arg>
	146	</method>
	147
	148	<signal name="BlockedContactsChanged"
	149	tp:name-for-bindings="Blocked_Contacts_Changed">
	150	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	151	<p>Emitted when the list of blocked contacts is first retrieved
	152	(before returning from any pending calls to
	153	<tp:member-ref>RequestBlockedContacts</tp:member-ref>), and
	154	whenever the list of blocked contacts subsequently changes.</p>
	155	</tp:docstring>
	156
	157	<arg name="Blocked_Contacts" type="a{us}" tp:type="Handle_Identifier_Map">
	158	<tp:docstring>Contacts added to the result of
	159	<tp:member-ref>RequestBlockedContacts</tp:member-ref>.</tp:docstring>
	160	</arg>
	161
	162	<arg name="Unblocked_Contacts" type="a{us}"
	163	tp:type="Handle_Identifier_Map">
	164	<tp:docstring>Contacts removed from the result of
	165	<tp:member-ref>RequestBlockedContacts</tp:member-ref>.</tp:docstring>
	166	</arg>
	167	</signal>
	168
	169	<tp:contact-attribute name="blocked" type="b">
	170	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	171	<p><code>True</code> if the contact would be in the result of
	172	<tp:member-ref>RequestBlockedContacts</tp:member-ref>;
	173	<code>False</code> or omitted if the contact is not blocked, or if it
	174	is unknown whether the contact is blocked.</p>
	175	</tp:docstring>
	176	</tp:contact-attribute>
	177
	178	<property name="ContactBlockingCapabilities"
	179	tp:name-for-bindings="Contact_Blocking_Capabilities"
	180	tp:type="Contact_Blocking_Capabilities" type="u" access="read"
	181	tp:immutable="yes">
	182	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	183	<p>Additional capabilities for contact blocking; currently, this is
	184	limited to whether contacts may be reported as abusive.</p>
	185
	186	<p>Note that there is no capability for supporting blocking itself:
	187	the presence of this interface on a <tp:dbus-ref
	188	namespace='ofdT'>Connection</tp:dbus-ref> indicates that blocking
	189	contacts is supported.</p>
	190	</tp:docstring>
	191	</property>
	192
	193	<tp:flags name="Contact_Blocking_Capabilities" type="u"
	194	value-prefix="Contact_Blocking_Capability">
	195	<tp:flag suffix="Can_Report_Abusive" value="1">
	196	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	197	When calling <tp:member-ref>BlockContacts</tp:member-ref>, the
	198	contacts may be reporting as abusive to the server administrators by
	199	setting <var>Report_Abusive</var> to <code>True</code>.
	200	</tp:docstring>
	201	</tp:flag>
	202	</tp:flags>
	203
	204	</interface>
	205	</node>
	206	<!-- vim:set sw=2 sts=2 et ft=xml: -->

-1

spec/Connection_Interface_Location.xml less more

59	59
60	60	<!-- Potentially to be reinstated later:
61	61	http://bugs.freedesktop.org/show_bug.cgi?id=19585
62		<tp:enum name="Location_Accuracy_Level" type="i">
	62	<tp:enum name="Location_Accuracy_Level" type="u">
63	63	<tp:docstring>
64	64	A location accuracy level. This should be kept in sync with
65	65	GeoclueAccuracyLevel in the Geoclue project.

-1

spec/Connection_Interface_Requests.xml less more

485	485	<tp:dbus-ref>org.freedesktop.Telepathy.Channel.ChannelType</tp:dbus-ref>
486	486	and
487	487	<tp:dbus-ref>org.freedesktop.Telepathy.Channel.TargetHandleType</tp:dbus-ref>.
488		</p>
	488	(One exception is that <tp:dbus-ref namespace="ofdT.Channel.Type"
	489	>ContactSearch</tp:dbus-ref> channels do not have TargetHandleType
	490	<code>None</code> in their requestable channel classes, for
	491	historical reasons.)</p>
489	492	</tp:docstring>
490	493
491	494	<tp:member type="s" name="Key" tp:type="DBus_Qualified_Member">

+86

-25

spec/Connection_Interface_Simple_Presence.xml less more

275	275	</tp:docstring>
276	276	</property>
277	277
	278	<property name="MaximumStatusMessageLength"
	279	tp:name-for-bindings="Maximum_Status_Message_Length" access="read"
	280	type="u">
	281	<tp:added version="0.22.2"/>
	282	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	283	<p>The maximum length in characters for any individual status
	284	message, or 0 if there is no limit.</p>
	285
	286	<p>While the connection is in the DISCONNECTED state, this property will
	287	be 0. The connection manager will attempt to set the appropriate value
	288	when the connection becomes connected, but cannot necessarily
	289	guarantee it. The maximum length cannot change until the
	290	connection status changes, so there is no change notification.</p>
	291
	292	<p>While the connection is in the CONNECTED state, this property
	293	contains the maximum length in characters for any individual status
	294	message which is actually allowed on this protocol.
	295	This value is constant for the remaining lifetime
	296	of the connection, so again, there is no change notification.</p>
	297
	298	<p>While the connection is in the CONNECTING state, the value of
	299	this property is undefined and SHOULD NOT be used. It can change
	300	at any time without notification (in particular, any cached values
	301	from when the connection was in the DISCONNECTED or CONNECTING
	302	state MUST NOT be assumed to still be correct when the state has
	303	become CONNECTED).</p>
	304
	305	<p>If a message passed to <tp:member-ref>SetPresence</tp:member-ref> is
	306	longer than allowed by this property, the connection manager MUST
	307	truncate the supplied message; when emitting
	308	<tp:member-ref>PresencesChanged</tp:member-ref>, the truncated version
	309	of the message MUST be used.</p>
	310
	311	<tp:rationale>
	312	<p>Some XMPP servers, like Google Talk, define a maximum length for
	313	status messages. Whether the user's server is one of
	314	these cannot be detected until quite late in the connection
	315	process.</p>
	316	</tp:rationale>
	317
	318	</tp:docstring>
	319	</property>
	320
278	321	<signal name="PresencesChanged" tp:name-for-bindings="Presences_Changed">
279	322	<arg name="Presence" type="a{u(uss)}" tp:type="Simple_Contact_Presences">
280	323	<tp:docstring>

546	589
547	590	<table>
548	591	<tr>
549		<th>status identifier</th>
550		<th>Connection_Presence_Type</th>
551		<th>comments</th>
552		</tr>
553		<tr>
554		<td>available</td>
555		<td>Connection_Presence_Type_Available</td>
	592	<th>Status identifier</th>
	593	<th><tp:type>Connection_Presence_Type</tp:type></th>
	594	<th>Remarks</th>
	595	</tr>
	596	<tr>
	597	<td><code>"available"</code></td>
	598	<td>Available</td>
556	599	<td></td>
557	600	</tr>
558	601	<tr>
559		<td>away</td>
560		<td>Connection_Presence_Type_Away</td>
	602	<td><code>"chat"</code></td>
	603	<td>Available</td>
	604	<td>Actively interested in chatting, as opposed to merely
	605	available.</td>
	606	</tr>
	607	<tr>
	608	<td><code>"pstn"</code></td>
	609	<td>Available</td>
	610	<td>This contact is actually a phone number, not an IM account. As
	611	such, the contact is conceptually always available, but not in the
	612	same way that a contact can set their IM status to “available”.
	613	It does not make sense to allow the user to set this status on
	614	herself; hence, on protocols where this status is supported, its
	615	entry in <tp:member-ref>Statuses</tp:member-ref> SHOULD have
	616	<var>May_Set_On_Self</var> set to <code>False</code>.</td>
	617	</tr>
	618	<tr>
	619	<td><code>"away"</code></td>
	620	<td>Away</td>
561	621	<td></td>
562	622	</tr>
563	623	<tr>
564		<td>brb</td>
565		<td>Connection_Presence_Type_Away</td>
	624	<td><code>"brb"</code></td>
	625	<td>Away</td>
566	626	<td>Be Right Back (a more specific form of Away)</td>
567	627	</tr>
568	628	<tr>
569		<td>busy</td>
570		<td>Connection_Presence_Type_Busy</td>
	629	<td><code>"busy"</code></td>
	630	<td>Busy</td>
571	631	<td></td>
572	632	</tr>
573		<tr><td>dnd</td>
574		<td>Connection_Presence_Type_Busy</td>
	633	<tr>
	634	<td><code>"dnd"</code></td>
	635	<td>Busy</td>
575	636	<td>Do Not Disturb (a more specific form of Busy)</td>
576	637	</tr>
577	638	<tr>
578		<td>xa</td>
579		<td>Connection_Presence_Type_Extended_Away</td>
	639	<td><code>"xa"</code></td>
	640	<td>Extended_Away</td>
580	641	<td>Extended Away</td>
581	642	</tr>
582	643	<tr>
583		<td>hidden</td>
584		<td>Connection_Presence_Type_Hidden</td>
	644	<td><code>"hidden"</code></td>
	645	<td>Hidden</td>
585	646	<td>Also known as "Invisible" or "Appear Offline"</td>
586	647	</tr>
587	648	<tr>
588		<td>offline</td>
589		<td>Connection_Presence_Type_Offline</td>
	649	<td><code>"offline"</code></td>
	650	<td>Offline</td>
590	651	<td></td>
591	652	</tr>
592	653	<tr>
593		<td>unknown</td>
594		<td>Connection_Presence_Type_Unknown</td>
	654	<td><code>"unknown"</code></td>
	655	<td>Unknown</td>
595	656	<td>special, see below</td>
596	657	</tr>
597	658	<tr>
598		<td>error</td>
599		<td>Connection_Presence_Type_Error</td>
	659	<td><code>"error"</code></td>
	660	<td>Error</td>
600	661	<td>special, see below</td>
601	662	</tr>
602	663	</table>

+17

-5

spec/Connection_Manager.xml less more

195	195	</tp:docstring>
196	196	</arg>
197	197	<tp:docstring>
198		Get a list of the parameters which must or may be provided to the
199		<tp:member-ref>RequestConnection</tp:member-ref> method when connecting
200		to the given protocol,
201		or registering (the boolean "register" parameter is available,
202		and set to true).
	198	Get a list of the parameters which may be specified in the
	199	<tp:dbus-ref namespace='ofdT.Account'>Parameters</tp:dbus-ref> of an
	200	<tp:dbus-ref namespace='ofdT'>Account</tp:dbus-ref> (or, for
	201	specialised applications which do not use the account manager, passed
	202	to <tp:member-ref>RequestConnection</tp:member-ref>). Some parameters
	203	are mandatory, and some parameters only make sense when registering new
	204	accounts with the server; see the <tp:type>Param_Spec</tp:type>
	205	documentation for more details.
203	206	</tp:docstring>
204	207	<tp:possible-errors>
205	208	<tp:error name="org.freedesktop.Telepathy.Error.NotImplemented">

321	324	with the
322	325	<tp:dbus-ref namespace="org.freedesktop.Telepathy.Connection">Connect</tp:dbus-ref>
323	326	method.</p>
	327
	328	<p><strong>Most applications should not use this method</strong>: they
	329	should instead use the the <tp:dbus-ref
	330	namespace='ofdT.Account'>Connection</tp:dbus-ref> property on an
	331	<tp:dbus-ref namespace='ofdT'>Account</tp:dbus-ref> object obtained
	332	from the <tp:dbus-ref
	333	namespace='ofdT'>AccountManager</tp:dbus-ref>. This method is used
	334	internally by the account manager to create connections when
	335	needed.</p>
324	336
325	337	<p>The parameters which must and may be provided in the parameters
326	338	dictionary can be discovered with the

+16

-13

spec/Connection_Manager_Interface_Account_Storage.xml less more

28	28	<p>An interface for connection managers that store account details
29	29	internally. At the moment this consists only of storing an account's
30	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
	31
	32	<p><tp:dbus-ref namespace="ofdT">Account</tp:dbus-ref> objects
33	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>
	34	interface should implement the
	35	<tp:dbus-ref namespace="ofdT.Account.Interface">ExternalPasswordStorage.DRAFT</tp:dbus-ref>
36	36	interface.</p>
37
38	37	</tp:docstring>
39	38
40	39	<tp:flags name="Account_Flags" value-prefix="Account_Flag" type="u">
41	40	<tp:docstring>
42		A set of flags representing the status of the Account stored in the Connection Manager.
	41	A set of flags representing the status of the Account stored in the
	42	Connection Manager.
43	43	</tp:docstring>
44	44
45	45	<tp:flag suffix="Credentials_Stored" value="1">

60	60	<property name="Accounts"
61	61	tp:name-for-bindings="Accounts"
62	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.
	63	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	64	<p>The set of Accounts stored in this Connection Manager, and flags
	65	indicating their status.</p>
	66
	67	<p>Change notification for this property is provided by the standard
	68	D-Bus <code>PropertiesChanged</code> signal.</p>
66	69	</tp:docstring>
67	70	</property>
68	71

75	78	<arg direction="in" name="Account_Id"
76	79	type="s">
77	80	<tp:docstring>
78		An account id as returned from <tp:dbus-ref
79		namespace="org.freedesktop.Telepathy">Protocol.IdentifyAccount</tp:dbus-ref>.
	81	An account id as returned from
	82	<tp:dbus-ref namespace="ofdT">Protocol.IdentifyAccount</tp:dbus-ref>.
80	83	</tp:docstring>
81	84	</arg>
82	85

98	101	<arg direction="in" name="Account_Id"
99	102	type="s">
100	103	<tp:docstring>
101		An account id as returned from <tp:dbus-ref
102		namespace="org.freedesktop.Telepathy">Protocol.IdentifyAccount</tp:dbus-ref>.
	104	An account id as returned from
	105	<tp:dbus-ref namespace="ofdT">Protocol.IdentifyAccount</tp:dbus-ref>.
103	106	</tp:docstring>
104	107	</arg>
105	108

+181

-11

spec/Media_Stream_Handler.xml less more

18	18	Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</p>
19	19	</tp:license>
20	20	<interface name="org.freedesktop.Telepathy.Media.StreamHandler">
	21
	22	<tp:docstring>
	23	Handles signalling the information pertaining to a specific media stream.
	24	A client should provide information to this handler as and when it is
	25	available.
	26	</tp:docstring>
21	27
22	28	<tp:struct name="Media_Stream_Handler_Candidate"
23	29	array-name="Media_Stream_Handler_Candidate_List">

532	538	<tp:docstring>
533	539	Signal emitted when the connection manager wishes to inform the
534	540	client of the codecs supported by the remote end.
535		If these codecs are compatible with the remote codecs, then the client
	541	If these codecs are compatible with the remote codecs, then the client
536	542	must call <tp:member-ref>SupportedCodecs</tp:member-ref>,
537	543	otherwise call <tp:member-ref>Error</tp:member-ref>.
538	544	</tp:docstring>

580	586	<arg name="Codec_ID" type="u">
581	587	<tp:docstring>
582	588	The payload type to use when sending events. The value 0xFFFFFFFF
583		means to send with the already configured event type instead of using
584		the specified one.
	589	means to send with the already configured event type instead of using
	590	the specified one.
585	591	</tp:docstring>
586	592	</arg>
587	593	<tp:docstring>
588	594	Request that a telephony event (as defined by RFC 4733) is transmitted
589	595	over this stream until StopTelephonyEvent is called. This differs from
590	596	StartTelephonyEvent in that you force the event to be transmitted
591		as a RFC 4733 named event, not as sound. You can also force a specific
592		Codec ID.
	597	as a RFC 4733 named event, not as sound. You can also force a specific
	598	Codec ID.
593	599	</tp:docstring>
594	600	</signal>
595	601	<signal name="StartSoundTelephonyEvent"

604	610	Request that a telephony event (as defined by RFC 4733) is transmitted
605	611	over this stream until StopTelephonyEvent is called. This differs from
606	612	StartTelephonyEvent in that you force the event to be transmitted
607		as sound instead of as a named event.
	613	as sound instead of as a named event.
608	614	</tp:docstring>
609	615	</signal>
610	616	<signal name="StopTelephonyEvent"

714	720	<tp:added version="0.17.3"/>
715	721	</method>
716	722
717		<tp:docstring>
718		Handles signalling the information pertaining to a specific media stream.
719		A client should provide information to this handler as and when it is
720		available.
721		</tp:docstring>
	723	<tp:struct name="RTCP_Feedback_Message_Properties">
	724	<tp:added version="0.22.1"/>
	725	<tp:member type="u" name="RTCPMinimumInterval">
	726	<tp:docstring>
	727	The minimum interval between two regular RTCP packets in
	728	milliseconds for this content. If no special value is desired, one
	729	should put MAXUINT (0xFFFFFFFF).
	730	</tp:docstring>
	731	</tp:member>
	732	<tp:member type="a(sss)" tp:type="RTCP_Feedback_Message[]"
	733	name="Messages">
	734	<tp:docstring>
	735	The RTCP feedback messages for this codec.
	736	</tp:docstring>
	737	</tp:member>
	738	</tp:struct>
	739
	740	<tp:struct name="RTCP_Feedback_Message"
	741	array-name="RTCP_Feedback_Message_List">
	742	<tp:added version="0.22.1"/>
	743	<tp:docstring>
	744	A struct defining an RTCP feedback message.
	745	</tp:docstring>
	746	<tp:member type="s" name="Type">
	747	<tp:docstring>
	748	Feedback type, for example "ack", "nack", or "ccm".
	749	</tp:docstring>
	750	</tp:member>
	751	<tp:member type="s" name="Subtype">
	752	<tp:docstring>
	753	Feedback subtype, according to the Type, can be an empty string (""),
	754	if there is no subtype.
	755	For example, generic nack is Type="nack" Subtype="".
	756	</tp:docstring>
	757	</tp:member>
	758	<tp:member type="s" name="Parameters">
	759	<tp:docstring>
	760	Feedback parameters as a string. Format is defined in the relevant RFC
	761	</tp:docstring>
	762	</tp:member>
	763	</tp:struct>
	764
	765	<tp:mapping name="RTCP_Feedback_Message_Map">
	766	<tp:added version="0.22.1"/>
	767	<tp:docstring>
	768	A map of codec and its feedback properties.
	769	</tp:docstring>
	770	<tp:member type="u" name="Codec_Identifier">
	771	<tp:docstring>
	772	Numeric identifier for the codec. This will be used as the
	773	PT in the SDP or content description.
	774	</tp:docstring>
	775	</tp:member>
	776	<tp:member type="(ua(sss))" tp:type="RTCP_Feedback_Message_Properties"
	777	name="Properties">
	778	<tp:docstring>
	779	The RTCP feedback properties for this codec.
	780	</tp:docstring>
	781	</tp:member>
	782	</tp:mapping>
	783
	784	<signal name="SetRemoteFeedbackMessages"
	785	tp:name-for-bindings="Set_Remote_Feedback_Messages">
	786	<tp:added version="0.22.1"/>
	787	<arg name="Messages" type="a{u(ua(sss))}"
	788	tp:type="RTCP_Feedback_Message_Map">
	789	<tp:docstring>
	790	Remote Feedback messages desired by the remote side
	791	</tp:docstring>
	792	</arg>
	793	<tp:docstring>
	794	Signal emitted when the connection manager wishes to inform the
	795	client of the feedback messages supported by the remote end.
	796	This signal is emitted before
	797	<tp:member-ref>SetRemoteCodecs</tp:member-ref>. If the client
	798	supports any of these messages, it must call
	799	<tp:member-ref>SupportedFeedbackMessages</tp:member-ref> before calling
	800	<tp:member-ref>SupportedCodecs</tp:member-ref>.
	801	</tp:docstring>
	802	</signal>
	803
	804	<method name="SupportedFeedbackMessages"
	805	tp:name-for-bindings="Supported_Feedback_Messages">
	806	<tp:added version="0.22.1"/>
	807	<arg name="Messages" direction="in" type="a{u(ua(sss))}"
	808	tp:type="RTCP_Feedback_Message_Map">
	809	<tp:docstring>
	810	Locally supported feedback messages.
	811	</tp:docstring>
	812	</arg>
	813	<tp:docstring>
	814	Inform the connection manager of the supported feedback messages
	815	for this session.
	816	This is called a before calling
	817	<tp:member-ref>SupportedCodecs</tp:member-ref>,
	818	<tp:member-ref>Ready</tp:member-ref> or
	819	<tp:member-ref>CodecsUpdated</tp:member-ref> to indicate the local,
	820	or negotiated feedback messages.
	821	</tp:docstring>
	822	</method>
	823
	824	<tp:struct name="RTP_Header_Extension"
	825	array-name="RTP_Header_Extensions_List">
	826	<tp:added version="0.22.1"/>
	827	<tp:docstring>
	828	A struct defining a RTP Header extension
	829	</tp:docstring>
	830	<tp:member type="u" name="ID">
	831	<tp:docstring>
	832	Identifier to be negotiated
	833	</tp:docstring>
	834	</tp:member>
	835	<tp:member type="u" tp:type="Media_Stream_Direction" name="Direction">
	836	<tp:docstring>
	837	Direction in which the Header Extension is negotiated.
	838	</tp:docstring>
	839	</tp:member>
	840	<tp:member type="s" name="URI">
	841	<tp:docstring>
	842	URI defining the extension
	843	</tp:docstring>
	844	</tp:member>
	845	<tp:member type="s" name="Parameters">
	846	<tp:docstring>
	847	Feedback parameters as a string. Format is defined in the relevant RFC
	848	</tp:docstring>
	849	</tp:member>
	850	</tp:struct>
	851
	852	<signal name="SetRemoteHeaderExtensions"
	853	tp:name-for-bindings="Set_Remote_Header_Extensions">
	854	<tp:added version="0.22.1"/>
	855	<arg name="Header_Extensions" type="a(uuss)"
	856	tp:type="RTP_Header_Extension[]">
	857	<tp:docstring>
	858	Header extensions desired by the remote side
	859	</tp:docstring>
	860	</arg>
	861	<tp:docstring>
	862	Signal emitted when the connection manager wishes to inform the
	863	client of the RTP header extensions supported by the remote end.
	864	This signal is emitted before
	865	<tp:member-ref>SetRemoteCodecs</tp:member-ref>. If the client
	866	supports any of these messages, it must call
	867	<tp:member-ref>SupportedHeaderExtensions</tp:member-ref> before calling
	868	<tp:member-ref>SupportedCodecs</tp:member-ref>.
	869	</tp:docstring>
	870	</signal>
	871
	872	<method name="SupportedHeaderExtensions"
	873	tp:name-for-bindings="Supported_Header_Extensions">
	874	<tp:added version="0.22.1"/>
	875	<arg name="Header_Extensions" direction="in" type="a(uuss)"
	876	tp:type="RTP_Header_Extension[]">
	877	<tp:docstring>
	878	Locally supported RTP header extensions.
	879	</tp:docstring>
	880	</arg>
	881	<tp:docstring>
	882	Inform the connection manager of the supported RTP header extensions
	883	for this session.
	884	This is called before calling
	885	<tp:member-ref>SupportedCodecs</tp:member-ref>,
	886	<tp:member-ref>Ready</tp:member-ref> or
	887	<tp:member-ref>CodecsUpdated</tp:member-ref> to indicate the local
	888	or negotiated RTP header extensions.
	889	</tp:docstring>
	890	</method>
	891
722	892	</interface>
723	893	</node>
724	894	<!-- vim:set sw=2 sts=2 et ft=xml: -->

-4

spec/Protocol.xml less more

98	98	access="read" type="a(susv)" tp:type="Param_Spec[]"
99	99	tp:immutable="yes">
100	100	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
101		<p>The parameters which must or may be provided to the
102		<tp:dbus-ref namespace="org.freedesktop.Telepathy.ConnectionManager"
103		>RequestConnection</tp:dbus-ref> method when connecting to the
104		given protocol.</p>
	101	<p>The parameters which may be specified in the
	102	<tp:dbus-ref namespace='ofdT.Account'>Parameters</tp:dbus-ref> of an
	103	<tp:dbus-ref namespace='ofdT'>Account</tp:dbus-ref> (or, for
	104	specialised applications which do not use the account manager, passed
	105	to <tp:dbus-ref
	106	namespace='ofdT.ConnectionManager'>RequestConnection</tp:dbus-ref>).
	107	Some parameters are mandatory, and some parameters only make sense
	108	when registering new accounts with the server; see the
	109	<tp:type>Param_Spec</tp:type> documentation for more details.</p>
105	110
106	111	<p>Connection managers with a <code>.manager</code> file
107	112	(as described as part of the

-8

spec/Protocol_Interface_Avatars.xml less more

67	67
68	68	<property name="SupportedAvatarMIMETypes"
69	69	tp:name-for-bindings="Supported_Avatar_MIME_Types"
70		type="as" access="read">
	70	type="as" access="read" tp:immutable="yes">
71	71	<tp:docstring>
72	72	The expected value of the <tp:dbus-ref
73	73	namespace="org.freedesktop.Telepathy"

78	78
79	79	<property name="MinimumAvatarHeight"
80	80	tp:name-for-bindings="Minimum_Avatar_Height"
81		type="u" access="read">
	81	type="u" access="read" tp:immutable="yes">
82	82	<tp:docstring>
83	83	The expected value of the <tp:dbus-ref
84	84	namespace="org.freedesktop.Telepathy"

89	89
90	90	<property name="MinimumAvatarWidth"
91	91	tp:name-for-bindings="Minimum_Avatar_Width"
92		type="u" access="read">
	92	type="u" access="read" tp:immutable="yes">
93	93	<tp:docstring>
94	94	The expected value of the <tp:dbus-ref
95	95	namespace="org.freedesktop.Telepathy"

100	100
101	101	<property name="RecommendedAvatarHeight"
102	102	tp:name-for-bindings="Recommended_Avatar_Height"
103		type="u" access="read">
	103	type="u" access="read" tp:immutable="yes">
104	104	<tp:docstring>
105	105	The expected value of the <tp:dbus-ref
106	106	namespace="org.freedesktop.Telepathy"

111	111
112	112	<property name="RecommendedAvatarWidth"
113	113	tp:name-for-bindings="Recommended_Avatar_Width"
114		type="u" access="read">
	114	type="u" access="read" tp:immutable="yes">
115	115	<tp:docstring>
116	116	The expected value of the <tp:dbus-ref
117	117	namespace="org.freedesktop.Telepathy"

122	122
123	123	<property name="MaximumAvatarHeight"
124	124	tp:name-for-bindings="Maximum_Avatar_Height"
125		type="u" access="read">
	125	type="u" access="read" tp:immutable="yes">
126	126	<tp:docstring>
127	127	The expected value of the <tp:dbus-ref
128	128	namespace="org.freedesktop.Telepathy"

133	133
134	134	<property name="MaximumAvatarWidth"
135	135	tp:name-for-bindings="Maximum_Avatar_Width"
136		type="u" access="read">
	136	type="u" access="read" tp:immutable="yes">
137	137	<tp:docstring>
138	138	The expected value of the <tp:dbus-ref
139	139	namespace="org.freedesktop.Telepathy"

144	144
145	145	<property name="MaximumAvatarBytes"
146	146	tp:name-for-bindings="Maximum_Avatar_Bytes"
147		type="u" access="read">
	147	type="u" access="read" tp:immutable="yes">
148	148	<tp:docstring>
149	149	The expected value of the <tp:dbus-ref
150	150	namespace="org.freedesktop.Telepathy"

-6

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.11</tp:version>
6
7		<tp:copyright>Copyright © 2005-2010 Collabora Limited</tp:copyright>
8		<tp:copyright>Copyright © 2005-2010 Nokia Corporation</tp:copyright>
	5	<tp:version>0.23.1</tp:version>
	6
	7	<tp:copyright>Copyright © 2005-2011 Collabora Limited</tp:copyright>
	8	<tp:copyright>Copyright © 2005-2011 Nokia Corporation</tp:copyright>
9	9	<tp:copyright>Copyright © 2006 INdT</tp:copyright>
10	10
11	11	<tp:license xmlns="http://www.w3.org/1999/xhtml">

55	55	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
56	56	<p>
57	57	On protocols that support contact lists, these interface expose the user's
58		contact lists, along with presence subscription information and contact
59		list groups (if supported).
	58	contact lists, along with presence subscription information, contact
	59	list groups (if supported), and the ability to block and unblock contacts
	60	(if supported).
60	61	</p>
61	62	</tp:docstring>
62	63
63	64	<xi:include href="Connection_Interface_Contact_List.xml"/>
64	65	<xi:include href="Connection_Interface_Contact_Groups.xml"/>
	66	<xi:include href="Connection_Interface_Contact_Blocking.xml"/>
65	67	</tp:section>
66	68
67	69	<tp:section name="Contact metadata interfaces">

+54

-0

spec/errors.xml less more

543	543	</tp:docstring>
544	544	</tp:error>
545	545
	546	<tp:error name="Software Upgrade Required">
	547	<tp:added version="0.21.12"/>
	548	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	549	<p>Raised as a
	550	<tp:dbus-ref namespace="ofdT.Connection">ConnectionError</tp:dbus-ref>
	551	when a Connection cannot be established because either the Connection
	552	Manager or its support library (e.g. wocky, papyon, sofiasip) requires
	553	upgrading to support a newer protocol version.</p>
	554
	555	<p>This error corresponds to the
	556	<tp:type>Connection_Status_Reason</tp:type> of Network_Error.</p>
	557
	558	<tp:rationale>
	559	Some protocols transmit a protocol or library version number to the
	560	server, which will disconnect them if the version isn't appropriate.
	561	This way we can report the error to the user, and if appropriate, the
	562	user's client can check for updates.
	563	</tp:rationale>
	564	</tp:docstring>
	565	</tp:error>
	566
	567	<tp:error name="Emergency Calls Not Supported">
	568	<tp:added version="0.21.12"/>
	569	<tp:docstring>
	570	Raised if a client attempts to dial a number that is recognized as an
	571	emergency number (e.g. '911' in the USA), but the Connection Manager or
	572	provider does not support dialling emergency numbers.
	573
	574	<tp:rationale>
	575	Many VOIP providers have the ability to dial traditional (PSTN)
	576	telephone numbers, but do not provide the ability to dial emergency
	577	numbers (for instance, Google Voice). This error provides additional
	578	information about why such a call was unsuccessful.
	579	</tp:rationale>
	580	</tp:docstring>
	581	</tp:error>
	582
	583	<tp:error name="Insufficient Balance">
	584	<tp:added version="0.22.1"/>
	585	<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
	586	<p>Raised if the user has insufficient
	587	<tp:dbus-ref namespace="ofdT.Connection.Interface">Balance</tp:dbus-ref>
	588	to place a call or send a message.</p>
	589
	590	<p>The key 'balance-required' MAY be included in
	591	<tp:dbus-ref namespace="ofdT.Channel.Type.Call.DRAFT">CallStateDetails</tp:dbus-ref>
	592	or a delivery report's <tp:type>Message_Part</tp:type>
	593	(with the same units and scale as
	594	<tp:dbus-ref namespace="ofdT.Connection.Interface.Balance">AccountBalance</tp:dbus-ref>)
	595	to indicate how much credit is required to make this call or send
	596	this message.</p>
	597	</tp:docstring>
	598	</tp:error>
	599
546	600	<tp:copyright>Copyright © 2005-2010 Collabora Limited</tp:copyright>
547	601	<tp:copyright>Copyright © 2005-2009 Nokia Corporation</tp:copyright>
548	602	<tp:license xmlns="http://www.w3.org/1999/xhtml">