errors.xml 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418
  1. <?xml version="1.0" ?>
  2. <tp:errors xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0" namespace="org.freedesktop.Telepathy.Error">
  3. <tp:error name="Network Error">
  4. <tp:docstring>
  5. Raised when there is an error reading from or writing to the network.
  6. </tp:docstring>
  7. </tp:error>
  8. <tp:error name="Not Implemented">
  9. <tp:docstring>
  10. Raised when the requested method, channel, etc is not available on this connection.
  11. </tp:docstring>
  12. </tp:error>
  13. <tp:error name="Invalid Argument">
  14. <tp:docstring>
  15. Raised when one of the provided arguments is invalid.
  16. </tp:docstring>
  17. </tp:error>
  18. <tp:error name="Not Available">
  19. <tp:docstring>
  20. Raised when the requested functionality is temporarily unavailable.
  21. </tp:docstring>
  22. </tp:error>
  23. <tp:error name="Permission Denied">
  24. <tp:docstring>
  25. The user is not permitted to perform the requested operation.
  26. </tp:docstring>
  27. </tp:error>
  28. <tp:error name="Disconnected">
  29. <tp:docstring>
  30. The connection is not currently connected and cannot be used.
  31. This error may also be raised when operations are performed on a
  32. Connection for which
  33. <tp:dbus-ref namespace="org.freedesktop.Telepathy.Connection">StatusChanged</tp:dbus-ref>
  34. has signalled status Disconnected for reason None.
  35. <tp:rationale>
  36. The second usage corresponds to None in the
  37. <tp:type>Connection_Status_Reason</tp:type> enum; if a better reason
  38. is available, the corresponding error should be used instead.
  39. </tp:rationale>
  40. </tp:docstring>
  41. </tp:error>
  42. <tp:error name="Invalid Handle">
  43. <tp:docstring>
  44. The handle specified is unknown on this channel or connection.
  45. </tp:docstring>
  46. </tp:error>
  47. <tp:error name="Channel.Banned">
  48. <tp:docstring>
  49. You are banned from the channel.
  50. </tp:docstring>
  51. </tp:error>
  52. <tp:error name="Channel.Full">
  53. <tp:docstring>
  54. The channel is full.
  55. </tp:docstring>
  56. </tp:error>
  57. <tp:error name="Channel.Invite Only">
  58. <tp:docstring>
  59. The requested channel is invite-only.
  60. </tp:docstring>
  61. </tp:error>
  62. <tp:error name="Not Yours">
  63. <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
  64. <p>The requested channel or other resource already exists, and another
  65. user interface in this session is responsible for it.</p>
  66. <p>User interfaces SHOULD handle this error unobtrusively, since it
  67. indicates that some other user interface is already processing the
  68. channel.</p>
  69. </tp:docstring>
  70. </tp:error>
  71. <tp:error name="Cancelled">
  72. <tp:docstring>
  73. Raised by an ongoing request if it is cancelled by user request before
  74. it has completed, or when operations are performed on an object which
  75. the user has asked to close (for instance, a Connection where the user
  76. has called Disconnect, or a Channel where the user has called Close).
  77. <tp:rationale>
  78. The second form can be used to correspond to the Requested member in
  79. the <tp:type>Connection_Status_Reason</tp:type> enum, or to
  80. to represent the situation where disconnecting a Connection,
  81. closing a Channel, etc. has been requested by the user but this
  82. request has not yet been acted on, for instance because the
  83. service will only act on the request when it has finished processing
  84. an event queue.
  85. </tp:rationale>
  86. </tp:docstring>
  87. </tp:error>
  88. <tp:error name="Authentication Failed">
  89. <tp:docstring>
  90. Raised when authentication with a service was unsuccessful.
  91. <tp:rationale>
  92. This corresponds to Authentication_Failed in the
  93. <tp:type>Connection_Status_Reason</tp:type> enum.
  94. </tp:rationale>
  95. </tp:docstring>
  96. </tp:error>
  97. <tp:error name="Encryption Not Available">
  98. <tp:docstring>
  99. Raised if a user request insisted that encryption should be used,
  100. but encryption was not actually available.
  101. <tp:rationale>
  102. This corresponds to part of Encryption_Error in the
  103. <tp:type>Connection_Status_Reason</tp:type> enum. It's been separated
  104. into a distinct error here because the two concepts that were part
  105. of EncryptionError seem to be things that could reasonably appear
  106. differently in the UI.
  107. </tp:rationale>
  108. </tp:docstring>
  109. </tp:error>
  110. <tp:error name="Encryption Error">
  111. <tp:docstring>
  112. Raised if encryption appears to be available, but could not actually be
  113. used (for instance if SSL/TLS negotiation fails).
  114. <tp:rationale>
  115. This corresponds to part of Encryption_Error in the
  116. <tp:type>Connection_Status_Reason</tp:type> enum.
  117. </tp:rationale>
  118. </tp:docstring>
  119. </tp:error>
  120. <tp:error name="Cert.Not Provided">
  121. <tp:docstring>
  122. Raised if the server did not provide a SSL/TLS certificate. This error
  123. MUST NOT be used to represent the absence of a client certificate
  124. provided by the Telepathy connection manager.
  125. <tp:rationale>
  126. This corresponds to Cert_Not_Provided in the
  127. <tp:type>Connection_Status_Reason</tp:type> enum. That error
  128. explicitly applied only to server SSL certificates, so this one
  129. is similarly limited; having the CM present a client certificate
  130. is a possible future feature, but it should have its own error
  131. handling.
  132. </tp:rationale>
  133. </tp:docstring>
  134. </tp:error>
  135. <tp:error name="Cert.Untrusted">
  136. <tp:docstring>
  137. Raised if the server provided a SSL/TLS certificate signed by an
  138. untrusted certifying authority. This error SHOULD NOT be used to
  139. represent a self-signed certificate: see the Self Signed error for that.
  140. <tp:rationale>
  141. This corresponds to Cert_Untrusted in the
  142. <tp:type>Connection_Status_Reason</tp:type> enum, with a clarification
  143. to avoid ambiguity.
  144. </tp:rationale>
  145. </tp:docstring>
  146. </tp:error>
  147. <tp:error name="Cert.Expired">
  148. <tp:docstring>
  149. Raised if the server provided an expired SSL/TLS certificate.
  150. <tp:rationale>
  151. This corresponds to Cert_Expired in the
  152. <tp:type>Connection_Status_Reason</tp:type> enum.
  153. </tp:rationale>
  154. </tp:docstring>
  155. </tp:error>
  156. <tp:error name="Cert.Not Activated">
  157. <tp:docstring>
  158. Raised if the server provided an SSL/TLS certificate that will become
  159. valid at some point in the future.
  160. <tp:rationale>
  161. This corresponds to Cert_Not_Activated in the
  162. <tp:type>Connection_Status_Reason</tp:type> enum.
  163. </tp:rationale>
  164. </tp:docstring>
  165. </tp:error>
  166. <tp:error name="Cert.Fingerprint Mismatch">
  167. <tp:docstring>
  168. Raised if the server provided an SSL/TLS certificate that did not have
  169. the expected fingerprint.
  170. <tp:rationale>
  171. This corresponds to Cert_Fingerprint_Mismatch in the
  172. <tp:type>Connection_Status_Reason</tp:type> enum.
  173. </tp:rationale>
  174. </tp:docstring>
  175. </tp:error>
  176. <tp:error name="Cert.Hostname Mismatch">
  177. <tp:docstring>
  178. Raised if the server provided an SSL/TLS certificate that did not match
  179. its hostname.
  180. <tp:rationale>
  181. This corresponds to Cert_Hostname_Mismatch in the
  182. <tp:type>Connection_Status_Reason</tp:type> enum.
  183. </tp:rationale>
  184. </tp:docstring>
  185. </tp:error>
  186. <tp:error name="Cert.Self Signed">
  187. <tp:docstring>
  188. Raised if the server provided an SSL/TLS certificate that is self-signed
  189. and untrusted.
  190. <tp:rationale>
  191. This corresponds to Cert_Hostname_Mismatch in the
  192. <tp:type>Connection_Status_Reason</tp:type> enum.
  193. </tp:rationale>
  194. </tp:docstring>
  195. </tp:error>
  196. <tp:error name="Cert.Invalid">
  197. <tp:docstring>
  198. Raised if the server provided an SSL/TLS certificate that is
  199. unacceptable in some way that does not have a more specific error.
  200. <tp:rationale>
  201. This corresponds to Cert_Other_Error in the
  202. <tp:type>Connection_Status_Reason</tp:type> enum.
  203. </tp:rationale>
  204. </tp:docstring>
  205. </tp:error>
  206. <tp:error name="Not Capable">
  207. <tp:docstring>
  208. Raised when requested functionality is unavailable due to contact
  209. not having required capabilities.
  210. </tp:docstring>
  211. </tp:error>
  212. <tp:error name="Offline">
  213. <tp:docstring>
  214. Raised when requested functionality is unavailable because a contact is
  215. offline.
  216. <tp:rationale>
  217. This corresponds to Offline in the
  218. <tp:type>Channel_Group_Change_Reason</tp:type> enum.
  219. </tp:rationale>
  220. </tp:docstring>
  221. </tp:error>
  222. <tp:error name="Channel.Kicked">
  223. <tp:docstring>
  224. Used to represent a user being ejected from a channel by another user,
  225. for instance being kicked from a chatroom.
  226. <tp:rationale>
  227. This corresponds to Kicked in the
  228. <tp:type>Channel_Group_Change_Reason</tp:type> enum.
  229. </tp:rationale>
  230. </tp:docstring>
  231. </tp:error>
  232. <tp:error name="Busy">
  233. <tp:docstring>
  234. Used to represent a user being removed from a channel because of a
  235. "busy" indication. This error SHOULD NOT be used to represent a server
  236. or other infrastructure being too busy to process a request - for that,
  237. see ServerBusy.
  238. <tp:rationale>
  239. This corresponds to Busy in the
  240. <tp:type>Channel_Group_Change_Reason</tp:type> enum.
  241. </tp:rationale>
  242. </tp:docstring>
  243. </tp:error>
  244. <tp:error name="No Answer">
  245. <tp:docstring>
  246. Used to represent a user being removed from a channel because they did
  247. not respond, e.g. to a StreamedMedia call.
  248. <tp:rationale>
  249. This corresponds to No_Answer in the
  250. <tp:type>Channel_Group_Change_Reason</tp:type> enum.
  251. </tp:rationale>
  252. </tp:docstring>
  253. </tp:error>
  254. <tp:error name="Does Not Exist">
  255. <tp:docstring>
  256. Raised when the requested user does not, in fact, exist.
  257. <tp:rationale>
  258. This corresponds to Invalid_Contact in the
  259. <tp:type>Channel_Group_Change_Reason</tp:type> enum, but can also be
  260. used to represent other things not existing (like chatrooms, perhaps).
  261. </tp:rationale>
  262. </tp:docstring>
  263. </tp:error>
  264. <tp:error name="Terminated">
  265. <tp:docstring>
  266. Raised when a channel is terminated for an unspecified reason. In
  267. particular, this error SHOULD be used whenever normal termination of
  268. a 1-1 StreamedMedia call by the remote user is represented as a D-Bus
  269. error name.
  270. <tp:rationale>
  271. This corresponds to None in the
  272. <tp:type>Channel_Group_Change_Reason</tp:type> enum.
  273. </tp:rationale>
  274. </tp:docstring>
  275. </tp:error>
  276. <tp:error name="Connection Refused">
  277. <tp:docstring>
  278. Raised when a connection is refused.
  279. </tp:docstring>
  280. </tp:error>
  281. <tp:error name="Connection Failed">
  282. <tp:docstring>
  283. Raised when a connection can't be established.
  284. </tp:docstring>
  285. </tp:error>
  286. <tp:error name="Connection Lost">
  287. <tp:docstring>
  288. Raised when a connection is broken.
  289. </tp:docstring>
  290. </tp:error>
  291. <tp:error name="Already Connected">
  292. <tp:docstring>
  293. Raised when the user attempts to connect to an account but they are
  294. already connected (perhaps from another client or computer), and the
  295. protocol or account settings do not allow this.
  296. <tp:rationale>
  297. XMPP can have this behaviour if the user chooses the same resource
  298. in both clients (it is server-dependent whether the result is
  299. AlreadyConnected on the new connection, ConnectionReplaced on the
  300. old connection, or two successful connections).
  301. </tp:rationale>
  302. </tp:docstring>
  303. </tp:error>
  304. <tp:error name="Connection Replaced">
  305. <tp:docstring>
  306. Raised by an existing connection to an account if it is replaced by
  307. a new connection (perhaps from another client or computer).
  308. <tp:rationale>
  309. In MSNP, when connecting twice with the same Passport, the new
  310. connection "wins" and the old one is automatically disconnected.
  311. XMPP can also have this behaviour if the user chooses the same
  312. resource in two clients (it is server-dependent whether the result is
  313. AlreadyConnected on the new connection, ConnectionReplaced on the
  314. old connection, or two successful connections).
  315. </tp:rationale>
  316. </tp:docstring>
  317. </tp:error>
  318. <tp:error name="Registration Exists">
  319. <tp:docstring>
  320. Raised during in-band registration if the server indicates that the
  321. requested account already exists.
  322. </tp:docstring>
  323. </tp:error>
  324. <tp:error name="Service Busy">
  325. <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
  326. Raised if a server or some other piece of infrastructure cannot process
  327. the request, e.g. due to resource limitations. Clients MAY try again
  328. later.
  329. <tp:rationale>
  330. This is not the same error as Busy, which indicates that a
  331. <em>user</em> is busy.
  332. </tp:rationale>
  333. </tp:docstring>
  334. </tp:error>
  335. <tp:error name="Resource Unavailable">
  336. <tp:docstring>
  337. Raised if a request cannot be satisfied because a process local to the
  338. user has insufficient resources. Clients MAY try again
  339. later.
  340. <tp:rationale>
  341. For instance, the <tp:dbus-ref
  342. namespace="org.freedesktop.Telepathy">ChannelDispatcher</tp:dbus-ref>
  343. might raise this error for some or all channel requests if it has
  344. detected that there is not enough free memory.
  345. </tp:rationale>
  346. </tp:docstring>
  347. </tp:error>
  348. <tp:copyright>Copyright © 2005-2009 Collabora Limited</tp:copyright>
  349. <tp:copyright>Copyright © 2005-2009 Nokia Corporation</tp:copyright>
  350. <tp:license xmlns="http://www.w3.org/1999/xhtml">
  351. <p>This library is free software; you can redistribute it and/or
  352. modify it under the terms of the GNU Lesser General Public
  353. License as published by the Free Software Foundation; either
  354. version 2.1 of the License, or (at your option) any later version.</p>
  355. <p>This library is distributed in the hope that it will be useful,
  356. but WITHOUT ANY WARRANTY; without even the implied warranty of
  357. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  358. Lesser General Public License for more details.</p>
  359. <p>You should have received a copy of the GNU Lesser General Public
  360. License along with this library; if not, write to the Free Software
  361. Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</p>
  362. </tp:license>
  363. </tp:errors>