[Telepathy-commits] [telepathy-spec/master] server-defined lists: remove MUSTs for clients, and rephrase

Alban Crequy alban.crequy at collabora.co.uk
Wed Oct 22 06:41:44 PDT 2008

 spec/Channel_Type_Contact_List.xml |   16 ++++++++--------
 1 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/spec/Channel_Type_Contact_List.xml b/spec/Channel_Type_Contact_List.xml
index b348756..9f2f22b 100644
--- a/spec/Channel_Type_Contact_List.xml
+++ b/spec/Channel_Type_Contact_List.xml
@@ -51,15 +51,15 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
-    <p>All lists are optional to implement. When a specific list is not
-    implemented, RequestHandles and RequestChannel return
-    org.freedesktop.Telepathy.Error.NotAvailable. If this happens for the
-    subscribe, publish, hide and deny lists, clients MUST behave as if it was
-    empty. If this happens for the allow list, clients MUST assume you can send
-    messages to everybody. If this happens for the stored list, the client MAY
-    use the union of the publish and subscribe lists.</p>
+    <p>A contact can be in several server-defined lists. All lists are optional
+    to implement. If RequestHandles or RequestChannel for a particular contact
+    list raises an error, this indicates that the connection manager makes no
+    particular statement about the list's contents; clients MUST NOT consider
+    this to be fatal.</p>
-    <p>A contact can be in several server-defined lists.</p>
+    <p>If a client wants to list all of a user's contacts, it is appropriate to
+    use the union of the subscribe, publish and stored lists, including the
+    local and remote pending members.</p>
     <p>For example in XMPP, contacts who have the subscription type "none",
     "from", "to" and "both" can be respectively in the lists:</p>

More information about the Telepathy-commits mailing list