[Telepathy-commits] [telepathy-spec/master] More details on server-defined contact lists

[Alban Crequy]

20080623165249-a41c0-52ffa8c30dbb7f520f6299a01050c1f1539b1de3.gz
---
 spec/Channel_Type_Contact_List.xml |   32 ++++++++++++++++++++++----------
 1 files changed, 22 insertions(+), 10 deletions(-)

diff --git a/spec/Channel_Type_Contact_List.xml b/spec/Channel_Type_Contact_List.xml
index 7e763aa..c7f5808 100644
--- a/spec/Channel_Type_Contact_List.xml
+++ b/spec/Channel_Type_Contact_List.xml
@@ -46,18 +46,30 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
       <li>hide - a group of contacts who are on the publish list but are temporarily disallowed from receiving your presence</li>
       <li>allow - a group of contacts who may send you messages</li>
       <li>deny - a group of contacts who may not send you messages</li>
-      <li>known - the group of all contacts known by the connection manager.
-      A contact can be absent from the subscribe and publish lists but still be
-      in the known list: it can be useful if the server stores metadata
-      on contacts.
-      Added in 0.17.?.</li>
+      <li>known - a group of contacts who have been stored by the user,
+      regardless of subscription state</li>
     </ul>
 
-    <p>A contact can be in several server-defined lists. All lists are
-    optional to implement. When a specific list is not implemented,
-    RequestHandles and RequestChannel return
-    org.freedesktop.Telepathy.Error.NotAvailable and clients MUST behave as if
-    it was empty.</p>
+    <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 known list, the client MUST
+    NOT assume that there is no contact stored by the user. Instead, the client
+    SHOULD get both the publish and subscribe lists.</p>
+
+    <p>A contact can be in several server-defined lists.</p>
+
+    <p>For example in XMPP, contacts who have the subscription type "none",
+    "from", "to" and "both" can be respectively in the lists:</p>
+
+    <ul>
+      <li>"none": known</li>
+      <li>"from": known and publish</li>
+      <li>"to": known and subscribe</li>
+      <li>"both": known, publish and subscribe</li>
+    </ul>
 
     <p>These contact list channels may not be closed.</p>
 
-- 
1.5.6.5