[Telepathy-commits] [telepathy-spec/master] Attempt to explain what Channel_Group_Change_Reason_Invalid_Contact means

Simon McVittie simon.mcvittie at collabora.co.uk
Mon Jan 19 10:05:36 PST 2009


---
 spec/Channel_Interface_Group.xml |   12 ++++++++++--
 1 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/spec/Channel_Interface_Group.xml b/spec/Channel_Interface_Group.xml
index 019e848..c0e85de 100644
--- a/spec/Channel_Interface_Group.xml
+++ b/spec/Channel_Interface_Group.xml
@@ -603,8 +603,16 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
         </tp:docstring>
       </tp:enumvalue>
       <tp:enumvalue suffix="Invalid_Contact" value="7">
-        <tp:docstring>
-            The change is because the requested contact does not exist.
+        <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
+          <p>The change is because the requested contact does not exist.</p>
+
+          <tp:rationale>
+            <p>For instance, if the user invites a nonexistent contact to a
+              chatroom or attempts to call a nonexistent contact, this could
+              be indicated by the CM adding that contact's handle to
+              remote-pending for reason None or Invited, then removing it for
+              reason Invalid_Contact.</p>
+          </tp:rationale>
         </tp:docstring>
       </tp:enumvalue>
       <tp:enumvalue suffix="No_Answer" value="8">
-- 
1.5.6.5




More information about the Telepathy-commits mailing list