[next] telepathy-spec: Remove ContactAttributeInterfaces property

[Xavier Claessens]

Module: telepathy-spec
Branch: next
Commit: 1af77275bb04c99972e3a720d81f9a8272315da4
URL:    http://cgit.freedesktop.org/telepathy/telepathy-spec/commit/?id=1af77275bb04c99972e3a720d81f9a8272315da4

Author: Xavier Claessens <xavier.claessens at collabora.co.uk>
Date:   Mon Jun 11 11:14:34 2012 +0200

Remove ContactAttributeInterfaces property

That property was used to detect legacy CMs that did not
implement all the contact attributes.

---

 spec/Connection_Interface_Contacts.xml |   30 ------------------------------
 1 files changed, 0 insertions(+), 30 deletions(-)

diff --git a/spec/Connection_Interface_Contacts.xml b/spec/Connection_Interface_Contacts.xml
index f105045..98d2b2b 100644
--- a/spec/Connection_Interface_Contacts.xml
+++ b/spec/Connection_Interface_Contacts.xml
@@ -81,16 +81,6 @@
       </tp:member>
     </tp:mapping>
 
-    <property name="ContactAttributeInterfaces" access="read" type="as"
-      tp:type="DBus_Interface[]"
-      tp:name-for-bindings="Contact_Attribute_Interfaces">
-      <tp:docstring>
-        A list of D-Bus interfaces for which
-        <tp:member-ref>GetContactAttributes</tp:member-ref> is expected to work.
-        This cannot change during the lifetime of the Connection.
-      </tp:docstring>
-    </property>
-
     <method name="GetContactAttributes"
       tp:name-for-bindings="Get_Contact_Attributes">
       <tp:docstring>
@@ -111,20 +101,6 @@
             interfaces, whose values can be obtained without additional network
             activity, will be in the reply.</p>
 
-          <p>Connection managers SHOULD ignore interfaces requested which they
-            do not support (i.e. those not mentioned in the
-            <tp:member-ref>ContactAttributeInterfaces</tp:member-ref>
-            property.)</p>
-
-          <tp:rationale>
-            <p>This simplifies client-side code. Clients which care may
-              distinguish between unsupported interfaces (e.g. this Connection
-              does not support Avatars), and interfaces on which no information
-              is known for these contacts (e.g. we don't know the avatar tokens
-              of any of the contacts, so we omitted them all) by inspecting
-              <tp:member-ref>ContactAttributeInterfaces</tp:member-ref>.</p>
-          </tp:rationale>
-
           <p>Attributes from the interface
             <tp:dbus-ref>im.telepathy1.Connection</tp:dbus-ref>
             are always returned, and need not be requested explicitly.</p>
@@ -143,12 +119,6 @@
             attributes.
           </tp:rationale>
         </tp:docstring>
-        <tp:changed version="0.19.2">
-          requesting information for interfaces not mentioned in
-          <tp:member-ref>ContactAttributeInterfaces</tp:member-ref> is no
-          longer an error. Be aware that older connection managers may still
-          consider this an error.
-        </tp:changed>
       </arg>
 
       <arg direction="out" type="a{ua{sv}}" name="Attributes"